Prepared by
Forrest M. Council
University of North Carolina
Highway Safety Research Center
730 Martin Luther King Jr Blvd, Suite 300, CB #3430
NC 27599-3430
and
Rushi Patel
Yusuf Mohamedshah
LENDIS Corporation
Turner-Fairbank Highway Research Center
Federal Highway Administration
6300 Georgetown Pike
McLean, VA 22101
Prepared for
Federal Highway Administration
Office of Safety and Traffic Operations Research & Development
U.S. Department of Transportation
Washington, DC 20590
January 2006
(Changes from the earlier version are in bold and italics)
The North Carolina database, which is incorporated into the HSIS system, is derived from an Oracle database on the “NCDMV” system. Before 2000, the data was derived from the “MERGE” system –- a mainframe database -- maintained by the NCDOT MIS group. North Carolina provides data to HSIS in four different files -- accident characteristics, vehicles in the accidents, occupants in the vehicles, and roadway inventory. The first three files are derived from the “NCDMV” system, while the roadway inventory file is provided by the NCDOT GIS section. The roadway file contains information on traffic counts. As with the other HSIS states, these four files (three accident subfiles plus roadway inventory) are then SAS formatted and loaded into the HSIS system. The raw file data are provided to the Highway Safety Research Center where they are retained as backup information. The documentation (variable listings, definitions, etc.) for these raw files and for the SAS files that are developed from them are available at FHWA offices. HSIS team at FHWA maintains the conversion programs developed by HSRC and LENDIS, CORP. to convert the files into SQL and SAS formats.
Beginning in 1994, the HSIS system has been converted to a relational
database for internal use. This database, originally a SYBASE
system and now an ORACLE system, stores the data received from
North Carolina and other states, and the data files for a given state
are linked and manipulated using SQL language. However,
this conversion from the original SAS-based system to the newer relational system
is somewhat transparent to the end-user of the data since the output files produced
by ORACLE for modeling and analysis will be SAS formatted. As in the past,
we have continued to produce SAS format libraries for each of the variables in
each of the files. Because it is envisioned that the majority of analyses
will utilize these SAS files and formats, this Guidebook will concern these SAS
files -- their formats, completeness, and quality.
As noted above, the accident data are divided into three separate subfiles. The first containing the basic accident information on a case by case basis, the second containing information up to 15 vehicles in each accident, and a third containing all occupants in each of the 15 possible vehicles. The vehicle and occupant data can be linked to the basic accident file for a specific case using the accident report number. The accident subfile can be linked to the Roadway Inventory File using a county/route/milepost variable.
Unlike the accident file, which is referenced to a point on the roadway, each record in the Roadway Inventory File contains information on a homogeneous section of roadway (i.e., a stretch of road which is consistent in terms of certain characteristics, with a new section being defined each time any of the characteristics changes.) Each record on the basic inventory file contains current characteristics of the roadway system, and includes such variables as surface width, lane width and type, shoulder width and type, median information and other variables. This file also contains information on traffic volumes -- AADT and some data on total percent trucks and truck percent during peak time periods.
Details of the files noted above are included in the following sections.Accident data are collected statewide by all police departments in North Carolina on a standard form as prescribed by state law. The prescribed accident-reporting threshold is currently personal injury or $1,000 property damage. Prior to 1996, the crash-reporting threshold was $500. It is felt that this threshold is generally used for all accidents occurring on the entire North Carolina roadway system, both in rural and urban areas. It is probably more consistently followed in the rural areas where State Highway Patrol does most of the reporting. However, it is a feeling of North Carolina data users that the overwhelming majority of municipal police agencies also follow the same reporting threshold.
There are approximately 230,000 accidents in the entire state each year. For each crash that is investigated, an accident report form is sent to the North Carolina Department of Motor Vehicles (DMV) Accident Reports Division, the central repository of the accident data. The DMV is responsible for coding and keypunching all of the information on the form, including the data used in locating the accident to the roadway system. Of the 230,000 accidents that are keypunched each year, approximately 70% of these are linkable with the Roadway Inventory File. It should be noted that the number of linkable accidents has increased considerably from 2002 onwards. This is because the number of inventoried miles to which crashes can be mileposted has increased. Hence, for 2003, HSIS has about 145,000 crashes that are linkable to the roadway inventory. Before 2003, the number of linkable crashes was significantly lower (about 100,000 in 2001 and about 95,000 in 1997). The HSIS currently includes data from 1990 through 2004.
In terms of coding accident location, the North Carolina system is different than many of the other state systems. The crash location system is a county/route/milepost system, which is based on a computerized (non-physically mileposted) “paper” reference system. The Department of Motor Vehicles types the basic location information provided by the investigating officer. This includes the route on which the accident occurred, and a distance and a direction to a reference point such as an intersecting roadway, a bridge, or a city boundary. The computer then assigns a milepost based on these data. Of the 77,000 miles of roadway on the North Carolina state system, approximately 39,000 miles are included in this computerized reference system until 2001. Accidents could only be located to these 39,000 miles of roadway. For 2002 and 2003, approximately 62,000 miles are included, which results in a significant increase in linkable accidents. (It is noted that the 39,000 miles total for pre-2002 years is still larger than the inventoried and mileposted systems in most states within HSIS). The linkable routes include all Interstate, U.S., and N.C. routes, and major secondary routes (down through collectors) in both rural and urban areas. The un-linkable miles are predominantly secondary roads in rural areas and city streets in urban areas. (Note that there are no "county roads" in North Carolina since all except for non-system city streets are under State control.) Some accidents on primary routes in urban areas cannot be mileposted due to changes in street names, which have not been updated in the computerized mileposting program.
In short, the computer assigns a milepost to an accident based on the route it is on and the distance to a nearby reference point. In providing their location information, police officers are asked to report distance to the nearest one-tenth of a mile in rural areas when the crash is not at or near an intersection. If an accident occurs within 500 feet of an intersection, the distance is to be reported in feet. In urban areas, locations are generally provided in feet from a nearby intersection. There is some indication that the “less than 500 feet” criterion is not always followed for rural intersections.
Even with the lack of computerized reference mileposts for some of the roadways, and with errors due to changes in city street names, approximately 120,000 accidents per year are mileposted. Again, note that the number of mileposted accidents for 2003 is approximately 145,000. It is felt by NC DOT and other users that approximately 80 to 90 percent of the mileposted accidents in urban areas are correctly mileposted within 100 feet of their true location. Similarly, it is felt that approximately 80% of those in rural areas are mileposted within a tenth of a mile of their true location.
As indicated above, North Carolina is in the process of beginning to update its accident record system by converting to a relational database. An important component of this modified system will be the ability for users of the data (e.g., Traffic Engineering staff) to make online corrections to accident locations in their use of hard copies.
The North Carolina accident file contains the basic variables found on most state accident files, with some important additions. There is both a first harmful event and a most harmful event variable, allowing one to better correlate injury to specific type of impact. Unlike other HSIS states, North Carolina accident files from 2000 onwards have some work zone related variables which allows one to locate a crash in relation to the location in the work zone and whether the work zone was marked or not.
The Vehicle file contains approximately 250,000 vehicles each year. As in accident file, the number of vehicles for 2002 and 2003 reflects the higher number of crashes that are present for these years because of a higher number of linkable roads. Ratings of vehicle damage severity, useful in analyzing and controlling for crash severity, are captured in the TAD ratings. Unlike any other HSIS state, information on truck trailer width and length and total truck length is captured from the accident report form until 2000. This allows for categorizations of truck data not usually possible in most state truck files. There is a rollover variable that is separate from all other variables and specific to each vehicle, allowing one to separate rollover from both the type of accident and from impact with fixed objects. This allows the study of rollover as a result of other impacts, such as impacts with fixed objects. There is an officer judgment related to “drivability” of the vehicle, which can be used as a towaway threshold in certain analyses. From 2000 onwards, there are event variables in the vehicle file, which allows one to examine the sequence of events of an accident. Finally, there is also an indicator of airbag deployment, and estimates of distance from the roadway to the fixed object struck. Note that due to change in reporting practices from 2000 onwards some variables were dropped and some new variables were added. A NOTE is added under such variables in the format section of the guidebook.
The Occupant subfile includes information on all occupants in a vehicle, whether injured or not. This file contains approximately 300,000 occupants each year (and this number is lower for years before 2002 as the number of accidents in HSIS for 2002 and 2003 has increased considerably), and includes standard variables related to seating positions, sex, race, and injury. As with most other states, the injury variable in North Carolina is the KABCO system, which provides police estimates of injury level.
In general, the severity of crashes in North Carolina is somewhat more severe than in the other HSIS states, with more injury crashes and a lower percentage of PDOs. This probably stems from the fact that North Carolina is somewhat rural, as reflected by the slightly higher proportion of crashes in rural areas.
Tabulations were run to examine the question of reporting completeness and data quality for accident, vehicle, and occupant variables. Here, study of percent of “unknown,” “not applicable,” and “not stated” values for all key variables found in these files indicates that, in general, the data are quite complete. In most cases, non-coding occurs in less than one percent of the cases. For variables in which the percentage of non-coding is somewhat higher, a "NOTE" has been included under that variable listing in the later format sections of this Guidebook.
It should also be noted that the North Carolina Vehicle subfile did not contain detailed elements on large truck crashes proposed by the National Governor's Association (NGA) until 2000. In 1999 and earlier, supplemental NGA data were collected by some officers (primarily State Highway Patrol officers) on truck crashes on a supplemental report form. These data are submitted to the Truck Enforcement Unit at the Division of Motor Vehicles for computerization. Unfortunately, no standard accident number is available to link these data with the standard Accident File. However, in 2000, the accident report form was modified to include virtually all of the NGA-specified variables. Thus, these truck-related data are in the 2000 and later accident files. If warranted for a special study, linkage for the pre-1999 data might be accomplished through driver license number, driver name, and date of crash.
To
assess the accuracy of the accident variables (and the variables in the other
files), we questioned users of the data and examined and compared certain
single variable tables. In North Carolina, we questioned staffs
in the Management Information Systems office who maintain the computerized
files, the Traffic Engineering Branch who use the data in various
hazardous location analyses and other evaluations, and the Highway Safety
Research Center staff who have used the data for more than thirty years in a
variety of analysis efforts. The staff were interviewed concerning variables
they feel are incompletely coded or that might be inaccurate.
In general, most indicated that they felt that almost all the variables on the file were accurately coded. It is obvious that the “occupant restraint use” variable on the file is inaccurate, in that regularly conducted field observations of use indicate figures which are at least 10 to 15 percent lower than the values found in the accident file. (This is felt to be the case in accident-based measures of occupant restraint use in all states systems, particularly in states with a strong belt-use law which will cause drivers to report to the investigating officer that they have used the belt whether they have or not).
In the accident file, accident severity has gradually decreased over the 1990 - 2003 period. Here, fatalities and A-injuries have decreased slightly while C- (minor) injuries have increased slightly. This is very likely due to changes in the overall accident pattern in North Carolina, probably due to increased urbanization. Under accident type (i.e., first harmful event), it appears that the number of animals being struck has increased slightly. We have noted similar increasing trends in other HSIS states. In general, from the interviews and the data comparisons conducted, the data appear quite accurate. In the limited number of cases where possible inaccuracies were found, they are noted under the specific variables.The roadway inventory information is the responsibility of the Roadway Inventory Section, GIS Branch, of the NC Division of Highways. The original roadway inventory file was based on field inventory and constructions plans and was developed a number of years ago. Since that time, copies of all construction, resurfacing, or major widening plans are sent to the Roadway Inventory Section who input data from the plans. Thus, the updating is done on an ongoing basis. The file is usually completely updated by April 1 of the following year for the preceding December 31 closeout.
As noted above, the basic inventory file contains current characteristics of the state road system. It is estimated that there is approximately 92,000 miles of total roadway mileage in the state. There is 77,000 miles of roadway in the NC DOT roadway inventory system, approximately 14,000 of which are primary roadways. The 77,000 miles represents a very high proportion of total existing mileage in the state, much higher than is what is found in almost all of the states in the nation, since there are no “county roads” in North Carolina -- all such roads are controlled by the NC DOT. The remaining 15,000 miles of total state mileage are city streets.
Of the 77,000 miles in the state system, approximately 62,000 miles are now in the computer mileposting system, allowing accidents to be linked to them. These are the miles in the HSIS system. As noted before, these 62,000 miles are significantly higher than the 35,000 miles that were captured in the NC roadway inventory system for earlier years. This is not because of new roads were built, but reflects a sustained NC DOT effort to enter these existing miles into the “mileposting” computer program, making linking accidents to these miles possible. As noted above, this mileage includes all 14,000 miles of primary roadways plus an additional 48,000 miles of secondary roadways and urban streets. Note here that before 2002, the miles of primary roads in the roadway inventory system was the same, around 14,000, but the miles in the secondary system was around 21,000. The average homogeneous section length in the NC (and HSIS) roadway inventory file is approximately 0.7 miles. Table 1 presents mileage breakdowns for all paved two-way roadways (i.e., omitting all unpaved and one-way roadways) for the latest available year, 2003. As expected since it is a state-controlled system, the file is predominately rural in nature, with close to 84% of the roadways being in rural or near-rural areas.
(NOTE: Of the total amount of mileposted mileage available for inclusion in the basic Inventory File, approximately 750 miles of roadway were omitted. These roadways are either characterized as couplets (i.e., usually urban roadways with the same route number in which the two directions of travel are separated by one or more city blocks) or as other divided roadway with "unbalanced" geometrics (i.e., roadway segments in which the geometrics, such as shoulder width or type, are not the same in both directions of travel). This relative small amount of mileage is difficult to work with both in terms of characterization of a "standard" cross-section and in terms of appropriate linkage with the accident files.)
| Roadway Category | Mileage |
|---|---|
| Urban freeways | 530.4 |
| Urban freeways < 4 Lanes | 49.27 |
| Urban multilane divided non-freeways | 1,098.36 |
| Urban multilane undivided non-freeways | 420.09 |
| Urban 2 In highways | 5,135.07 |
| Rural freeways | 944.75 |
| Rural freeways < 4 Ins | 142.91 |
| Rural multilane divided non-freeways | 1,080.01 |
| Rural multilane undivided non-freeways | 186.08 |
| Rural 2 In highways | 50,129.54 |
| Other | 2,971.32 |
| Total | 62,687.8 |
The basic HSIS Inventory File contains both route description variables and cross-section variables that would be considered common among state inventory files. It includes such "standard" items as right and left shoulder width and type, lane widths, number of lanes, median width and type, roadway surface description, AADT, percent trucks, and others. In addition, it contains information on terrain, whether a section is a HPMS sample section, information on total and peak period truck percentages for certain roadway sections, and an indication of traffic growth factors for sections for which such growth factors have been developed.
While there is no construction zone inventory or project history file in North Carolina, each section of roadway in the basic inventory file contains an “improvement” flag, which denotes the year of the last improvement, made to the section. There is a second variable, which denotes the general type of improvement. This would differentiate between renovation, repaving, major rationing, minor rationing, and traffic safety/traffic engineering improvements. However, it does not provide the types of traffic safety/engineering improvement actually done. The improvement flag is based on construction plans and other sources identified above. Using this information, a "generic" roadway improvement-history file could be developed as years of inventory data are accumulated into HSIS.
The major gaps in the inventory information include intersection/interchange inventory information, passing sight distance, design speed and design volume, information on inside shoulders on a majority of the divided roadways (as discussed below) and, most importantly, information on either horizontal curve or vertical grade data. With respect to the latter two data items, the North Carolina DOT Traffic Engineering Branch is considering using temporary employees to develop horizontal and vertical files from CADD drawings for the Interstate system and certain other major roadways. This project has not yet been funded.
In addition, there is no current computerized intersection inventory information available. Inventory information does exist on a separate file related to traffic signals. At this point it is not readily mergeable with the location file.
Examination of the single variable tables for key variables in the file indicates very little uncoded mileage for most of the variables -- less than 1.5%. The main problem variables are with the right and left "shoulder type" and "shoulder width," which are coded as "unknown" in over ten percent of the cases. Conversations with DOT staff indicated that this lack of inventory information involves both missing data and the inventory practices on divided roadways. On these divided roadways, "right shoulder" is indeed the outer shoulder on the right in the direction of inventory. However, in the base file, "left shoulder" actually refers to the outer shoulder on the far left side of the roadway, across the opposing lanes of travel. This is unlike other states where "left shoulder" on a divided roadway refers to inside, or median shoulder. Thus, for almost all of the divided roadways in North Carolina, there is no information on the inside, or median shoulder. There is information on median type and width, with the width being measured from the edge of the traveled lane, thus including the inside shoulder.
To determine the accuracy within the roadway file, both user and data maintaining groups within the North Carolina DOT were questioned, and a set of runs of variables that should be similar were compared to each other. Both the data maintenance and users staffs indicated that they felt the data in the universe file to be quite accurate. Field checks of the data in the HPMS samples have been done by the headquarters inventory staff, and indicate that the data accurately represented the cross sections of the roadway. As is the case for most states, the percent trucks assigned to each section are not as accurate as would be desired.
We also attempted to determine if there was consistency between variables for similar variables found in the Inventory File. In general, there was. For example, speed limit appeared to be consistent with functional class. Median type (including undivided) and median width were quite consistent in terms of miles in each category.
There are two variables related to urban/rural location, with some differences indicated in the mileage that might be considered "rural" or "urban." One is "Population Group" (including "unincorporated"), and the second is "Urban/Rural Designated by Population." “Population Group” variable indicates that about 93% of the roads fall within rural areas, whereas “Urban/Rural Designated Population” indicates about 89% of the roads fall within rural areas. Conversations with the DOT staff indicated that each is based on slightly different definitions. "Population Group" is based solely on whether the road segment is inside an incorporated town or city, regardless of city size. The second variable, "Urban/Rural Designation by Population" is based on a combination of incorporation and urbanized area classifications. In short, the two define slightly different categories, and, according to the DOT staff, neither is considered to be a better measure of the overall nature of the roadway (i.e., design, roadside, nature of surrounding area, etc.).
In general, the roadway inventory file contains a large amount of mileage when compared to other state systems, and the data in the file appear to be quite accurate.As indicated above, the basic AADT and percent truck information is included on the Roadway Inventory File. This information comes from the NCDOT traffic monitoring system, which consists of a Continuous Count Program and a Coverage Count Program. The Continuous Count Program involves the continuous 24-hour collection of volume, vehicle classification, and truck weight data at a sample of locations across the state. Continuous count sites are located on all types of highway facilities in all regions of the state. Approximately 90 Automatic Traffic Recording stations collect volume data (ATRs) and 50 Weigh-In-Motion stations collect vehicle classification and truck weight data (WIMs). Continuous counts are screened for data quality and used to generate seasonal factors and statistics to support the Coverage Count program.
The Coverage Count Program involves the collection of short-term volume and vehicle classification counts to provide “coverage” of the major highway systems in North Carolina. Data are collected for 48 hours at each station at periodic intervals. There are approximately 40,000 volume-monitoring stations and 570 vehicle classification-monitoring stations. Using information from the Continuous Count stations, these volume counts are factored to generate Annual Average Daily Traffic (AADT) estimates. This data are screened for consistency with historic trends at a station (temporal) and consistency between neighboring stations (spatial). Interstate mainline counts are collected every 5 to 8 interchanges and ramp counts are collected at all interchanges. Mainline interstate counts are factored to generate AADTs at these stations. AADT estimates on intervening segments are calculated by balancing the ramp volumes at interchanges between mainline count stations. Approximately 25,000 monitoring stations are updated annually including all interstate stations. All stations except interstates within major urban planning areas are updated biennially, half of the urban areas being updated each year. All primary route stations in rural areas are updated annually. Stations on rural secondary routes are updated biennially, approximately half of the stations each year. There is comprehensive volume coverage of major routes but only key secondary routes are monitored. AADT data are used in Highway Performance Monitoring System (HPMS) reporting through the Roadway Inventory File. Truck statistics in this file are updated on an ad hoc basis.
Vehicle classification counts are screened for data quality and compared to historic values at the same station. This data are used primarily to generate statewide averages by functional class of highway to meet HPMS reporting requirements. The existing monitoring stations support a sample based analysis and a comprehensive coverage of truck data are not available at this time. Vehicle classification coverage counts are updated on a three-year cycle.
Finally, the Projects Program within NC DOT provides traffic data collection services to support urban transportation modeling studies, traffic forecasting for TIP projects, and other transportation engineering studies. Services provided include the collection of daily, hourly, and vehicle classification counts using portable counters and turning movement and vehicle classification counts collected manually. Traffic counts are requested to provide more detailed traffic flows within a study area. A study will typically require a variety of data types collected at numerous locations. Counts are screened for data quality and consistency and are factored when requested. Approximately 1,400 portable counts and 600 manual counts are collected annually within the program. Major external origin and destination studies and travel time studies are conducted infrequently to provide more detailed information. (It is noted that HSIS does not capture these counts, since there is no NC intersection inventory file. However, the counts could be used if such a file is developed in the future.)
Examination of the traffic related variables in the HSIS Inventory File indicate that AADT is present for 99.9% of the sections. However, there are problems with the two variables related to percent of trucks. The data related to “percent trucks at peak” is uncoded for 60% of the mileage for all years. The variable for “total truck percent” is uncoded for approximately 90% of the mileage for pre-2000 years, but is present for almost all mileage after 2000. Conversations with DOT staff indicated that this is the result of the fact that these variables are only coded if there is fairly high confidence in the percentages. This would occur if a classification count had been done on the section (as in an HPMS sample section), or on an adjacent or nearby section. Thus, while the data present should be fairly accurate, it is missing for a large number of miles in years until 2000.As noted above, the accident data are subdivided into three subfiles -- accident, vehicle and occupant. These subfiles can be linked together using the "case number" variable, which includes the accident year (i.e., CASENO) present in each of the three files. When linking the occupant subfile, the additional linking variable "vehicle number" (i.e., VEHNO) must match so that the occupants are associated with the vehicle in which they were traveling. To link the Vehicle subfile with the Accident alone, first sort both subfiles by case number. To link the Occupant file with the other two subfiles, first sort both the Vehicle subfile and Occupant subfile by case number and vehicle position number. Next sort the Accident subfile by case number. Alternatively, the separate subfiles can be linked by specifying an SQL JOIN operation with the constraining condition that case number and vehicle number from each table are equal. SQL processing does not require the data to be pre-sorted and the output will not be in any particular sort order unless ORDER BY is specified.
The Accident subfile can then be linked with the Roadway Inventory File using information related to county, route number, and milepost on the route. The actual linkage variables on the Accident file that are used in the merging operation are COUNTY, ROUTE and MILEPOST.
To prepare the Accident subfile for linking with the Roadway Inventory File using a SAS data step process, the analyst must sort both the Accident and the Roadway File into location order (by COUNTY, ROUTE and MILEPOST on the Accident file and by COUNTY, RTE_NBR and BEGMP on the Roadway File). For the alternative SQL join, the analyst must specify an exact match on COUNTY, an exact match on ROUTE with RTE_NBR and a range match where MILEPOST occurs between BEGMP and ENDMP. (Programs to accomplish this merging and division are documented in the HSIS Programmer's Guidebook, available at FHWA.)
Finally, where appropriate and possible, a format, which defines categories within a given variable, has been developed for HSIS SAS variables. These categories are shown in the pages below. These formats have been saved in a format library, which can be provided to the user. As a naming convention, the "format name" is the same as the variable name; with the only exception being for certain character variables (in contrast with numeric variables). More specifically, a SAS format name has to be preceded by a "$" if the variable is character in nature. There is an 8-character length limit on both variable name and format name. In cases where the variable name is already eight characters in length, the addition of the preceding "$" would make the format name one character too long. In these cases, the format name is the same as the variable name except the final character of the variable name is dropped.
State liaison and accident data contact – Kevin Lacy (919-733-5467, jklacy@dot.state.nc.us) – Mr. Lacey, the NC State Traffic Engineer, is the primary contact when questions arise concerning the data. In his absence, questions are submitted to Terry Hopkins, State Traffic Safety Engineer (919-733-5418, thopkins@dot.state.nc.usk), Brian Mayhew, Manager, Traffic Safety Systems Section (919-715-7818, bmayhew@dot.state.nc.us) and Jeff Jaeger, Traffic Safety Project Engineer (919-733-3915, jjaeger@dot.state.nc.us).
Roadway Inventory information -- L. C. Smith (919-212-6001) -- Mr. Smith is the Director of the Geographic Information Systems (GIS) Unit, and is the contact person for questions related to the specifics of the Roadway Inventory File. His office staff is responsible for all aspects of the basic inventory information and file preparation.
Traffic Counts – Kent Taylor (919-212-4550, kltaylor@dot.state.nc.us) – Mr. Taylor is the Supervisor of the State Traffic Survey Group within the NC Division of Highways. He is responsible for the statewide traffic count program. He forwards AADT and truck count information to Mr. Smith for inclusion in the Inventory File.
| VARIABLE NAME | VARIABLE DESCRIPTION | FILE | VARIABLE TYPE | FORMAT PAGE NO |
|---|---|---|---|---|
| AADT | AVER ANNUAL DAILY TRAFFIC | Roadway | NUM (8) | 103 |
| AADT_YR | YEAR OF ADT | Roadway | CHAR (2) | 103 |
| ACC_DATE | ACCIDENT DATE-MMDDYY | Accident | NUM (8) | 34 |
| ACCESS | ACCESS CONTROL | Accident | NUM (8) | 34 |
| ACCESS | ACCESS CONTROL | Roadway | CHAR (1) | 103 |
| ACCTYPE | FIRST HARMFUL EVENT | Accident | NUM (8) | 34 |
| ACCYR | ACCIDENT YEAR | Accident | CHAR (4) | 35 |
| ACTION | DRIVER CHARGED WITH VIOL | Vehicle | CHAR (1) | 62 |
| ADD_DAMG | ADDITIONAL PROPERTY DAMAGE | Accident | NUM (8) | 35 |
| AGE | OCCUPANT AGE | Occupant | NUM (8) | 95 |
| AGENCY | INVESTIGATING AGENCY | Accident | CHAR (1) | 36 |
| AIR_SW | AIRBAG SWITCH STATUS | Occupant | NUM (8) | 95 |
| AIRBAGS | AIR BAGS PRESENT IN VEH | Vehicle | CHAR (1) | 62 |
| AIRDEPL | AIRBAGS DEPLOYED DURING CRASH | Vehicle | CHAR (1) | 96 |
| AIRDEPL | AIRBAG DEPLOYED | Occupant | NUM (8) | 62 |
| ALC_DRUG | ALCOHOL/DRUG IN ACC | Vehicle | NUM (8) | 62 |
| ALCFLAG | ALCOHOL/DRUGS IN ACC | Accident | CHAR (1) | 36 |
| ALCFLAG | ALCOHOL FLAG | Vehicle | CHAR (1) | 63 |
| AMB_TIME | TIME OF AMBULANCE REQUEST | Accident | CHAR (4) | 36 |
| AMBUL | AMBULANCE REQUESTED | Accident | CHAR (1) | 36 |
| AMTDAMG | AMOUNT OF DAMAGE TO VEH | Vehicle | NUM (8) | 63 |
| AREATYPE | AREA TYPE | Roadway | CHAR (1) | 103 |
| AXLE_NBR | COMMERCIAL CARRIER AXLES | Vehicle | NUM (8) | 63 |
| AXLES | NUMBER OF AXLES FOR TRL#1 | Vehicle | NUM (8) | 64 |
| AXLES2 | NUMBER OF AXLES FOR TRL#2 | Vehicle | NUM (8) | 64 |
| BEGMP | BEGIN MILEPOST | Roadway | NUM (8) | 103 |
| BIKEFLAG | BICYCLE IN ACC | Accident | CHAR (1) | 36 |
| BIKEFLAG | BICYCLE FLAG | Vehicle | CHAR (1) | 64 |
| BODY | CARGO BODY TYPE | Vehicle | NUM (8) | 64 |
| CASENO | YEAR + CASE NUMBER | Accident | NUM (8) | 37 |
| CASENO | NC ACCIDENT NUMBER WITH YR | Vehicle | NUM (8) | 96 |
| CASENO | NC ACCIDENT NUMBER WITH YR | Occupant | NUM (8) | 64 |
| CC_CITY | COMMERCIAL CARRIER CITY | Vehicle | CHAR (22) | 64 |
| CC_STATE | COMMERCIAL CARRIER STATE | Vehicle | CHAR (2) | 65 |
| CC_ZIP | COMMERCIAL CARRIER ZIP CODE | Vehicle | CHAR (9) | 65 |
| CCB_CITY | COMM CARR BUSINESS CITY | Vehicle | CHAR (2) | 65 |
| CCB_STAT | COMM CARR BUSINESS STATE | Vehicle | NUM (8) | 65 |
| CDL_IND | CDL INDICATOR | Vehicle | CHAR (1) | 65 |
| VARIABLE NAME | VARIABLE DESCRIPTION | FILE | VARIABLE TYPE | FORMAT PAGE NO |
|---|---|---|---|---|
| CITY | CITY/TOWN CODE (INCL CO) | Accident | NUM (8) | 37 |
| CNT_SEAT | NUMBER OF SEATS OCCUPIED | Vehicle | CHAR (1) | 65 |
| CNTY_RTE | COUNTY ROUTE NUMBER | Accident | CHAR (10) | 37 |
| CNTYRTE | COUNTY ROUTE NUMBER | Roadway | CHAR (10) | 104 |
| COMMFLAG | COMMERCIAL VEHICLE IN ACC | Accident | CHAR (1) | 37 |
| CONTRIB1 | VIOL/CONTRIBUT FACTOR #1 | Vehicle | NUM (8) | 65 |
| CONTRIB2 | VIOL/CONTRIBUT FACTOR #2 | Vehicle | NUM (8) | 65 |
| CONTRIB3 | VIOL/CONTRIBUT FACTOR #3 | Vehicle | NUM (8) | 65 |
| CONTRIB4 | VIOL/CONTRIBUT FACTOR #4 | Vehicle | NUM (8) | 65 |
| CONTRIB5 | VIOL/CONTRIBUT FACTOR #5 | Vehicle | NUM (8) | 65 |
| COUNTY | NC COUNTY NUMBER | Accident | NUM (8) | 37 |
| COUNTY | COUNTY | Roadway | CHAR (2) | 104 |
| CROSSMED | CROSS MEDIAN | Vehicle | CHAR (1) | 66 |
| DAMSEV | TAD#1 SEVERITY | Vehicle | CHAR (1) | 67 |
| DAMSEV2 | TAD#2 SEVERITY | Vehicle | CHAR (1) | 67 |
| DAMSEV3 | TAD#3 SEVERITY | Vehicle | CHAR (1) | 67 |
| DAY | DAY OF THE MONTH | Accident | CHAR (2) | 38 |
| DEPT_CDE | REPORTING DEPARTMENT CODE | Accident | CHAR (9) | 38 |
| DESC_ | ROAD DESCRIPTION | Roadway | CHAR (10) | 105 |
| DEVELOP | DEVELOPMENT AMOUNT | Accident | NUM (8) | 38 |
| DHRVOL | DESIGN HOUR VOLUME | Roadway | CHAR (2) | 105 |
| DIR_TRVL | DIRECT OF TRAVEL ON ROUTE | Vehicle | CHAR (2) | 67 |
| DIV | HIGHWAY DIVISION | Roadway | CHAR (2) | 105 |
| DRG_RES | DRIVER ALC/DRUG TEST RESULT | Vehicle | NUM (8) | 67 |
| DRG_SUSP | DRIVER ALC/DRUG SUSPECTED | Vehicle | NUM (8) | 67 |
| DRSTATE | OUT OF STATE DRIVERS LIC | Vehicle | CHAR (1) | 68 |
| DRV_AGE | DRIVER/PEDEST AGE | Vehicle | CHAR (3) | 68 |
| DRV_BAC | DRIVER BLOOD ALCOHOL IN % | Vehicle | NUM (8) | 68 |
| DRV_CITY | DRIVER CITY | Vehicle | CHAR (22) | 68 |
| DRV_DOB | DRIVER DATE OF BIRTH | Vehicle | NUM (8) | 69 |
| DRV_INJ | DRIVER/PEDESTRIAN INJURY | Vehicle | CHAR (1) | 69 |
| DRV_RACE | DRIVER/PEDEST RACE | Vehicle | CHAR (1) | 69 |
| DRV_REST | DRIVER RESTRAINT USAGE | Vehicle | CHAR (2) | 69 |
| DRV_SEAT | DRIVER/PEDEST SEAT POS | Vehicle | CHAR (1) | 70 |
| DRV_SEX | DRIVER/PEDEST SEX | Vehicle | CHAR (1) | 70 |
| DRV_ZIP | DRIVER ZIP CODE | Vehicle | CHAR (9) | 70 |
| EJECT | EJECTION | Occupant | NUM (8) | 96 |
| EMERGUSE | EMERGENCY VEHICLE USE | Vehicle | NUM (8) | 70 |
| EMS_DES | EMERGENCY MEDICAL SERVICE | Occupant | CHAR (50) | 96 |
| ENDMP | ENDING MILEPOST | Roadway | NUM (8) | 105 |
| VARIABLE NAME | VARIABLE DESCRIPTION | FILE | VARIABLE TYPE | FORMAT PAGE NO |
|---|---|---|---|---|
| EVENT1 | SEQUENCE OF EVENTS 1 | Vehicle | NUM (8) | 70 |
| EVENT2 | SEQUENCE OF EVENTS 2 | Vehicle | NUM (8) | 70 |
| EVENT3 | SEQUENCE OF EVENTS 3 | Vehicle | NUM (8) | 70 |
| EVENT4 | SEQUENCE OF EVENTS 4 | Vehicle | NUM (8) | 70 |
| EXPR_DT | LICENSE EXPIRATION DATE | Vehicle | NUM (8) | 72 |
| FIRE | POSTCRASH FIRE | Vehicle | NUM (8) | 72 |
| FRM_RD | FROM ROAD | Accident | CHAR (8) | 39 |
| FRMRD_CL | FROM ROAD CLASS | Accident | CHAR (4) | 39 |
| FROM_DIR | DIRECTION FROM FRM_RD | Accident | CHAR (2) | 39 |
| FUNC_CLS | FUNCTIONAL CLASS | Roadway | CHAR (2) | 105 |
| FUNC_ST | FUNCTIONAL CLASS (STATE) | Roadway | CHAR (1) | 105 |
| GOV_OWN | GOV OWNED VEH INDICATOR | Vehicle | CHAR (1) | 72 |
| GVWR_WGT | COMM CARR GROSS VEH WEIGHT | Vehicle | NUM (8) | 72 |
| HAZ_NUM1 | 1 DIGIT HAZMAT NUM PLACARD | Vehicle | NUM (8) | 72 |
| HAZ_NUM4 | 4 DIGIT HAZMAT NUM PLACARD | Vehicle | CHAR (4) | 72 |
| HAZ_PLAC | HAZMAT PLACARD INDICATOR | Vehicle | CHAR (1) | 73 |
| HAZFLAG | HAZMAT VEHICLE IN ACC | Accident | CHAR (1) | 39 |
| HAZMAT | HAZARDOUS CARGO | Vehicle | CHAR (1) | 73 |
| HITRUN | HIT AND RUN ACC | Accident | CHAR (1) | 40 |
| HOUR | HOUR | Accident | CHAR (4) | 40 |
| HPMS1 | HPMS SAMPLE ID | Roadway | CHAR (6) | 106 |
| IMPACTFT | DIST TRAVEL AFTER IMPACT | Vehicle | NUM (8) | 73 |
| IMPACTSP | IMPACT SPEED | Vehicle | NUM (8) | 73 |
| IMPROVE1 | TYPE OF RECENT IMPROVEMENT | Roadway | CHAR (2) | 106 |
| INJ | OCCUPANT INJURY | Occupant | NUM (8) | 96 |
| INSURED | INSURANCE INDICATOR | Vehicle | CHAR (1) | 74 |
| INTOXC | DRIVER INTOXICATION GROUP | Vehicle | NUM (8) | 74 |
| INTSTMP | INTERSTATE MILEPOST | Roadway | CHAR (5) | 106 |
| INV_CNTL | INVENTORY CONTROL | Roadway | CHAR (1) | 106 |
| L_PERMIT | LEARNER PERMIT | Vehicle | CHAR (1) | 74 |
| LENGTRL | LENGTH OF TRAILER #1,IN FT | Vehicle | NUM (8) | 74 |
| LENGTRL2 | LENGTH OF TRAILER #2,IN FT | Vehicle | NUM (8) | 74 |
| LIC_IND | DRIVER LICENSE INDICATOR | Vehicle | CHAR (1) | 75 |
| LIC_STAT | LICENSE STATE | Vehicle | CHAR (2) | 75 |
| LICRESTR | RESTRICT ON DRIV LICENSE | Vehicle | CHAR (2) | 75 |
| LICTYPE | TYPE OF DRIVERS LICENSE | Vehicle | CHAR (1) | 75 |
| LIGHT | LIGHT CONDITION | Accident | NUM (8) | 40 |
| LISTCNTL | LIST CONTROL | Roadway | CHAR (1) | 106 |
| LOC_TYPE | ACCIDENT LOCATION TYPE | Accident | NUM (8) | 41 |
| LOCALITY | DEVELOPMENT TYPE | Accident | NUM (8) | 41 |
| VARIABLE NAME | VARIABLE DESCRIPTION | FILE | VARIABLE TYPE | FORMAT PAGE NO |
|---|---|---|---|---|
| LSHL_TYP | LEFT SHOULDER TYPE | Roadway | CHAR (2) | 107 |
| LSHLDWID | LEFT SHOULDER WIDTH | Roadway | NUM (8) | 107 |
| LT_PARK | LEFT PEAK PARK | Roadway | CHAR (1) | 107 |
| MAKE | VEHICLE MAKE | Vehicle | CHAR (2) | 75 |
| MAKENAME | VEHICLE MAKE NAME | Vehicle | CHAR (20) | 76 |
| MANEUVER | VEH MANEUVER/PEDEST ACTION | Vehicle | NUM (8) | 76 |
| MCFLAG | MOTORCYCLE IN ACC | Accident | CHAR (1) | 42 |
| MEANS | MEANS OF INVOLVEMENT | Accident | CHAR (1) | 42 |
| MED_TYPE | MEDIAN TYPE | Roadway | CHAR (1) | 108 |
| MEDWID | MEDIAN WIDTH TOTAL | Roadway | NUM (8) | 108 |
| MHARM_AC | MOST HARMFUL EVENT | Accident | NUM (8) | 42 |
| MILEPOST | MILEPOST | Accident | NUM (8) | 43 |
| MISCACT1 | MISCELLANEOUS ACTION | Vehicle | CHAR (2) | 76 |
| MONTH | MONTH OF ACCIDENT | Accident | CHAR (2) | 43 |
| MOPEDFLG | MOPED IN ACCIDENT | Accident | CHAR (1) | 43 |
| MOSTHARM | MOST HARMFUL EVENT | Vehicle | NUM (8) | 77 |
| MUNI_DIR | DIRECTION FROM MUNICIPALITY TO ACC | Accident | CHAR (2) | 43 |
| MUNI_DIS | DISTANCE FROM MUNICIPALITY IN MILES | Accident | NUM (8) | 44 |
| MVMT | MILLION VEHICLE MILLIONS OF TRAVEL | Accident | NUM (8) | 44 |
| MVMT | MILLION VEHICLE MILES TRAVELLED | Roadway | NUM (8) | 108 |
| NBR_LANE | NUMBER OF LANES (CRASH RE) | Accident | NUM (8) | 44 |
| NEARTOWN | IN OR NEAR TOWN | Accident | NUM (8) | 44 |
| NHS | NATIONAL HIGHWAY SYSTEM | Roadway | CHAR (1) | 108 |
| NO_LANES | NUMBER OF LANES- TOTAL | Roadway | CHAR (1) | 108 |
| NON_REP | NON-REPORTABLE | Accident | NUM (8) | 44 |
| NONMTCNT | NON-MOTORIST COUNT | Accident | NUM (8) | 44 |
| NUM_A | TOTAL A INJURIES IN VEH | Vehicle | CHAR (2) | 78 |
| NUM_B | TOTAL B INJURIES IN VEH | Vehicle | CHAR (2) | 78 |
| NUM_C | TOTAL C INJURIES IN VEH | Vehicle | CHAR (2) | 78 |
| NUM_K | TOTAL KILLED IN VEHICLE | Vehicle | CHAR (2) | 78 |
| NUM_OCCS | TOTAL OCCUPANTS IN VEH | Vehicle | CHAR (2) | 78 |
| NUM_POCS | NO OF POINTS OF CONTACT | Vehicle | CHAR (1) | 79 |
| NUM_TADS | NUMBER OF TAD CODES | Vehicle | CHAR (1) | 79 |
| NUM_UNIT | NUMBER OF UNITS | Accident | NUM (8) | 45 |
| NUMINJ | TOT INJURED IN VEH (K+A+B+C) | Vehicle | CHAR (2) | 79 |
| NUMVEHS | NUMBER OF VEH+PED+BIKE | Accident | NUM (8) | 45 |
| NUMVIOLS | NUM OF VIOLS INDICATED | Vehicle | CHAR (1) | 79 |
| OBJECT1 | TYPE OF OBJECT STRUCK | Vehicle | CHAR (2) | 79 |
| OFFCR_ST | REPORTING OFFICER STATE | Accident | CHAR (2) | 45 |
| ON_RD | ON ROAD | Accident | CHAR (8) | 45 |
| VARIABLE NAME | VARIABLE DESCRIPTION | FILE | VARIABLE TYPE | FORMAT PAGE NO |
|---|---|---|---|---|
| ON_RD | ON ROAD | Vehicle | CHAR (8) | 80 |
| ONRD_CL | ON ROAD CLASS | Accident | CHAR (4) | 45 |
| ONRD_CL | ON ROAD CLASS | Vehicle | CHAR (4) | 80 |
| OTH_UNIT | OTHER UNIT TYPE | Vehicle | CHAR (20) | 81 |
| OUTSTATE | OUT OF STATE VEH REGIS | Vehicle | CHAR (1) | 81 |
| OWN_CITY | VEHICLE OWNER CITY | Vehicle | CHAR (22) | 81 |
| OWN_STAT | VEHICLE OWNER STATE | Vehicle | CHAR (2) | 81 |
| OWN_ZIP | VEHICLE OWNER ZIP CODE | Vehicle | CHAR (9) | 81 |
| OWNERTYP | OWNER CATEGORY | Vehicle | CHAR (3) | 81 |
| PARK_VEH | INDICATOR OF PARKED VEH | Vehicle | CHAR (1) | 81 |
| PATROLAC | PATROL AREA CODE | Accident | CHAR (2) | 45 |
| PAVECOND | PAVEMENT CONDITION | Roadway | CHAR (2) | 109 |
| PCT_TRK1 | PERCENT TRUCKS | Roadway | CHAR (2) | 109 |
| PEAK_TRK | PERCENT TRUCKS AT PEAK | Roadway | CHAR (1) | 109 |
| PED_LOC | NON-MOTORIST LOCATION | Vehicle | NUM (8) | 82 |
| PEDACT | NON-MOTORIST ACTION | Vehicle | NUM (8) | 82 |
| PEDCONT1 | CONTRIB CIRCUM NON-MOT 1 | Vehicle | NUM (8) | 82 |
| PEDCONT2 | CONTRIB CIRCUM NON-MOT 2 | Vehicle | NUM (8) | 82 |
| PEDFLAG | PEDESTRIAN IN ACC | Accident | CHAR (1) | 46 |
| PEDFLAG | PEDESTRIAN IN ACCIDENT | Vehicle | CHAR (1) | 83 |
| PEDHITBY | PUPIL PEDEST STRUCK BY (SCHLBUS CRASH) | Vehicle | CHAR (1) | 83 |
| PHYSCOND | PHYSICAL COND OF DRIVER | Vehicle | NUM (8) | 83 |
| PLOTQUAL | QUALITY OF MILEPOST | Accident | CHAR (1) | 46 |
| POP_GRP | CITY POPULATION IN 1000 | Accident | NUM (8) | 46 |
| POP_GRP | POPULATION GROUP | Roadway | CHAR (1) | 109 |
| PROPDAM | TOTAL PROPERTY DAMAGE | Accident | NUM (8) | 46 |
| PRSN_CTY | PERSON COUNTY | Occupant | CHAR (22) | 96 |
| PRSN_DOB | PERSON DATE OF BIRTH | Occupant | NUM (8) | 97 |
| PRSN_NBR | PERSON NUMBER | Occupant | NUM (8) | 97 |
| PRSN_ST | PERSON STATE | Occupant | CHAR (2) | 97 |
| PRSN_TYP | PERSON TYPE | Occupant | NUM (8) | 97 |
| PRSN_ZIP | PERSON ZIP CODE | Occupant | CHAR (9) | 97 |
| PTCONT1 | POINT OF CONTACT #1 | Vehicle | CHAR (2) | 84 |
| PTCONT2 | POINT OF CONTACT #2 | Vehicle | CHAR (2) | 84 |
| PTCONT3 | POINT OF CONTACT #3 | Vehicle | CHAR (2) | 84 |
| PTCONT4 | POINT OF CONTACT #4 | Vehicle | CHAR (2) | 84 |
| PTCONT5 | POINT OF CONTACT #5 | Vehicle | CHAR (2) | 84 |
| PTCSTAT | PORTABLE TRAFFIC COUNTER | Roadway | CHAR (8) | 110 |
| PVA | PUBLIC VEHICLE AREA | Accident | CHAR (2) | 47 |
| RACE | OCCUPANT RACE | Occupant | NUM (8) | 97 |
| VARIABLE NAME | VARIABLE DESCRIPTION | FILE | VARIABLE TYPE | FORMAT PAGE NO |
|---|---|---|---|---|
| RD_CHAR1 | ROAD CHARACTER | Accident | NUM (8) | 47 |
| RD_CONF | ROAD CONFIGURATION | Accident | NUM (8) | 47 |
| RD_PAVE | TYPE OF ROAD SURFACE (REP) | Accident | NUM (8) | 48 |
| RD2OBJST | DISTANCE TO OBJECT STRUCK | Vehicle | NUM (8) | 85 |
| RDSURF | SURFACE CONDITION | Accident | NUM (8) | 48 |
| RECCONT | RECORD CONTINUATION CODE | Roadway | CHAR (1) | 110 |
| REFDISFT | DIST FROM FRM_RD IN FEET | Accident | NUM (8) | 49 |
| REFDISMI | DIST FROM FRM_RD IN MILES | Accident | NUM (8) | 49 |
| REGION | REGION OF IMPACT | Vehicle | CHAR (1) | 85 |
| REL_RD | RELATION TO ROADWAY | Accident | NUM (8) | 49 |
| REPORT | REPORTABLE STATUS | Accident | CHAR (1) | 49 |
| REST1 | OCCUPANT RESTRAINT | Occupant | NUM (8) | 98 |
| RMP_SVRD | RAMP OR SERVICE ROAD | Accident | NUM (8) | 49 |
| ROAD_CLS | ROAD CLASSIFICATION | Accident | NUM (8) | 50 |
| ROADCNT1 | ROADWAY CONTRIBUT CIRCUM 1 | Accident | NUM (8) | 50 |
| ROADCNT2 | ROADWAY CONTRIBUT CIRCUM 2 | Accident | NUM (8) | 50 |
| RODWYCLS | ROAD WAY CLASS | Accident | CHAR (2) | 50 |
| RODWYCLS | ROAD WAY CLASS VARIABLE | Roadway | CHAR (2) | 110 |
| ROLLOVER | VEHICLE ROLLOVER | Vehicle | CHAR (1) | 85 |
| ROLLPTCT | ROLLOVER, POINT OF CONTACT | Vehicle | NUM (8) | 85 |
| ROLLTAD | ROLLOVER, TAD SEVERITY | Vehicle | NUM (8) | 85 |
| ROUGH | PAVEMENT ROUGHNESS | Roadway | CHAR (3) | 110 |
| ROW | RIGHT OF WAY | Roadway | CHAR (2) | 110 |
| RRX_NUM | RAIL ROAD CROSSING NUMBER | Accident | CHAR (7) | 51 |
| RRXFLAG | RAILROAD CROSS NOT INDICATED | Accident | CHAR (1) | 51 |
| RSHL_TYP | RIGHT SHOULDER TYPE | Roadway | CHAR (2) | 110 |
| RSHLDWID | RIGHT SHOULDER WIDTH | Roadway | NUM (8) | 111 |
| RT_PARK | RIGHT PEAK PARK | Roadway | CHAR (1) | 111 |
| RTE_NBR | MILEPOSTED ROUTE | Accident | CHAR (8) | 51 |
| RTE_NBR | ROUTE INVENTORIED | Roadway | CHAR (8) | 111 |
| RTE_TYPE | ROUTE TYPE (1ST DIGIT OF RTE_NBR) | Roadway | CHAR (1) | 111 |
| RULURBID | RURAL URBAN IDENTIFICATION | Roadway | CHAR (2) | 112 |
| RURURB | RURAL-URBAN IDENTIFICATION | Accident | CHAR (1) | 51 |
| SCENIC | SCENIC BYWAY | Roadway | CHAR (1) | 112 |
| SCH_BUS1 | SCHOOL BUS CONTACT VEH | Vehicle | NUM (8) | 85 |
| SCH_BUS2 | SCHOOL BUS NON-CONTACT VEH | Vehicle | NUM (8) | 86 |
| SCHBUS | SCHOOL BUS INVOLVED IN ACC | Accident | CHAR (1) | 51 |
| SEATPOS | SEATING POSITION | Occupant | NUM (8) | 98 |
| SEG_LNG | SECTION LENGTH IN MILES | Roadway | NUM (8) | 112 |
| VARIABLE NAME | VARIABLE DESCRIPTION | FILE | VARIABLE TYPE | FORMAT PAGE NO |
|---|---|---|---|---|
| SEVERITY | WORST INJURY IN ACC | Accident | CHAR (1) | 51 |
| SEX | OCCUPANT SEX | Occupant | NUM (8) | 98 |
| SIGHTDIS | SIGHT DISTANCE | Roadway | CHAR (2) | 112 |
| SOB_TEST | CHEMICAL TEST GIVEN | Vehicle | NUM (8) | 86 |
| SPD_GRP | COMPUTED SPEED OF ACCIDENT | Accident | CHAR (1) | 51 |
| SPD_LIMT | SPEED LIMIT | Roadway | CHAR (2) | 112 |
| SPDLIM | POSTED SPEED LIMIT | Vehicle | NUM (8) | 86 |
| SPEC_SYS | SPECIAL SYSTEM | Roadway | CHAR (1) | 112 |
| SPILL | HAZARDOUS CARGO SPILL | Vehicle | CHAR (1) | 86 |
| STATE_SY | STATE HIGHWAY SYSTEM | Roadway | CHAR (1) | 113 |
| SURF_TYP | SURFACE TYPE | Roadway | CHAR (2) | 113 |
| SURF_WID | SURFACE WIDTH TOTAL | Roadway | NUM (8) | 113 |
| TERRAIN | TERRAIN | Roadway | CHAR (1) | 113 |
| TICKET1 | CITATION ISSUED TO SOMEONE IN ACCIDENT | Accident | CHAR (1) | 52 |
| TICKET2 | CITATION ISSUED TO SOMEONE IN ACCIDENT | Accident | CHAR (1) | 52 |
| TIME | TIME OF DAY (24 HOUR) | Accident | CHAR (4) | 52 |
| TIRESKID | TIRE IMPRESSIONS IN FEET | Vehicle | NUM (8) | 87 |
| TO_DIR | DIRECTION TOWARD TO_RD | Accident | CHAR (2) | 53 |
| TO_RD | TOWARD ROAD | Accident | CHAR (8) | 53 |
| TORD_CL | TOWARD ROAD CLASS | Accident | CHAR (4) | 53 |
| TOT_KILL | TOTAL KILLED IN ACC | Accident | NUM (8) | 53 |
| TOTAINJ | TOTAL A INJURIES IN ACC | Accident | NUM (8) | 53 |
| TOTBINJ | TOTAL B INJURIES IN ACC | Accident | NUM (8) | 54 |
| TOTCINJ | TOTAL C INJURIES IN ACC | Accident | NUM (8) | 54 |
| TOTLENG | TOT LENGTH OF TRAILER(S) IN FEET | Vehicle | CHAR (3) | 87 |
| TOWAWAY | VEHICLE DRIVEABLE | Vehicle | NUM (8) | 87 |
| TOWED_BY | TOWED BY | Vehicle | CHAR (50) | 87 |
| TOWED_TO | TOWED TO | Vehicle | CHAR (50) | 87 |
| TOWN | TOWN | Roadway | CHAR (2) | 113 |
| TOWN_CD | DOT ASSIGNED TOWN CODE | Accident | NUM (8) | 54 |
| TRAPPED | TRAPPED | Occupant | NUM (8) | 98 |
| TRF_CNTL | TRAFFIC CONTROL TYPE | Accident | NUM (8) | 54 |
| TRF_OPER | TRAFFIC CONTROL OPERATING | Accident | NUM (8) | 54 |
| TRF_VIS | TRAFFIC CONTROL VISIBLE | Accident | CHAR (1) | 55 |
| TRFGROW | TRAFFIC GROWTH FACTOR | Roadway | NUM (8) | 113 |
| TRK_RTE | DESIGNATED TRUCK ROUTE | Roadway | CHAR (1) | 113 |
| TRL_TYPE | TRAILER TYPE | Vehicle | NUM (8) | 88 |
| TRL1_FLG | DATA PRESENT (TRAILER #1) | Vehicle | CHAR (1) | 88 |
| TRL2_FLG | DATA PRESENT (TRAILER #2) | Vehicle | CHAR (1) | 88 |
| VARIABLE NAME | VARIABLE DESCRIPTION | FILE | VARIABLE TYPE | FORMAT PAGE NO |
|---|---|---|---|---|
| TRNLNWD | TURN LANE WIDTH | Roadway | NUM (8) | 114 |
| TRT_FAC | TREATMENT FACILITY NAME | Occupant | CHAR (100) | 99 |
| TRVL_SPD | ESTIMATED ORIGINAL SPEED | Vehicle | NUM (8) | 88 |
| UNDEROVR | VEHICLE UNDERRIDE/OVERRIDE | Vehicle | NUM (8) | 89 |
| UNIT_TYP | UNIT TYPE | Vehicle | CHAR (1) | 89 |
| UPDATE_ | UPDATE | Roadway | CHAR (8) | 114 |
| URB_LOC | URBAN LOCATION | Roadway | CHAR (1) | 114 |
| URB_POP | RUR/URB DESIGNATED BY POP | Roadway | CHAR (1) | 114 |
| V_DAMAG2 | TAD#2 LOCATION | Vehicle | CHAR (2) | 89 |
| V_DAMAG3 | TAD#3 LOCATION | Vehicle | CHAR (2) | 89 |
| V_DAMAGE | TAD#1 (AREA OF DAMAGE) LOC | Vehicle | CHAR (2) | 89 |
| VEH_SEIZ | VEHICLE SEIZURE DWI | Vehicle | NUM (8) | 90 |
| VEHCOND1 | VEHICLE DEFECT | Vehicle | CHAR (1) | 90 |
| VEHNO | VEHICLE POSITION NUMBER | Vehicle | NUM (8) | 99 |
| VEHNO | VEHICLE POSITION NUMBER | Occupant | NUM (8) | 90 |
| VEHON | VEHICLE LOCATION BASED ON ROAD | Vehicle | CHAR (1) | 90 |
| VEHSEV | SEVERITY | Vehicle | NUM (8) | 90 |
| VEHTYPE | VEHICLE TYPE | Vehicle | NUM (8) | 90 |
| VEHYR | MODEL YEAR OF VEHICLE | Vehicle | NUM (8) | 91 |
| VIN | VEHICLE IDENTIFICATION NO | Vehicle | CHAR (17) | 91 |
| VIN_ID | VEHICLE IDENTIFICATION NO | Vehicle | CHAR (25) | 92 |
| VISION | VISION OBSTRUCTION | Vehicle | NUM (8) | 92 |
| WEATHER1 | WEATHER CONDITION 1 | Accident | NUM (8) | 55 |
| WEATHER2 | WEATHER CONDITION 2 | Accident | NUM (8) | 55 |
| WEEKDAY | DAY OF WEEK | Accident | CHAR (1) | 55 |
| WETHCONT | WEATHER CONTRIBUT TO ACC | Accident | NUM (8) | 55 |
| WIDTRL | WIDTH OF TRAILER #1 (IN) | Vehicle | NUM (8) | 92 |
| WIDTRL2 | WIDTH OF TRAILER #2 (IN) | Vehicle | NUM (8) | 92 |
| WORKZONE | WORK ZONE MARKED | Accident | NUM (8) | 55 |
| WTDSGSPD | WEIGHTED DESIGN SPEED | Roadway | CHAR (2) | 114 |
| WZ_ACT | WORK ZONE ACTIVITY | Accident | NUM (8) | 56 |
| WZ_AREA | WORK ZONE AREA | Accident | NUM (8) | 56 |
| WZ_LOC | WORK ZONE CRASH LOCATION | Accident | NUM (8) | 56 |
| Y_LINE | NON-MILEPOSTED CROSSING ROUTE LOCATION | Accident | CHAR (1) | 56 |
| YEAR | YEAR OF TRAFFIC COUNT | Roadway | NUM (8) | 114 |
| YR_IMPR1 | YEAR OF RECENT IMPROVEMENT | Roadway | CHAR (2) | 115 |
| YRADD | YEAR ADDED | Roadway | CHAR (2) | 115 |
| ZIP_ADR | REPORTING OFFICER ZIP CODE | Accident | CHAR (9) | 56 |
| VARIABLE NAME | VARIABLE DESCRIPTION | FILE | VARIABLE TYPE | FORMAT PAGE NO |
|---|---|---|---|---|
| ACC_DATE | ACCIDENT DATE-MMDDYY | Accident | NUM (8) | 34 |
| ACCESS | ACCESS CONTROL | Accident | NUM (8) | 34 |
| ACCTYPE | FIRST HARMFUL EVENT | Accident | NUM (8) | 34 |
| ACCYR | ACCIDENT YEAR | Accident | CHAR (4) | 35 |
| ADD_DAMG | ADDITIONAL PROPERTY DAMAGE | Accident | NUM (8) | 35 |
| AGENCY | INVESTIGATING AGENCY | Accident | CHAR (1) | 36 |
| ALCFLAG | ALCOHOL/DRUGS IN ACC | Accident | CHAR (1) | 36 |
| AMB_TIME | TIME OF AMBULANCE REQUEST | Accident | CHAR (4) | 36 |
| AMBUL | AMBULANCE REQUESTED | Accident | CHAR (1) | 36 |
| BIKEFLAG | BICYCLE IN ACC | Accident | CHAR (1) | 36 |
| CASENO | YEAR + CASE NUMBER | Accident | NUM (8) | 37 |
| CITY | CITY/TOWN CODE (INCL CO) | Accident | NUM (8) | 37 |
| CNTY_RTE | COUNTY ROUTE NUMBER | Accident | CHAR (10) | 37 |
| COMMFLAG | COMMERCIAL VEHICLE IN ACC | Accident | CHAR (1) | 37 |
| COUNTY | NC COUNTY NUMBER | Accident | NUM (8) | 37 |
| DAY | DAY OF THE MONTH | Accident | CHAR (2) | 38 |
| DEPT_CDE | REPORTING DEPARTMENT CODE | Accident | CHAR (9) | 38 |
| DEVELOP | DEVELOPMENT AMOUNT | Accident | NUM (8) | 38 |
| FRM_RD | FROM ROAD | Accident | CHAR (8) | 39 |
| FRMRD_CL | FROM ROAD CLASS | Accident | CHAR (4) | 39 |
| FROM_DIR | DIRECTION FROM FRM_RD | Accident | CHAR (2) | 39 |
| HAZFLAG | HAZMAT VEHICLE IN ACC | Accident | CHAR (1) | 39 |
| HITRUN | HIT AND RUN ACC | Accident | CHAR (1) | 40 |
| HOUR | HOUR | Accident | CHAR (4) | 40 |
| LIGHT | LIGHT CONDITION | Accident | NUM (8) | 40 |
| LOC_TYPE | ACCIDENT LOCATION TYPE | Accident | NUM (8) | 41 |
| LOCALITY | DEVELOPMENT TYPE | Accident | NUM (8) | 41 |
| MCFLAG | MOTORCYCLE IN ACC | Accident | CHAR (1) | 42 |
| MEANS | MEANS OF INVOLVEMENT | Accident | CHAR (1) | 42 |
| MHARM_AC | MOST HARMFUL EVENT | Accident | NUM (8) | 42 |
| MILEPOST | MILEPOST | Accident | NUM (8) | 43 |
| MONTH | MONTH OF ACCIDENT | Accident | CHAR (2) | 43 |
| MOPEDFLG | MOPED IN ACCIDENT | Accident | CHAR (1) | 43 |
| MUNI_DIR | DIRECTION FROM MUNICIPALITY TO ACC | Accident | CHAR (2) | 43 |
| MUNI_DIS | DISTANCE FROM MUNICIPALITY IN MILES | Accident | NUM (8) | 44 |
| MVMT | MILLION VEHICLE MILLIONS OF TRAVEL | Accident | NUM (8) | 44 |
| NBR_LANE | NUMBER OF LANES (CRASH RE) | Accident | NUM (8) | 44 |
| VARIABLE NAME | VARIABLE DESCRIPTION | FILE | VARIABLE TYPE | FORMAT PAGE NO |
|---|---|---|---|---|
| NEARTOWN | IN OR NEAR TOWN | Accident | NUM (8) | 44 |
| NON_REP | NON-REPORTABLE | Accident | NUM (8) | 44 |
| NONMTCNT | NON-MOTORIST COUNT | Accident | NUM (8) | 44 |
| NUM_UNIT | NUMBER OF UNITS | Accident | NUM (8) | 45 |
| NUMVEHS | NUMBER OF VEH+PED+BIKE | Accident | NUM (8) | 45 |
| OFFCR_ST | REPORTING OFFICER STATE | Accident | CHAR (2) | 45 |
| ON_RD | ON ROAD | Accident | CHAR (8) | 45 |
| ONRD_CL | ON ROAD CLASS | Accident | CHAR (4) | 45 |
| PATROLAC | PATROL AREA CODE | Accident | CHAR (2) | 45 |
| PEDFLAG | PEDESTRIAN IN ACC | Accident | CHAR (1) | 46 |
| PLOTQUAL | QUALITY OF MILEPOST | Accident | CHAR (1) | 46 |
| POP_GRP | CITY POPULATION IN 1000 | Accident | NUM (8) | 46 |
| PROPDAM | TOTAL PROPERTY DAMAGE | Accident | NUM (8) | 46 |
| PVA | PUBLIC VEHICLE AREA | Accident | CHAR (2) | 47 |
| RD_CHAR1 | ROAD CHARACTER | Accident | NUM (8) | 47 |
| RD_CONF | ROAD CONFIGURATION | Accident | NUM (8) | 47 |
| RD_PAVE | TYPE OF ROAD SURFACE (REP) | Accident | NUM (8) | 48 |
| RDSURF | SURFACE CONDITION | Accident | NUM (8) | 48 |
| REFDISFT | DIST FROM FRM_RD IN FEET | Accident | NUM (8) | 49 |
| REFDISMI | DIST FROM FRM_RD IN MILES | Accident | NUM (8) | 49 |
| REL_RD | RELATION TO ROADWAY | Accident | NUM (8) | 49 |
| REPORT | REPORTABLE STATUS | Accident | CHAR (1) | 49 |
| RMP_SVRD | RAMP OR SERVICE ROAD | Accident | NUM (8) | 49 |
| ROAD_CLS | ROAD CLASSIFICATION | Accident | NUM (8) | 50 |
| ROADCNT1 | ROADWAY CONTRIBUT CIRCUM 1 | Accident | NUM (8) | 50 |
| ROADCNT2 | ROADWAY CONTRIBUT CIRCUM 2 | Accident | NUM (8) | 50 |
| RODWYCLS | ROAD WAY CLASS | Accident | CHAR (2) | 50 |
| RRX_NUM | RAIL ROAD CROSSING NUMBER | Accident | CHAR (7) | 51 |
| RRXFLAG | RAILROAD CROSS NOT INDICATED | Accident | CHAR (1) | 51 |
| RTE_NBR | MILEPOSTED ROUTE | Accident | CHAR (8) | 51 |
| RURURB | RURAL-URBAN IDENTIFICATION | Accident | CHAR (1) | 51 |
| SCHBUS | SCHOOL BUS INVOLVED IN ACC | Accident | CHAR (1) | 51 |
| SEVERITY | WORST INJURY IN ACC | Accident | CHAR (1) | 51 |
| SPD_GRP | COMPUTED SPEED OF ACCIDENT | Accident | CHAR (1) | 51 |
| TICKET1 | CITATION ISSUED TO SOMEONE IN ACCIDENT | Accident | CHAR (1) | 52 |
| TICKET2 | CITATION ISSUED TO SOMEONE IN ACCIDENT | Accident | CHAR (1) | 52 |
| VARIABLE NAME | VARIABLE DESCRIPTION | FILE | VARIABLE TYPE | FORMAT PAGE NO |
|---|---|---|---|---|
| TIME | TIME OF DAY (24 HOUR) | Accident | CHAR (4) | 52 |
| TO_DIR | DIRECTION TOWARD TO_RD | Accident | CHAR (2) | 53 |
| TO_RD | TOWARD ROAD | Accident | CHAR (8) | 53 |
| TORD_CL | TOWARD ROAD CLASS | Accident | CHAR (4) | 53 |
| TOT_KILL | TOTAL KILLED IN ACC | Accident | NUM (8) | 53 |
| TOTAINJ | TOTAL A INJURIES IN ACC | Accident | NUM (8) | 53 |
| TOTBINJ | TOTAL B INJURIES IN ACC | Accident | NUM (8) | 54 |
| TOTCINJ | TOTAL C INJURIES IN ACC | Accident | NUM (8) | 54 |
| TOWN_CD | DOT ASSIGNED TOWN CODE | Accident | NUM (8) | 54 |
| TRF_CNTL | TRAFFIC CONTROL TYPE | Accident | NUM (8) | 54 |
| TRF_OPER | TRAFFIC CONTROL OPERATING | Accident | NUM (8) | 54 |
| TRF_VIS | TRAFFIC CONTROL VISIBLE | Accident | CHAR (1) | 55 |
| WEATHER1 | WEATHER CONDITION 1 | Accident | NUM (8) | 55 |
| WEATHER2 | WEATHER CONDITION 2 | Accident | NUM (8) | 55 |
| WEEKDAY | DAY OF WEEK | Accident | CHAR (1) | 55 |
| WETHCONT | WEATHER CONTRIBUT TO ACC | Accident | NUM (8) | 55 |
| WORKZONE | WORK ZONE MARKED | Accident | NUM (8) | 55 |
| WZ_ACT | WORK ZONE ACTIVITY | Accident | NUM (8) | 56 |
| WZ_AREA | WORK ZONE AREA | Accident | NUM (8) | 56 |
| WZ_LOC | WORK ZONE CRASH LOCATION | Accident | NUM (8) | 56 |
| Y_LINE | NON-MILEPOSTED CROSSING ROUTE LOCATION | Accident | CHAR (1) | 56 |
| ZIP_ADR | REPORTING OFFICER ZIP CODE | Accident | CHAR (9) | 56 |
NOTE:(1) SAS variable names and longer explanatory names are shown above each listing. (See Discussion for information on SAS formats.)
(2) For all SAS-formatted variables below, an extra category labeled as "ERROR CODES" consolidates all values not listed as legitimate codes. This category is printed when variables are listed in tables.
NON-LABELED VARIABLE -- See Raw File Documentation.
Note: Variable has YYYYMMDD format up to 1999, where YYYY = year, MM = Month and DD = Day. From 2000 onwards the variable captures the time of the accident as well.
NOTE: New variable added in 2000.
* Categories discontinued from 2000 onwards.
** Categories added from 2000 onwards.
NOTE: (1) Some changes in codes for this variable from 2000 onwards. This resulted in some shifts in categories. Some categories were combined, while some categories were differentiated because of this.
(2) There is a significant decrease in run-off road crashes from 1999 to 2000. This is because quiet a few crashes that were coded as run-off road until 1999 were coded as fixed object crashes from 2000 onwards. Similarly, category 18 (movable object) for 2000 and later years appears to be similar to category 34 (other object) for 1999 and earlier years. Also, categories 28 and 29 (sideswipe crashes) for 2000 and later years appear to be similar to category 36 for 1999 and earlier years.
NON-LABELED VARIABLE -- See Raw File Documentation.
Format YYYY Where YYYY=Year.
NOTE: Variable discontinued from 2000 onwards.
NOTE: Variable discontinued from 2000 onwards.
NOTE: Variable discontinued from 2000 onwards.
NON-LABELED VARIABLE -- See Raw File Documentation.
Format HHMM where HH=HOUR and MM=MINUTE.
NOTE: Variable discontinued from 2000 onwards.
NOTE: Variable discontinued from 2000 onwards.
NON-LABELED VARIABLE -- See Raw File Documentation.
Format YYNNNNNN Where YY=YEAR and NNNNNN=CASENUM.
NOTE: Variable type is CHAR for 1990 to 1999.
Note: Contact HSIS staff for more information on codes for the city variable. Also note that the city variable codes are different for pre 2000 and post 2000 years. HSIS staff maintains a list of all these codes.
NON-LABELLED VARIABLE ‑‑ See Raw File Documentation.
Computed Variable, used for linkage with the Road log variable.
NOTE: Variable discontinued from 1999 onwards.
NON-LABELLED VARIABLE -- See Raw File Documentation.
Format DD Where DD=Day of the Month (01 to 31).
NOTE: Variable added in 1998, and discontinued from 2000 onwards.
NON-LABELLED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NON-LABELLED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
Note: Variable discontinued from 2000 onwards.
NOTE: Variable discontinued from 1999 onwards.
NOTE: Variable discontinued from 2000 onwards.
NOTE: Variable discontinued from 2000 onwards.
* Categories coded before 2000
** Categories coded after 2000
NOTE: (1) Some changes in codes for this variable from 2000 onwards.
This resulted in some shifts in categories. Some categories were combined, while some categories were differentiated because of this.
(2) For 2000 and later years categories 7 to 12 are coded which describe different types of intersections. Prior to 2000, all intersection related crashes were coded as category 27. Similarly, for 2000 and later years categories 15 to 21 are coded which describe different types of ramp crashes. Prior to 2000, all ramp related crashes were coded as category 28.
NOTE: Variable discontinued from 2000 onwards.
NOTE: Variable discontinued from 2000 onwards.
NOTE: New variable added in 2000.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: Variable discontinued from 2000 onwards.
NOTE: Variable discontinued from 2000 onwards.
NOTE: New variable added in 2000.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NON-LABELLED VARIABLE -- Million Vehicle Miles Traveled on Road Segment.
NOTE: Variable discontinued from 2000 onwards.
NOTE: New variable added in 2000.
NOTE: New variable added in 2000.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NON-LABELED VARIABLE -- See Raw File Documentation.
NON-LABELED VARIABLE -- See Raw File Documentation.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NOTE: Variable discontinued from 2000 onwards.
NOTE: The unit of this variable is thousands for years before 1999. So, if the variable is coded as 10, it indicates 10,000. For later years, the variable is coded as the absolute population, which are 10,000 indicates 10,000.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: Variable discontinued from 2000 onwards.
* Categories present in 1999 and earlier years.
** Categories present in 2000 and later years.
NOTE: All divided highways coded as category 6 for 1999 and earlier years. For 2000 and later years, all divided highways coded as category 3 and category 4.
* Categories present in 2000 and later years.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
* Categories present in 2000 and later years.
NOTE: New variable added in 2000.
NOTE: New variable added in 2000.
NOTE: New variable added in 2000.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NOTE: Variable discontinued from 2000 onwards.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NOTE: Variable discontinued from 2000 onwards.
NOTE: Variable discontinued from 2000 onwards.
NOTE: Variable discontinued from 2000 onwards. Almost 100% observations are coded as 0. Use this variable with caution.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: Variable added in 1998, and discontinued from 1999 onwards.
NOTE: Variable discontinued from 1999 onwards.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: Variable discontinued from 2000 onwards.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: Variable discontinued from 2000 onwards.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: Variable discontinued from 2000 onwards.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: Variable discontinued from 2000 onwards.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
* Categories present in 2000 and later years.
NOTE: Variable discontinued from 2000 onwards.
* Categories coded in 2000 and later years.
NOTE: Variable discontinued from 2000 onwards.
NOTE: New variable added in 2000.
NOTE: New variable added in 2000.
NOTE: New variable added in 2000.
NOTE: New variable added in 2000.
NOTE: New variable added in 2000.
NOTE: Variable discontinued from 2000 onwards.
NON-LABELED VARIABLE -- See Raw File Documentation
NOTE: New variable added in 2000.
| VARIABLE NAME | VARIABLE DESCRIPTION | FILE | VARIABLE TYPE | FORMAT PAGE NO |
|---|---|---|---|---|
| ACTION | DRIVER CHARGED WITH VIOL | Vehicle | CHAR (1) | 62 |
| AIRBAGS | AIR BAGS PRESENT IN VEH | Vehicle | CHAR (1) | 62 |
| AIRDEPL | AIRBAGS DEPLOYED DURING CRASH | Vehicle | CHAR (1) | 62 |
| ALC_DRUG | ALCOHOL/DRUG IN ACC | Vehicle | NUM (8) | 62 |
| ALCFLAG | ALCOHOL FLAG | Vehicle | CHAR (1) | 63 |
| AMTDAMG | AMOUNT OF DAMAGE TO VEH | Vehicle | NUM (8) | 63 |
| AXLE_NBR | COMMERCIAL CARRIER AXLES | Vehicle | NUM (8) | 63 |
| AXLES | NUMBER OF AXLES FOR TRL#1 | Vehicle | NUM (8) | 64 |
| AXLES2 | NUMBER OF AXLES FOR TRL#2 | Vehicle | NUM (8) | 64 |
| BIKEFLAG | BICYCLE FLAG | Vehicle | CHAR (1) | 64 |
| BODY | CARGO BODY TYPE | Vehicle | NUM (8) | 64 |
| CASENO | NC ACCIDENT NUMBER WITH YR | Vehicle | NUM (8) | 64 |
| CC_CITY | COMMERCIAL CARRIER CITY | Vehicle | CHAR (22) | 64 |
| CC_STATE | COMMERCIAL CARRIER STATE | Vehicle | CHAR (2) | 65 |
| CC_ZIP | COMMERCIAL CARRIER ZIP CODE | Vehicle | CHAR (9) | 65 |
| CCB_CITY | COMM CARR BUSINESS CITY | Vehicle | CHAR (2) | 65 |
| CCB_STAT | COMM CARR BUSINESS STATE | Vehicle | NUM (8) | 65 |
| CDL_IND | CDL INDICATOR | Vehicle | CHAR (1) | 65 |
| CNT_SEAT | NUMBER OF SEATS OCCUPIED | Vehicle | CHAR (1) | 65 |
| CONTRIB1 | VIOL/CONTRIBUT FACTOR #1 | Vehicle | NUM (8) | 65 |
| CONTRIB2 | VIOL/CONTRIBUT FACTOR #2 | Vehicle | NUM (8) | 65 |
| CONTRIB3 | VIOL/CONTRIBUT FACTOR #3 | Vehicle | NUM (8) | 65 |
| CONTRIB4 | VIOL/CONTRIBUT FACTOR #4 | Vehicle | NUM (8) | 65 |
| CONTRIB5 | VIOL/CONTRIBUT FACTOR #5 | Vehicle | NUM (8) | 65 |
| CROSSMED | CROSS MEDIAN | Vehicle | CHAR (1) | 66 |
| DAMSEV | TAD#1 SEVERITY | Vehicle | CHAR (1) | 67 |
| DAMSEV2 | TAD#2 SEVERITY | Vehicle | CHAR (1) | 67 |
| DAMSEV3 | TAD#3 SEVERITY | Vehicle | CHAR (1) | 67 |
| DIR_TRVL | DIRECT OF TRAVEL ON ROUTE | Vehicle | CHAR (2) | 67 |
| DRG_RES | DRIVER ALC/DRUG TEST RESULT | Vehicle | NUM (8) | 67 |
| DRG_SUSP | DRIVER ALC/DRUG SUSPECTED | Vehicle | NUM (8) | 67 |
| DRSTATE | OUT OF STATE DRIVERS LIC | Vehicle | CHAR (1) | 68 |
| DRV_AGE | DRIVER/PEDEST AGE | Vehicle | CHAR (3) | 68 |
| DRV_BAC | DRIVER BLOOD ALCOHOL IN % | Vehicle | NUM (8) | 68 |
| DRV_CITY | DRIVER CITY | Vehicle | CHAR (22) | 68 |
| DRV_DOB | DRIVER DATE OF BIRTH | Vehicle | NUM (8) | 69 |
| DRV_INJ | DRIVER/PEDESTRIAN INJURY | Vehicle | CHAR (1) | 69 |
| VARIABLE NAME | VARIABLE DESCRIPTION | FILE | VARIABLE TYPE | FORMAT PAGE NO |
|---|---|---|---|---|
| DRV_RACE | DRIVER/PEDEST RACE | Vehicle | CHAR (1) | 69 |
| DRV_REST | DRIVER RESTRAINT USAGE | Vehicle | CHAR (2) | 69 |
| DRV_SEAT | DRIVER/PEDEST SEAT POS | Vehicle | CHAR (1) | 70 |
| DRV_SEX | DRIVER/PEDEST SEX | Vehicle | CHAR (1) | 70 |
| DRV_ZIP | DRIVER ZIP CODE | Vehicle | CHAR (9) | 70 |
| EMERGUSE | EMERGENCY VEHICLE USE | Vehicle | NUM (8) | 70 |
| EVENT1 | SEQUENCE OF EVENTS 1 | Vehicle | NUM (8) | 70 |
| EVENT2 | SEQUENCE OF EVENTS 2 | Vehicle | NUM (8) | 70 |
| EVENT3 | SEQUENCE OF EVENTS 3 | Vehicle | NUM (8) | 70 |
| EVENT4 | SEQUENCE OF EVENTS 4 | Vehicle | NUM (8) | 70 |
| EXPR_DT | LICENSE EXPIRATION DATE | Vehicle | NUM (8) | 72 |
| FIRE | POSTCRASH FIRE | Vehicle | NUM (8) | 72 |
| GOV_OWN | GOV OWNED VEH INDICATOR | Vehicle | CHAR (1) | 72 |
| GVWR_WGT | COMM CARR GROSS VEH WEIGHT | Vehicle | NUM (8) | 72 |
| HAZ_NUM1 | 1 DIGIT HAZMAT NUM PLACARD | Vehicle | NUM (8) | 72 |
| HAZ_NUM4 | 4 DIGIT HAZMAT NUM PLACARD | Vehicle | CHAR (4) | 72 |
| HAZ_PLAC | HAZMAT PLACARD INDICATOR | Vehicle | CHAR (1) | 73 |
| HAZMAT | HAZARDOUS CARGO | Vehicle | CHAR (1) | 73 |
| IMPACTFT | DIST TRAVEL AFTER IMPACT | Vehicle | NUM (8) | 73 |
| IMPACTSP | IMPACT SPEED | Vehicle | NUM (8) | 73 |
| INSURED | INSURANCE INDICATOR | Vehicle | CHAR (1) | 74 |
| INTOXC | DRIVER INTOXICATION GROUP | Vehicle | NUM (8) | 74 |
| L_PERMIT | LEARNER PERMIT | Vehicle | CHAR (1) | 74 |
| LENGTRL | LENGTH OF TRAILER #1,IN FT | Vehicle | NUM (8) | 74 |
| LENGTRL2 | LENGTH OF TRAILER #2,IN FT | Vehicle | NUM (8) | 74 |
| LIC_IND | DRIVER LICENSE INDICATOR | Vehicle | CHAR (1) | 75 |
| LIC_STAT | LICENSE STATE | Vehicle | CHAR (2) | 75 |
| LICRESTR | RESTRICT ON DRIV LICENSE | Vehicle | CHAR (2) | 75 |
| LICTYPE | TYPE OF DRIVERS LICENSE | Vehicle | CHAR (1) | 75 |
| MAKE | VEHICLE MAKE | Vehicle | CHAR (2) | 75 |
| MAKENAME | VEHICLE MAKE NAME | Vehicle | CHAR (20) | 76 |
| MANEUVER | VEH MANEUVER/PEDEST ACTION | Vehicle | NUM (8) | 76 |
| MISCACT1 | MISCELLANEOUS ACTION | Vehicle | CHAR (2) | 76 |
| MOSTHARM | MOST HARMFUL EVENT | Vehicle | NUM (8) | 77 |
| NUM_A | TOTAL A INJURIES IN VEH | Vehicle | CHAR (2) | 78 |
| NUM_B | TOTAL B INJURIES IN VEH | Vehicle | CHAR (2) | 78 |
| NUM_C | TOTAL C INJURIES IN VEH | Vehicle | CHAR (2) | 78 |
| NUM_K | TOTAL KILLED IN VEHICLE | Vehicle | CHAR (2) | 78 |
| VARIABLE NAME | VARIABLE DESCRIPTION | FILE | VARIABLE TYPE | FORMAT PAGE NO |
|---|---|---|---|---|
| NUM_OCCS | TOTAL OCCUPANTS IN VEH | Vehicle | CHAR (2) | 78 |
| NUM_POCS | NO OF POINTS OF CONTACT | Vehicle | CHAR (1) | 79 |
| NUM_TADS | NUMBER OF TAD CODES | Vehicle | CHAR (1) | 79 |
| NUMINJ | TOT INJURED IN VEH (K+A+B+C) | Vehicle | CHAR (2) | 79 |
| NUMVIOLS | NUM OF VIOLS INDICATED | Vehicle | CHAR (1) | 79 |
| OBJECT1 | TYPE OF OBJECT STRUCK | Vehicle | CHAR (2) | 79 |
| ON_RD | ON ROAD | Vehicle | CHAR (8) | 80 |
| ONRD_CL | ON ROAD CLASS | Vehicle | CHAR (4) | 80 |
| OTH_UNIT | OTHER UNIT TYPE | Vehicle | CHAR (20) | 81 |
| OUTSTATE | OUT OF STATE VEH REGIS | Vehicle | CHAR (1) | 81 |
| OWN_CITY | VEHICLE OWNER CITY | Vehicle | CHAR (22) | 81 |
| OWN_STAT | VEHICLE OWNER STATE | Vehicle | CHAR (2) | 81 |
| OWN_ZIP | VEHICLE OWNER ZIP CODE | Vehicle | CHAR (9) | 81 |
| OWNERTYP | OWNER CATEGORY | Vehicle | CHAR (3) | 81 |
| PARK_VEH | INDICATOR OF PARKED VEH | Vehicle | CHAR (1) | 81 |
| PED_LOC | NON-MOTORIST LOCATION | Vehicle | NUM (8) | 82 |
| PEDACT | NON-MOTORIST ACTION | Vehicle | NUM (8) | 82 |
| PEDCONT1 | CONTRIB CIRCUM NON-MOT 1 | Vehicle | NUM (8) | 82 |
| PEDCONT2 | CONTRIB CIRCUM NON-MOT 2 | Vehicle | NUM (8) | 82 |
| PEDFLAG | PEDESTRIAN IN ACCIDENT | Vehicle | CHAR (1) | 83 |
| PEDHITBY | PUPIL PEDEST STRUCK BY (SCHLBUS CRASH) | Vehicle | CHAR (1) | 83 |
| PHYSCOND | PHYSICAL COND OF DRIVER | Vehicle | NUM (8) | 83 |
| PTCONT1 | POINT OF CONTACT #1 | Vehicle | CHAR (2) | 84 |
| PTCONT2 | POINT OF CONTACT #2 | Vehicle | CHAR (2) | 84 |
| PTCONT3 | POINT OF CONTACT #3 | Vehicle | CHAR (2) | 84 |
| PTCONT4 | POINT OF CONTACT #4 | Vehicle | CHAR (2) | 84 |
| PTCONT5 | POINT OF CONTACT #5 | Vehicle | CHAR (2) | 84 |
| RD2OBJST | DISTANCE TO OBJECT STRUCK | Vehicle | NUM (8) | 85 |
| REGION | REGION OF IMPACT | Vehicle | CHAR (1) | 85 |
| ROLLOVER | VEHICLE ROLLOVER | Vehicle | CHAR (1) | 85 |
| ROLLPTCT | ROLLOVER, POINT OF CONTACT | Vehicle | NUM (8) | 85 |
| ROLLTAD | ROLLOVER, TAD SEVERITY | Vehicle | NUM (8) | 85 |
| SCH_BUS1 | SCHOOL BUS CONTACT VEH | Vehicle | NUM (8) | 85 |
| SCH_BUS2 | SCHOOL BUS NON-CONTACT VEH | Vehicle | NUM (8) | 86 |
| SOB_TEST | CHEMICAL TEST GIVEN | Vehicle | NUM (8) | 86 |
| SPDLIM | POSTED SPEED LIMIT | Vehicle | NUM (8) | 86 |
| SPILL | HAZARDOUS CARGO SPILL | Vehicle | CHAR (1) | 86 |
| TIRESKID | TIRE IMPRESSIONS IN FEET | Vehicle | NUM (8) | 87 |
| VARIABLE NAME | VARIABLE DESCRIPTION | FILE | VARIABLE TYPE | FORMAT PAGE NO |
|---|---|---|---|---|
| TOTLENG | TOT LENGTH OF TRAILER(S) IN FEET | Vehicle | CHAR (3) | 87 |
| TOWED_TO | TOWED TO | Vehicle | CHAR (50) | 87 |
| TRL_TYPE | TRAILER TYPE | Vehicle | NUM (8) | 87 |
| TRL1_FLG | DATA PRESENT (TRAILER #1) | Vehicle | CHAR (1) | 87 |
| TRL2_FLG | DATA PRESENT (TRAILER #2) | Vehicle | CHAR (1) | 88 |
| TRVL_SPD | ESTIMATED ORIGINAL SPEED | Vehicle | NUM (8) | 88 |
| UNDEROVR | VEHICLE UNDERRIDE/OVERRIDE | Vehicle | NUM (8) | 88 |
| UNIT_TYP | UNIT TYPE | Vehicle | CHAR (1) | 88 |
| V_DAMAG2 | TAD#2 LOCATION | Vehicle | CHAR (2) | 89 |
| V_DAMAG3 | TAD#3 LOCATION | Vehicle | CHAR (2) | 89 |
| V_DAMAGE | TAD#1 (AREA OF DAMAGE) LOC | Vehicle | CHAR (2) | 89 |
| VEH_SEIZ | VEHICLE SEIZURE DWI | Vehicle | NUM (8) | 89 |
| VEHCOND1 | VEHICLE DEFECT | Vehicle | CHAR (1) | 89 |
| VEHNO | VEHICLE POSITION NUMBER | Vehicle | NUM (8) | 90 |
| VEHON | VEHICLE LOCATION BASED ON ROAD | Vehicle | CHAR (1) | 90 |
| VEHSEV | SEVERITY | Vehicle | NUM (8) | 90 |
| VEHTYPE | VEHICLE TYPE | Vehicle | NUM (8) | 90 |
| VEHYR | MODEL YEAR OF VEHICLE | Vehicle | NUM (8) | 90 |
| VIN | VEHICLE IDENTIFICATION NO | Vehicle | CHAR (17) | 90 |
| VIN_ID | VEHICLE IDENTIFICATION NO | Vehicle | CHAR (25) | 91 |
| VISION | VISION OBSTRUCTION | Vehicle | NUM (8) | 91 |
| WIDTRL | WIDTH OF TRAILER #1 (IN) | Vehicle | NUM (8) | 92 |
| WIDTRL2 | WIDTH OF TRAILER #2 (IN) | Vehicle | NUM (8) | 92 |
NOTE:(1) SAS variable names and longer explanatory names are shown above each listing. (See Discussion for information on SAS formats.)
(2) For all SAS-formatted variables below, an extra category labeled as "ERROR CODES" consolidates all values not listed as legitimate codes. This category is printed when variables are listed in tables.
(3) For consistency with other State's files and ease of handling, driver-related variables have been included in this Vehicle Subfile as well as in the Occupant Subfile.
NOTE: Variable discontinued from 2000 onwards.
NOTE: Variable discontinued from 2000 onwards.
NOTE: (1) Variable discontinued from 2000 onwards.
(2) There is an increase in the number of observations coded as “Airbag Deployed”. This is because for later years, more vehicles were equipped with air bags.
NOTE: Variable discontinued from 2000 onwards.
NOTE: New variable added in 2000.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NON-LABELED VARIABLE -- See Raw File Documentation.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NOTE: New variable added in 1999. We are unsure about the quality of this variable for 1999. From 2000 onwards, the variable appears consistent.
NON-LABELED VARIABLE -- See Raw File Documentation.
Format YYNNNNNN Where YY=YEAR and NNNNNN=CASENUM.
NOTE: Variable type is CHAR for 1990 to 1999.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: Variable discontinued from 2000 onwards.
* Categories coded for 2000 and later years.
** Categories coded for 1999 and earlier years.
NOTE: Variables CONTRIB4 and CONTRIB5 discontinued from 2000 onwards.
NOTE: Variable discontinued from 2000 onwards.
NOTE: Categories 1-4 coded for 1999 and earlier years. For earlier years of data, 1-4 indicated, North, East, South and West respectively.
NOTE: New variable added in 2000.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NOTE: Variable discontinued from 2000 onwards.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NON-LABELED VARIABLE -- See Raw File Documentation.
* Category coded from 2000 onwards.
* Categories coded from 2000 onwards.
NOTE: The data included under this variable is inaccurate, in that regularly conducted field observations of use indicate figures which are at least 10 to 15 percent lower than the values found in the accident file.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NOTE: New variable added in 2000.
NOTE: New variable added in 2000.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NOTE: From 2000 onwards almost 100% observations are coded as missing.
NOTE: New variable added in 2000.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NOTE: New variable added in 2000.
NOTE: From 2000 onwards, almost all observations coded as missing.
NOTE: New variable added in 2000.
NOTE: Variable added in 1996, and discontinued from 1998 onwards.
NOTE: Variable discontinued from 2000 onwards.
NON-LABELED VARIABLE -- See Raw File Documentation.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NOTE: (1) Variable discontinued from 2000 onwards.
(2) For years 1995 and 1996, all categories coded as missing.
NOTE: From 2000 onwards all observations coded as missing.
For 1995 and 1996, all observations coded as 0.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: Variable added in 1999, and discontinued from 2000 onwards.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: Variable discontinued from 2000 onwards.
NOTE: (1) Categories 33 – 63 are present for 2000 onwards. For earlier years all these information was captured in a single category 68 (hit fixed object).
(2) Similarly categories 18,28,29 and 32 are present for 2000 onwards. For earlier years they were coded either as Sideswipe (category 69) or other in road (category 65).
(3) Categories 4,6,7,8,9,11,12 and 13 are coded from 2000 onwards.
(4) Categories 65,66,68 and 69 coded for years prior to 2000.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: Variables discontinued from 2000 onwards.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: Variable discontinued from 2000 onwards.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: Variable discontinued from 2000 onwards.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: Variable discontinued from 2000 onwards.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: Variable discontinued from 2000 onwards.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: Variable discontinued from 2000 onwards.
NOTE: Variable discontinued from 2000 onwards.
NOTE: Variable discontinued from 2000 onwards.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NOTE: New variable added in 2000.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: Variable discontinued from 2000 onwards.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NOTE: New variable added in 2000.
NOTE: New variable added in 2000.
NOTE: Variable format changed from 2000 onwards.
NOTE: New variable added in 2000.
NOTE: New variable added in 2000.
NOTE: Categories 1-9 coded for years prior to 2000. For later years, categories 10-18 coded. The categories defined appear to be different and it seems there has been a change in what information is collected by this variable from years prior to 2000 and later years.
NOTE: New variable added in 2000.
NOTE: New variable added in 2000.
NOTE: Variable discontinued from 2000 onwards. Almost all observations are coded as missing.
NOTE: Variable discontinued from 2000 onwards.
NOTE: Variable discontinued from 2000 onwards.
NOTE: Variable added in 1996, and discontinued from 1998 onwards.
NOTE: Variable added in 1996, and discontinued from 1998 onwards.
NOTE: New variable added in 2000.
NOTE: New variable added in 2000.
NOTE: For years before 2000 all observations coded as not stated. Observations coded as categories 1-6 for later years.
NOTE: From 2000 onwards almost 100% observations coded as missing.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: Variable discontinued from 2000 onwards.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NOTE: Variable discontinued from 2000 onwards.
NOTE: New variable added in 2000.
NOTE: For years prior to 2000 only categories 0 and 2 were coded. Other categories, C,H,O,P and V are coded for later years.
NOTE: New variable added in 2000.
NOTE: Variable discontinued from 2000 onwards.
NON-LABELED VARIABLE -- See Raw File Documentation.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: Variable discontinued from 2000 onwards.
NOTE: Variable added in 1996, and discontinued from 1998 onwards.
* Categories present in 2000 and later years.
** Categories present in years prior to 2000.
NOTE: Coding for two-axle trucks changed between 1991 and 1992, when new codes were added. (See Discussion.)
NON-LABELED VARIABLE -- See Raw File Documentation.
Format YYYY Where YYYY=Year.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: Variable discontinued from 2000 onwards.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NON-LABELED VARIABLE -- See Raw File Documentation.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 1996.
| VARIABLE NAME | VARIABLE DESCRIPTION | FILE | VARIABLE TYPE | FORMAT PAGE NO |
|---|---|---|---|---|
| AGE | OCCUPANT AGE | Occupant | NUM (8) | 95 |
| AIR_SW | AIRBAG SWITCH STATUS | Occupant | NUM (8) | 95 |
| AIRDEPL | AIRBAG DEPLOYED | Occupant | NUM (8) | 96 |
| CASENO | NC ACCIDENT NUMBER WITH YR | Occupant | NUM (8) | 96 |
| EJECT | EJECTION | Occupant | NUM (8) | 96 |
| EMS_DES | EMERGENCY MEDICAL SERVICE | Occupant | CHAR (50) | 96 |
| INJ | OCCUPANT INJURY | Occupant | NUM (8) | 96 |
| PRSN_CTY | PERSON COUNTY | Occupant | CHAR (22) | 96 |
| PRSN_DOB | PERSON DATE OF BIRTH | Occupant | NUM (8) | 97 |
| PRSN_NBR | PERSON NUMBER | Occupant | NUM (8) | 97 |
| PRSN_ST | PERSON STATE | Occupant | CHAR (2) | 97 |
| PRSN_TYP | PERSON TYPE | Occupant | NUM (8) | 97 |
| PRSN_ZIP | PERSON ZIP CODE | Occupant | CHAR (9) | 97 |
| RACE | OCCUPANT RACE | Occupant | NUM (8) | 97 |
| REST1 | OCCUPANT RESTRAINT | Occupant | NUM (8) | 98 |
| SEATPOS | SEATING POSITION | Occupant | NUM (8) | 98 |
| SEX | OCCUPANT SEX | Occupant | NUM (8) | 98 |
| TRAPPED | TRAPPED | Occupant | NUM (8) | 98 |
| TRT_FAC | TREATMENT FACILITY NAME | Occupant | CHAR (100) | 99 |
| VEHNO | VEHICLE POSITION NUMBER | Occupant | NUM (8) | 99 |
NOTE: (1) SAS variable names and longer explanatory names are shown above each listing. (See Discussion for information on SAS formats.)
(2) For all SAS-formatted variables below, an extra category labeled as "ERROR CODES" consolidates all values not listed as legitimate codes. This category is printed when variables are listed in tables.
(3) For consistency with other State's files and ease of handling, driver-related variables have been included in this Occupant Subfile as well as in the Vehicle Subfile.
NOTE: New variable added in 2000.
NOTE: New variable added in 2000.
NON-LABELED VARIABLE -- Format YYNNNNNN Where YY=YEAR and NNNNNN=CASENUM.
NOTE: Variable type is CHAR for 1990 to 1999.
NOTE: New variable added in 2000.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NOTE: New variable added in 2000.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NOTE: New variable added in 2000.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 2000.
NON-LABELED VARIABLE -- Number of vehicle on accident report.
The vehicle position number is needed (along with CASENO) for linking this seated occupant to the corresponding vehicle observation in the vehicle file.
NOTE: This information was copied from the North Carolina Vehicle Subfile variable named VEHNO.
| VARIABLE NAME | VARIABLE DESCRIPTION | FILE | VARIABLE TYPE | FORMAT PAGE NO |
|---|---|---|---|---|
| AADT | AVER ANNUAL DAILY TRAFFIC | Roadway | NUM (8) | 103 |
| AADT_YR | YEAR OF ADT | Roadway | CHAR (2) | 103 |
| ACCESS | ACCESS CONTROL | Roadway | CHAR (1) | 103 |
| AREATYPE | AREA TYPE | Roadway | CHAR (1) | 103 |
| BEGMP | BEGIN MILEPOST | Roadway | NUM (8) | 103 |
| CNTYRTE | COUNTY ROUTE NUMBER | Roadway | CHAR (10) | 104 |
| COUNTY | COUNTY | Roadway | CHAR (2) | 104 |
| DESC_ | ROAD DESCRIPTION | Roadway | CHAR (10) | 105 |
| DHRVOL | DESIGN HOUR VOLUME | Roadway | CHAR (2) | 105 |
| DIV | HIGHWAY DIVISION | Roadway | CHAR (2) | 105 |
| ENDMP | ENDING MILEPOST | Roadway | NUM (8) | 105 |
| FUNC_CLS | FUNCTIONAL CLASS | Roadway | CHAR (2) | 105 |
| FUNC_ST | FUNCTIONAL CLASS (STATE) | Roadway | CHAR (1) | 105 |
| HPMS1 | HPMS SAMPLE ID | Roadway | CHAR (6) | 106 |
| IMPROVE1 | TYPE OF RECENT IMPROVEMENT | Roadway | CHAR (2) | 106 |
| INTSTMP | INTERSTATE MILEPOST | Roadway | CHAR (5) | 106 |
| INV_CNTL | INVENTORY CONTROL | Roadway | CHAR (1) | 106 |
| LISTCNTL | LIST CONTROL | Roadway | CHAR (1) | 106 |
| LSHL_TYP | LEFT SHOULDER TYPE | Roadway | CHAR (2) | 107 |
| LSHLDWID | LEFT SHOULDER WIDTH | Roadway | NUM (8) | 107 |
| LT_PARK | LEFT PEAK PARK | Roadway | CHAR (1) | 107 |
| MED_TYPE | MEDIAN TYPE | Roadway | CHAR (1) | 108 |
| MEDWID | MEDIAN WIDTH TOTAL | Roadway | NUM (8) | 108 |
| MVMT | MILLION VEHICLE MILES TRAVELLED | Roadway | NUM (8) | 108 |
| NHS | NATIONAL HIGHWAY SYSTEM | Roadway | CHAR (1) | 108 |
| NO_LANES | NUMBER OF LANES- TOTAL | Roadway | CHAR (1) | 108 |
| PAVECOND | PAVEMENT CONDITION | Roadway | CHAR (2) | 109 |
| PCT_TRK1 | PERCENT TRUCKS | Roadway | CHAR (2) | 109 |
| PEAK_TRK | PERCENT TRUCKS AT PEAK | Roadway | CHAR (1) | 109 |
| POP_GRP | POPULATION GROUP | Roadway | CHAR (1) | 109 |
| PTCSTAT | PORTABLE TRAFFIC COUNTER | Roadway | CHAR (8) | 110 |
| RECCONTCD | RECORD CONTINUATION CODE | Roadway | CHAR (1) | 110 |
| RODWYCLS | ROAD WAY CLASS VARIABLE | Roadway | CHAR (2) | 110 |
| ROUGH | PAVEMENT ROUGHNESS | Roadway | CHAR (3) | 110 |
| ROW | RIGHT OF WAY | Roadway | CHAR (2) | 110 |
| RSHL_TYP | RIGHT SHOULDER TYPE | Roadway | CHAR (2) | 110 |
| RSHLDWID | RIGHT SHOULDER WIDTH | Roadway | NUM (8) | 111 |
| VARIABLE NAME | VARIABLE DESCRIPTION | FILE | VARIABLE TYPE | FORMAT PAGE NO |
|---|---|---|---|---|
| RT_PARK | RIGHT PEAK PARK | Roadway | CHAR (1) | 111 |
| RTE_NBR | ROUTE INVENTORIED | Roadway | CHAR (8) | 111 |
| RTE_TYPE | ROUTE TYPE (1ST DIGIT OF RTE_NBR) | Roadway | CHAR (1) | 111 |
| RULURBID | RURAL URBAN IDENTIFICATION | Roadway | CHAR (2) | 112 |
| SCENIC | SCENIC BYWAY | Roadway | CHAR (1) | 112 |
| SEG_LNG | SECTION LENGTH IN MILES | Roadway | NUM (8) | 112 |
| SIGHTDIS | SIGHT DISTANCE | Roadway | CHAR (2) | 112 |
| SPD_LIMT | SPEED LIMIT | Roadway | CHAR (2) | 112 |
| SPEC_SYS | SPECIAL SYSTEM | Roadway | CHAR (1) | 112 |
| STATE_SY | STATE HIGHWAY SYSTEM | Roadway | CHAR (1) | 113 |
| SURF_TYP | SURFACE TYPE | Roadway | CHAR (2) | 113 |
| SURF_WID | SURFACE WIDTH TOTAL | Roadway | NUM (8) | 113 |
| TERRAIN | TERRAIN | Roadway | CHAR (1) | 113 |
| TOWN | TOWN | Roadway | CHAR (2) | 113 |
| TRFGROW | TRAFFIC GROWTH FACTOR | Roadway | NUM (8) | 113 |
| TRK_RTE | DESIGNATED TRUCK ROUTE | Roadway | CHAR (1) | 113 |
| TRNLNWD | TURN LANE WIDTH | Roadway | NUM (8) | 114 |
| UPDATE_ | UPDATE | Roadway | CHAR (8) | 114 |
| URB_LOC | URBAN LOCATION | Roadway | CHAR (1) | 114 |
| URB_POP | RUR/URB DESIGNATED BY POP | Roadway | CHAR (1) | 114 |
| WTDSGSPD | WEIGHTED DESIGN SPEED | Roadway | CHAR (2) | 114 |
| YEAR | YEAR OF TRAFFIC COUNT | Roadway | NUM (8) | 114 |
| YR_IMPR1 | YEAR OF RECENT IMPROVEMENT | Roadway | CHAR (2) | 115 |
| YRADD | YEAR ADDED | Roadway | CHAR (2) | 115 |
NOTE: SAS variable names and longer explanatory names are shown above each listing. (See Discussion for information on SAS formats.)
NON-LABELED VARIABLE -- See Raw File Documentation.
Format YY Where YY=Year.
NON-LABELED VARIABLE -- See Raw File Documentation.
NON-LABELED VARIABLE -- See Raw File Documentation.
NON-LABELLED VARIABLE -- See Raw File Documentation.
NON-LABELLED VARIABLE -- See Raw File Documentation.
NON-LABELLED VARIABLE -- See Raw File Documentation.
NON-LABELED VARIABLE -- See Raw File Documentation.
NOTE: Variable for internal use. Use the variable FUNC_CLS to capture the Information about FUNCTIONAL CLASS.
NON-LABELED VARIABLE -- See Raw File Documentation.
NON-LABELLED VARIABLE -- See Raw File Documentation.
NOTE: This variable doesn’t provide information on the inside shoulder for divided highways. It gives the shoulder type for the outside shoulder across the opposite direction travel lanes. Inside shoulder information for divided highways is available for a very few miles and it is not possible to identify those. Hence for all analysis consider this to be the outside shoulder type for the opposite direction travel lane. See discussion section.
NOTE: Median width is measured from edge of traveled lane to edge of opposing lane. It includes paved and unpaved inside shoulder width.
NON-LABELLED VARIABLE -- Million Vehicle Miles traveled.
NOTE: New variable added in 1993.
NON-LABELLED VARIABLE -- See Raw File Documentation.
NOTE: Here, 88.9 percent of the section mileage is coded as "unknown" for years prior to 2000. From 2000 onwards, this variable is sufficiently populated. Truck percentages are only assigned when there is some confidence in the percent given -- i.e., when a classification count is available on that, or a nearby, section.
NOTE: This variable is coded as "unknown" in 59.7% of the cases. Truck percentages are only assigned when there is some confidence in the percent given -- i.e., when a classification count is available on that, or a nearby, section.
NOTE: Categories are defined by size of incorporated area. (See RURURB, URB_POP and Discussion.)
NON-LABELLED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 1999.
NOTE: For 2003 and later years, the number of miles available in the system is greater than earlier years. This results in higher mileages for some categories – especially rural 2-lane and others. See discussion.
NON-LABELLED VARIABLE -- See Raw File Documentation.
NON-LABELLED VARIABLE -- See Raw File Documentation.
NOTE: Approximately 3 to 5 percent of the mileage is coded as unknown."
NOTE: Approximately 12 percent of the mileage have unknown shoulder widths.
NON-LABELED VARIABLE -- See Raw File Documentation.
NON-LABELLED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 1992.
NON-LABELLED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 1999 and discontinued from 2002 onwards.
NON-LABELED VARIABLE -- See Raw File Documentation.
NON-LABELED VARIABLE -- See Raw File Documentation.
NON-LABELED VARIABLE -- See Raw File Documentation.
NON-LABELLED VARIABLE -- See Raw File Documentation.
NON–LABELED VARIABLE –- See Raw File Documentation.
NON–LABELED VARIABLE –- See Raw File Documentation.
NON-LABELED VARIABLE -- See Raw File Documentation.
NON-LABELLED VARIABLE -- See Raw File Documentation.
NOTE: New variable added in 1992.
NON–LABELED VARIABLE –- See Raw File Documentation.
Format MM/DD/YY where MM=MONTH, DD=DAY and YY=YEAR.
NOTE: New variable added in 1999.
NON–LABELED VARIABLE –- See Raw File Documentation.
NOTE: Variable discontinued from 2002 onwards.
NOTE: Categories are defined by a combination of the census-related "urbanized area" definition and population groups. (See POP_GRP and Discussion.)
NON-LABELLED VARIABLE -- Calculated value based on degree and lengths of curves of tangents in the HPMS sample section.
NON–LABELED VARIABLE –- See Raw File Documentation.
Format YYYY Where YYYY=Year.
NOTE: New variable added in 1999.
NON-LABELED VARIABLE -- See Raw File Documentation.
NON-LABELED VARIABLE –- See Raw File Documentation.