using the fatality analysis reporting system (fars) for ......entered into the pedestrian and...

1

Using the Fatality Analysis Reporting System (FARS) for Systemic Analysis Introduction The systemic approach to roadway safety management includes the selection and treatment of sites based on the presence of geometric and operational attributes that increase crash risk. The Federal Highway Administration (FHWA) Systemic Safety Project Selection Tool presents the detailed process for conducting systemic safety analysis and identifies the Fatality Analysis Reporting System (FARS) as a potential data source. This document serves as a reference to identify potential variables of interest from FARS to support systemic analysis. The next two sections provide an overview of the systemic approach and FARS database. The remaining sections explain how to use FARS data to create crash trees and identify focus crash types, focus facility types, and risk factors. Appendix A, B, and C list and define potential variables of interest from the FARS dataset that can support systemic analysis for identifying focus crash types, facility types, and risk factors, respectively. FARS provides an online query tool that will automatically link data from multiple datasets; however, some users may prefer to work with the raw data. Appendix D explains how to merge raw data from multiple FARS datasets.

Overview of Systemic Approach The systemic approach is a six-step process as outlined in the Systemic Safety Project Selection Tool and shown in Figure 1. The systemic approach starts with the identification of focus crash types, focus facility types, and risk factors. Analysts then screen the network to identify and prioritize locations with the risk factors and select appropriate countermeasures to mitigate the risk factors.

Figure 1. Six-step systemic approach to safety management.

1. Identify Focus Crash Types, Facility Types,

and Risk Factors

2. Screen and Prioritize Candidate

Locations

3. Select Countermeasures

4. Prioritize Projects

5. Identify Funding and Implement

6. Perform Systemic Program Evaluation

https://safety.fhwa.dot.gov/rsdp/toolbox-content.aspx?toolid=38

https://safety.fhwa.dot.gov/rsdp/toolbox-content.aspx?toolid=38

2

The first step of the systemic approach is most relevant to the use of FARS data. This involves the identification of focus crash types, focus facility types, and related risk factors. Focus crash types typically reflect prevalent severe crash types for a given jurisdiction such as the emphasis areas listed in State and regional strategic highway safety plans (SHSPs). Focus facility types typically include the locations where the target crash types are most prevalent (e.g., rural, two-lane, undivided segments or urban, four-leg, signalized intersections). Risk factors are site-specific attributes common across locations with the focus crash type(s) and associated with an increased risk of the focus crashes (e.g., horizontal curves may increase the risk of roadway departure crashes and limited sight distance may increase the risk of right-angle crashes).

Overview of FARS The National Highway Traffic Safety Administration (NHTSA) maintains an online database of fatal crash records that can be used by agencies with limited or poor-quality crash records. These data records contain information related to the crash event, roadway, and environment as well as the people and vehicles involved. Analysts can use FARS data to identify focus crash types and facility types and to help identify potential crash contributing factors (i.e., risk factors). While FARS contains limited information about the road and traffic characteristics (e.g., shoulder width and type) needed for a detailed analysis of risk factors, the roadway attributes in the database can provide an initial indication of potential risk factors. Further, FARS has an online query tool that creates crash summaries and pin maps to display crash locations. Agencies can use these pin maps to locate the fatal crashes within their jurisdiction and identify additional details related to the roadway and traffic characteristics as needed.

The following is a summary of four primary data files available in FARS, the years of available data, and the relationship among the data files:

• Accident (1975-current): This data file contains information about crash characteristics and environmental conditions at the time of the crash. There is one record per crash.

• Vehicle (1975-current): This data file contains information describing the in-transport motor vehicles and the drivers of in-transport motor vehicles who are involved in the crash. There is one record per in-transport motor vehicle. Parked vehicle and working vehicle information is in the Parkwork data file.

• Person (1975-current): This data file contains information describing all persons involved in the crash including motorists (i.e., drivers and passengers of in-transport motor vehicles) and non-motorists (e.g., pedestrians and pedalcyclists). It provides information such as age, sex, vehicle occupant restraint use, and injury severity. There is one record per person.

• Pbtype (2014-current): This data file contains information about crashes between motor vehicles and pedestrians, people on personal conveyances, and cyclists. Data from the crash are entered into the Pedestrian and Bicycle Crash Analysis Tool (PBCAT). The output fields from PBCAT, including the pre-crash actions of the parties involved (crash type), are included in this data set. There is one record for each pedestrian, bicyclist, or person on a personal conveyance.

Note there are several other data files available such as Damage (indicates areas on the vehicle damaged in the crash), Drimpair (indicates physical impairments of drivers), and Violatn (indicates violations charged to drivers). These may be of interest for specific systemic analyses and analysts should refer to the FARS Analytical User’s Manual for further details on other data files and variables.

https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812602

3

Using FARS to Identify Focus Crash Types A focus crash type is typically one that represents the greatest number of severe crashes across the roadway system being analyzed and provides the greatest potential to reduce fatalities and serious injuries. Crash type is used loosely and could refer to general categories such as road departure, intersection, pedestrian, bicycle, or speeding related crashes. It could also refer to specific categories such as right-angle, left-turn, run-off-road right, head-on, or rollover. While systemic analysis could focus on any severity level (e.g., fatal and serious injury crashes, all injury crashes, or total crashes), the FARS database only provides data on fatal crashes.

Appendix A presents potential variables in the FARS database that can help define crash types. Each variable indicates the name of the related data file (e.g., ACCIDENT DATA FILE or VEHICLE DATA FILE). Codes are shown for specific categories within each variable; however, these codes change over time and analysts should refer to the latest FARS Analytical User’s Manual for the most recent codes. For age-related crash types (e.g., older driver or younger driver), use the ‘Age’ variable in the PERSON data file.

Using FARS to Identify Focus Facility Types A focus facility type is typically one on which the focus crash type most frequently occurs. Examples of general focus facility types include horizontal curves or local roads. Examples of specific focus facility types include rural, two-lane, undivided highways or urban, four-legged, signalized intersections.

Appendix B presents potential variables in the FARS database that can help define facility types. Each variable indicates the name of the related data file (e.g., ACCIDENT DATA FILE or VEHICLE DATA FILE). Codes are shown for specific categories within each variable; however, these codes change over time and analysts should refer to the latest FARS Analytical User’s Manual for the most recent codes.

Using FARS to Identify Risk Factors A risk factor is a characteristic of the roadway, environment, road user, or vehicle that is associated with the locations where the targeted crash types occurred. Examples include roadway alignment, traffic control, median type, and road surface condition.

Appendix C presents potential variables in the FARS database that can help to identify risk factors. Each variable indicates the name of the related data file (e.g., ACCIDENT DATA FILE or VEHICLE DATA FILE). Codes are shown for specific categories within each variable; however, these codes change over time and analysts should refer to the latest FARS Analytical User’s Manual for the most recent codes. Other vehicle-level attributes are available in the Vehicle Data File, including the year, make, model, body type, and vehicle factors that contributed to the crash.

4

Using FARS Data to Create Crash Trees A crash tree is a visualization of the crash data to show different subsets of crashes by variables of interest. Variables of interest may include those listed in the previous sections for focus facility types and risk factors. When using these variables, crash trees are useful for identifying or confirming focus facility types and risk factors. Crash trees are also useful for selecting targeted countermeasures when crash contributing factors (risk factors) are readily apparent.

Figure 2 is an example crash tree for fatal roadway departure crashes in a county. The focus crash type (i.e., fatal roadway departure crashes) is selected based on the county’s Local Road Safety Plan that identifies roadway departure crashes as a predominant crash type for severe crashes. This crash tree helps to identify the focus facility type associated with the focus crash type. The variables of interest include area type, number of lanes, and functional class. There is also a need to use variables related to the county and route signing to filter crashes on county roads within the county of interest. From the crash tree, fatal roadway departure crashes are most prevalent on rural roads (67% rural vs. 33% urban). Of the crashes on rural roads, nearly all are on 2-lane roads (95% 2-lane). It is apparent that the focus crash type is most prevalent on rural, 2-lane local roads. Rural, 2-lane collectors also standout as a potential focus facility type. As such, the county selects rural, 2-lane, undivided collector/local roads as the focus facility type.

Note: FARS provides numerical values to indicate different categories within a given variable. The user can convert the numbers to text (as shown in this crash tree) by using the ‘Find and Replace’ function (ctrl-F) in Excel. Refer to Appendix A, B, and C as well as the FARS Analytical User’s Manual for the codes.

Figure 2. Crash tree for fatal roadway departure crashes in County X (selecting focus facility type).

Location: 1 Date range: 2015 to 2017 Crashes: 90

Rural Number of Crashes: 60 Percent of Crashes: 67%

Urban Number of Crashes: 30 Percent of Crashes: 33%

2-Lane 57

95%

3-Lane 3

5%

2-Lane 30

100%

3-Lane 0

0%

Arterial 2

4%

Local 29

51%

Collector 26

46%

Arterial 0

0%

Collector 3

100%

Local 0

0%

Arterial 1

3%

Collector 1

3%

Local 28

93%

ftp://ftp.nhtsa.dot.gov/FARS/FARS-DOC/Analytical%20User%20Guide/

5

How to Generate FARS Data to Create Figure 2 1. Create a list of variables of interest and the corresponding data files. Based on the example, the

following is a list of variables of interest and the data files: a. Crash Type [VEHICLE DATA FILE] b. Relation to Junction- Specific Location (intersection or not) [ACCIDENT DATA FILE] c. Land Use (rural/urban) [ACCIDENT DATA FILE] d. Functional System [ACCIDENT DATA FILE] e. Total Lanes in Roadway [VEHICLE DATA FILE]

2. Access the ‘Query FARS Data’ tab on the FARS website: a. https://www-fars.nhtsa.dot.gov/QueryTool/QuerySection/SelectYear.aspx

3. Select the year of interest in the upper righthand corner (e.g., 2017) and click ‘Submit’ a. For multiple years, run the same query multiple times and merge the files.

4. Select the appropriate option based on the data files needed for the query a. From step 1, the variables are contained in the “accident” and “vehicle” data files b. As such, Option 3 (Crash / Vehicle / Driver / Precrash / Occupant) is applicable c. Select Option 3 and click ‘Submit’

5. Select the variables of interest from the list and click ‘Submit’ a. From step 1, the variables of interest are Crash Type, Relation to Junction- Specific Location,

Land Use, Functional System, and Total Lanes in Roadway. Look in the first section (Crashes fields) on the FARS website to find County, Relation to Junction (Specific Location), Land Use, and Functional System. Look in the last section (Precrash fields) to find Crash Type and Total Lanes in Roadway.

b. Since this is focused on county roads within a specific county, select the ‘Route Signing’ and ‘County’ variables as well. If there is interest in the specific crash date, then select the ‘Crash Date’ variable too. These variables are in the first section (Crashes fields) on the FARS website.

6. Apply any desired filters for the variables of interest and click ‘Submit’ a. In this case, select the State and County of interest (use the General Services

Administration’s (GSA) publication of worldwide Geographical Codes to identify the appropriate city or county code of interest)

b. The focus is on county roads, so select code 4 (County Road) from ‘Route Signing’ c. The focus crash type is roadway departure, so select code 1 (non-junction) from ‘Relation to

Junction’ and select codes 1-10 for ‘Crash Type.’ The codes are explained further in Appendix A as well as the FARS Analytical User’s Manual.

d. Since the focus is on county roads, you could filter ‘Functional System’ to include only certain functional class roads (e.g., codes 3-7 or 4-7 to include arterial (non-freeway), collector, and local roads)

7. Select ‘Case Listing’ a. This will provide access to raw data rather than summaries

8. Select the variables of interest to show in the case listing and click ‘Submit’ a. If you have selected any variables that could differ among the individual vehicles and

persons involved in the crash, then be sure to check “Vehicle Number” and “Person Number” to access these details

b. Otherwise, the case listing will return information at the crash level, which is sufficient for this example crash tree

9. Click ‘Export (XLS)’ to save the data as an Excel spreadsheet 10. If desired, modify the numeric values to text before creating crash trees by using the ‘Find and

Replace’ function (ctrl-F) in Excel.

https://www-fars.nhtsa.dot.gov/QueryTool/QuerySection/SelectYear.aspx

https://www.gsa.gov/reference/geographic-locator-codes/glcs-for-the-us-and-us-territorieshttps:/www.gsa.gov/reference/geographic-locator-codes/glcs-for-the-us-and-us-territories


6

The next step is to develop additional crash trees to explore potential risk factors. Thinking about the focus crash type (i.e., fatal roadway departure crashes) and focus facility type (i.e., rural, 2-lane, undivided collector/local roads), potential risk factors might include surface type, lane width, shoulder width and type, roadway alignment, surface condition, light condition, and roadside features. The FARS dataset does not include information on lane width, shoulder width/type, or roadside features. However, FARS does include information on surface type, roadway alignment, surface condition, and light condition among other potential risk factors as listed earlier in this document. It might be useful to develop crash trees to explore these potential risk factors.

Figure 3 shows a crash tree for horizontal roadway alignment (straight or curve), surface condition (dry or wet), and light condition (light, dark-lit, dark-unlit, dawn/dusk). From this crash tree, it appears that horizontal curves are a risk factor for fatal roadway departure crashes. Not only are these crashes most prevalent on curves (66% curves vs. 34% straight sections), the county knows there are many more miles of road that are straight than curved. As such, the county concludes that fatal crashes are over-represented on curves. Further, these crashes are most prevalent during dry and dark-unlit conditions.

Figure 3. Crash tree for fatal roadway departure crashes in County X (identifying risk factors).

Location: 1 Date range: 2015 to 2017 Number of Crashes: 90

Curve Number of Crashes: 59 Percent of Crashes: 66%

Straight Number of Crashes: 31 Percent of Crashes: 34%

Dry 52

88%

Wet 7

12%

Dry 29

94%

Wet 2

6%

Dark Lit 1

2%

Dark Unlit 40

77%

Dawn Dusk

3 6%

Light 8

15%

Dark Unlit

6 86%

Light 1

14%

Dark Unlit 12

41%

Light 17

59%

Dark Unlit

1 50%

Light 1

50%

7

How to Generate FARS Data to Create Figure 3 1. Create a list of variables of interest and the corresponding data files to first narrow the focus crash

type and facility type and then explore risk factors. Based on the example, the following is a list of variables of interest and the data files to explore risk factors (note these are in addition to the variables from Figure 2 that would narrow the focus crash type and facility type):

a. Roadway Alignment (straight/curve) [VEHICLE DATA FILE] b. Roadway Surface Condition (dry/wet) [VEHICLE DATA FILE] c. Light Condition (day/night) [ACCIDENT DATA FILE]

2. Access the ‘Query FARS Data’ tab on the FARS website: a. https://www-fars.nhtsa.dot.gov/QueryTool/QuerySection/SelectYear.aspx

3. Select the year of interest in the upper righthand corner (e.g., 2017) and click ‘Submit’ a. For multiple years, run the same query multiple times and merge the files.

4. Select the appropriate option based on the data files needed for the query a. From step 1, the variables are contained in the “accident” and “vehicle” data files b. As such, Option 3 (Crash / Vehicle / Driver / Precrash / Occupant) is applicable c. Select Option 3 and click ‘Submit’

5. Select the variables of interest from the list and click ‘Submit’ a. To narrow the focus crash and facility type, the variables of interest are County, Route

Signing, Crash Type, Relation to Junction- Specific Location, Land Use, Functional System, and Total Lanes in Roadway

b. From step 1, the additional variables of interest are Roadway Alignment, Roadway Surface Condition, and Light Condition

c. Look in the first section (Crashes fields) on the FARS website to find Light Condition d. Look in the last section (Precrash fields) on the FARS website to find Roadway Alignment and

Roadway Surface Condition e. Since this is focused on county roads within a specific county, select the ‘Route Signing’ and

‘County’ variables as well. These variables are in the first section (Crashes fields). 6. Apply any desired filters for the variables of interest and click ‘Submit’

a. In this case, select the State and County of interest (use the General Services Administration’s (GSA) publication of worldwide Geographical Codes to identify the appropriate city or county code of interest)

b. The focus is on county roads, so select code 4 (County Road) from ‘Route Signing’ c. The focus crash type is roadway departure, so select code 1 (non-junction) from ‘Relation to

Junction’ and select codes 1-10 for ‘Crash Type’ (all categories in Right Roadside Departure and Left Roadside Departure). The codes are explained further in Appendix A as well as the FARS Analytical User’s Manual.

d. The focus facility type is rural, 2-lane, undivided collector/local roads, so select code 1 (rural) from ‘Land Use’, select code 2 (2 lanes) from ‘Total Lanes in Roadway’, select code 1 (two-way not divided) from Trafficway Description, and select codes 5-7 (collector and local roads) from ‘Functional System’





9. Click ‘Export (XLS)’ to save the data as an Excel spreadsheet 10. If desired, modify the numeric values to text before creating crash trees (see above for details).




8

Finally, there is an opportunity to use crash trees to consider potential countermeasures. For example, Figure 3 might indicate the potential for enhanced curve warning and delineation (signing and pavement markings) given the prevalence of fatal roadway departure crashes on curves. In the example, these crashes were most prevalent during dry and dark-unlit conditions; however, if the crashes were more prevalent during wet and dark conditions, then this could indicate the need for other potential countermeasures (e.g., high friction surface treatment to address wet weather crashes). If an agency is considering the use of rumble strips to target roadway departure crashes, it is useful to know if centerline and/or shoulder rumble strips would be most appropriate. Figure 4 shows a crash tree for roadway alignment (straight or curve) and the side of road on which the crash occurred (left or right). For curves and straight sections, there is a relatively even split of ROR-Right vs. ROR-Left. It appears that centerline and shoulder rumble strips would both be appropriate for curves and straight sections in this case given the relatively even split.

Figure 4. Crash tree for fatal roadway departure crashes in County X (identifying countermeasures).

Location: 1 Date range: 2015 to 2017 Number of Crashes: 90

Curve Number of Crashes: 59 Percent of Crashes: 66%

Straight Number of Crashes: 31 Percent of Crashes: 34%

ROR-Left Crashes: 28 Percent: 47%

ROR-Right Crashes: 31 Percent: 53%

ROR-Left Crashes: 15 Percent: 48%

ROR-Right Crashes: 16 Percent: 52%

9

How to Generate FARS Data to Create Figure 4 1. This would rely on the same list of variables and data files that were used to generate the crash trees

in Figure 2 and Figure 3. 2. Access the ‘Query FARS Data’ tab on the FARS website:

a. https://www-fars.nhtsa.dot.gov/QueryTool/QuerySection/SelectYear.aspx 3. Select the year of interest in the upper righthand corner (e.g., 2017) and click ‘Submit’

a. For multiple years, run the same query multiple times and merge the files. 4. Select the appropriate option based on the data files needed for the query

a. From step 1, the variables are contained in the “accident” and “vehicle” data files b. As such, Option 3 (Crash / Vehicle / Driver / Precrash / Occupant) is applicable c. Select Option 3 and click ‘Submit’

5. Select the variables of interest from the list and click ‘Submit’ a. To narrow the focus crash and facility type, the variables of interest are County, Route

Signing, Crash Type, Relation to Junction- Specific Location, Land Use, Functional System, and Total Lanes in Roadway

b. For this specific crash tree, the variables of interest are Roadway Alignment and Crash Type c. Look in the first section (Crashes fields) on the FARS website to find Relation to Junction,

Land Use, and Functional System d. Look in the last section (Precrash fields) on the FARS website to find Roadway Alignment,

Crash Type, and Total Lanes in Roadway e. Since this is focused on county roads within a specific county, select the ‘Route Signing’ and

‘County’ variables as well. These variables are in the first section (Crashes fields) on the FARS website.

6. Apply any desired filters for the variables of interest and click ‘Submit’ a. In this case, select the State and County of interest (use the General Services

Administration’s (GSA) publication of worldwide Geographical Codes to identify the appropriate city or county code of interest)

a. The focus crash type is roadway departure, so select code 1 (non-junction) from ‘Relation to Junction’ and select codes 1-10 for ‘Crash Type’ (all categories in Right Roadside Departure and Left Roadside Departure). The codes are explained further in Appendix A as well as the FARS Analytical User’s Manual.

b. The focus facility type is rural, 2-lane, undivided collector/local county roads, so select code 1 (rural) from ‘Land Use’, select code 2 (2 lanes) from ‘Total Lanes in Roadway’, select code 1 (two-way not divided) from Trafficway Description, select codes 5-7 (collector and local roads) from ‘Functional System’, and select code 4 (County Road) from ‘Route Signing’





9. Click ‘Export (XLS)’ to save the data as an Excel spreadsheet 10. If desired, modify the numeric values to text before creating crash trees (see above for details).




10

Common Crash Trees of Interest This section provides a list of common crash trees and the related FARS variables and data files. Note the FARS query tool will merge the files for you. The key is to select the appropriate option (1, 2, or 3) as described in the previous section. For example, if you select Option 1 (Crash / Person Tables), then you won’t have access to variables such as number of lanes from the vehicle data file.

Table 1 presents FARS variables and data files to generate common intersection-related crash trees.

Table 1. FARS variables and data files for common intersection-related crash trees

FARS Variable FARS Data File Focus Crash Type

Focus Facility

Type

Risk Factor

Example Branches

County Accident ● ● ● Narrow to specific county City Accident ● ● ● Narrow to specific city Route Signing Accident ● ● ● Narrow to specific owner

Crash Type Vehicle ● • Rear end • Turn across path • Turn into path

Manner of Collision Accident ● • Angle • Front-to-Rear

Relation to Junction- Specific Location Accident ● ●

• Intersection • Intersection-related

Land Use (rural/urban) Accident ● • Rural • Urban

Functional System Accident ● • Major collector • Minor collector • Local

Type of Intersection Accident ● ● • Four-Way Intersection • T-Intersection • Roundabout

Traffic Control Device Vehicle ● ● • Traffic Control Signal • Stop Sign • Yield Sign

Roadway Surface Condition Vehicle ● • Dry

• Wet

Light Condition Accident ● • Light • Dark

Related Factors- Person Level Person ●

• Following Improperly • Driving Too Fast for

Conditions • Portable Electronic

Devices

11

Table 2 presents FARS variables and data files to generate common non-intersection-related crash trees.

Table 2. FARS variables and data files for common non-intersection-related crash trees

FARS Variable FARS Data File Focus Crash Type

Focus Facility

Type

Risk Factor Example Branches

County Accident ● ● ● Narrow to specific county City Accident ● ● ● Narrow to specific city Route Signing Accident ● ● ● Narrow to specific owner

Crash Type Vehicle ● • Right roadside departure • Left roadside departure

Manner of Collision Accident ● • Front-to-Front • Sideswipe – Opposite

Direction

First Harmful Event Accident ● • Rollover/overturn • Tree

Relation to Junction- Specific Location Accident ● ● • Non-junction

Land Use (rural/urban) Accident ● • Rural • Urban

Functional System Accident ● • Major collector • Minor collector • Local

Roadway Surface Type ● ● • Concrete • Blacktop • Dirt

Total Lanes in Roadway Vehicle ● ● • 1 • 2 • 3

Trafficway Description Vehicle ● ●

• One-Way Trafficway • Two-Way, Not Divided • Two-Way, Divided,

Positive Median Barrier

Roadway Alignment Vehicle ● ● • Straight • Curve Right • Curve Left

Roadway Surface Condition Vehicle ● • Dry

• Wet

Light Condition Accident ● • Light • Dark

Related Factors- Person Level Person ●

• Following Improperly • Driving Too Fast for

Conditions • Portable Electronic

Devices

12

Appendix A: Potential FARS Variables to Identify Focus Crash Types C6 County [ACCIDENT DATA FILE]

• 0 Not Applicable • 1-996 Use GSA publication of worldwide

Geographical Codes

• 997 Other • Not Reported • 999 Unknown

C7 City [ACCIDENT DATA FILE] • 0 Not Applicable • 1-9996 Use GSA publication of

worldwide Geographical Codes

• 9997 Other • 9898 Not Reported • 9999 Unknown

C11 Route Signing [ACCIDENT DATA FILE] This variable is available from 1975 to present. While ‘Ownership’ is available as a field from 2015 to present, Route Signing appears to be more complete. Prior to 2015, this data element’s Locator Code or Data Element Number was C12.

• 1 Interstate • 2 U.S. Highway • 3 State Highway • 4 County Road • 5 Local Street – Township

• 6 Local Street – Municipality • 7 Local Street – Frontage Road (Since

1994) • 8 Other • 9 Unknown

C20 Manner of Collision [ACCIDENT DATA FILE] • 0 Not Collision with Motor Vehicle in

Transport (Not Necessarily in Transport for 2005-2009)

• 1 Front-to-Rear • 2 Front-to-Front • 3 Angle – Front-to-Side, Same Direction • 4 Angle – Front-to-Side, Opposite Direction • 5 Angle – Front-to-Side, Right Angle

(Includes Broadside)

• 6 Angle – Front-to-Side/Angle-Direction Not Specified

• 7 Sideswipe – Same Direction • 8 Sideswipe – Opposite Direction • 9 Rear-to-Side • 10 Rear-to-Rear • 11 Other (End-Swipes and Others) • 98 Not Reported • 99 Unknown

C19 First Harmful Event [ACCIDENT DATA FILE] • 1 Rollover/Overturn • 8 Pedestrian • 9 Pedalcyclist

• 10 Railway Vehicle • 11 Live Animal

V11 Body Type [VEHICLE DATA FILE] • 80 Motorcycle



13

C21B Relation to Junction- Specific Location [ACCIDENT DATA FILE] • 1 Non-Junction • 2 Intersection • 3 Intersection Related • 4 Driveway Access • 5 Entrance/Exit Ramp Related • 6 Railway Grade Crossing • 7 Crossover Related • 8 Driveway Access Related

• 16 Shared-Use Path Crossing • 17 Acceleration/Deceleration Lane • 18 Through Roadway • 19 Other Location Within Interchange Area • 20 Entrance/Exit Ramp • 98 Not Reported • 99 Unknown

C23 Relation to Trafficway [ACCIDENT DATA FILE] • 1 On Roadway • 2 On Shoulder • 3 On Median • 4 On Roadside • 5 Outside Trafficway • 6 Off Roadway – Location Unknown

• 7 In Parking Lane/Zone (Since 2007) • 8 Gore • 10 Separator • 11 Continuous Left-Turn Lane • 98 Not Reported • 99 Unknown

C24 Work Zone [ACCIDENT DATA FILE] • 0 None • 1 Construction • 2 Maintenance

• 3 Utility • 4 Work Zone, Type Unknown • 8 Not Reported

PC23 Crash Type [VEHICLE DATA FILE] • CATEGORY I: SINGLE DRIVER

o CONFIGURATION A: RIGHT ROADSIDE DEPARTURE 1 Drive Off Road 2 Control/Traction Loss 3 Avoid Collision with Vehicle, Pedestrian, Animal 4 Specifics Other 5 Specifics Unknown

o CONFIGURATION B: LEFT ROADSIDE DEPARTURE 6 Drive Off Road 7 Control/Traction Loss 8 Avoid Collision With Vehicle, Pedestrian, Animal 9 Specifics Other 10 Specifics Unknown

o CONFIGURATION C: FORWARD IMPACT 11 Parked Vehicle 12 Stationary Object 13 Pedestrian/Animal 14 End Departure 15 Specifics Other 16 Specifics Unknown

14

• CATEGORY II: SAME TRAFFICWAY, SAME DIRECTION o CONFIGURATION D: REAR END

20 Stopped 21 Stopped, Straight 22 Stopped, Left 23 Stopped, Right 24 Slower 25 Slower, Straight 26 Slower, Left

27 Slower, Going Right 28 Decelerating 29 Decelerating, Straight 30 Decelerating, Left 31 Decelerating, Right 32 Specifics Other 33 Specifics Unknown

o CONFIGURATION E: FORWARD IMPACT 34 Vehicles Frontal Area

Impacts Another 35 Vehicle Impacted by

Frontal Area of Another 36 Vehicles Frontal Area



Impacts Another

39 Vehicle Impacted by Frontal Area of Another

40 Vehicles Frontal Area Impacts Another


42 Specifics Other 43 Specifics Unknown

o CONFIGURATION F: SIDESWIPE/ANGLE 44 Straight Ahead on Left 45 Straight Ahead on

Left/Right 46 Changing Lanes Right

47 Changing Lanes Left 48 Specifics Other 49 Specifics Unknown

• CATEGORY III: SAME TRAFFICWAY, OPPOSITE DIRECTION o CONFIGURATION G: HEAD-ON

50 Lateral Move (Left/Right)

51 Lateral Move (Straight)


o CONFIGURATION H: FORWARD IMPACT 54 Vehicles Frontal Area





Impacts Another


60 Vehicles Frontal Area Impacts Another



o CONFIGURATION I: SIDESWIPE/ANGLE 64 Lateral Move (Left/Rt) 65 Lateral Move (Straight)


15

• CATEGORY IV: CHANGING TRAFFICWAY, VEHICLE TURNING o CONFIGURATION J: TURN ACROSS PATH

68 Initial Opposite Directions (Left/Right)

69 Initial Opposite Directions (Going Straight)

70 Initial Same Directions (Turning Right)

71 Initial Same Directions (Going Straight)

72 Initial Same Directions (Turning Left)

73 Initial Same Directions (Going Straight)


o CONFIGURATION K: TURN INTO PATH 76 Turn Into Same

Direction (Turning Left) 77 Turn Into Same

Direction (Going Straight) 78 Turn Into Same

Direction (Turning Right) 79 Turn Into Same

Direction (Going Straight) 80 Turn Into Opposite

Directions (Turning Right)

81 Turn Into Opposite Directions (Going Straight)

82 Turn Into Opposite Directions (Turning Left)

83 Turn Into Opposite Directions (Going Straight)


• CATEGORY V: INTERSECTING PATHS (VEHICLE DAMAGE) o CONFIGURATION L: STRAIGHT PATHS

86 Striking from the Right 87 Struck on the Right 88 Striking from the Left

89 Struck on the Left 90 Specifics Other 91 Specifics Unknown

• CATEGORY VI: MISCELLANEOUS o CONFIGURATION M: BACKING, ETC.

92 Backing Vehicle 93 Other Vehicle or Object

(2010-2012)

93 Other Vehicle (2013-Later)

98 Other Crash Type 99 Unknown Crash Type

16

Appendix B: Potential FARS Variables to Identify Focus Facility Types C6 County [ACCIDENT DATA FILE]

• 0 Not Applicable • 1-996 Use General Services

Administration’s (GSA) publication of worldwide Geographical Codes









C13 Ownership [ACCIDENT DATA FILE] This variable is only available from 2015 to present. While this can help to identify the road owner, Route Signing appears to be more complete for this purpose.

• 1 State Highway Agency • 2 County Highway Agency • 3 Town or Township Highway Agency • 4 City or Municipal Highway Agency • 11 State Park, Forest or Reservation

Agency • 12 Local Park, Forest or Reservation

Agency • 21 Other State Agency • 25 Other Local Agency • 26 Private (other than Railroad) • 27 Railroad • 31 State Toll Road • 32 Local Toll Authority • 40 Other Public Instrumentality (i.e.,

Airport)

• 50 Indian Tribe Nation • 60 Other Federal Agency • 62 Bureau of Indian Affairs • 63 Bureau of Fish and Wildlife • 64 U.S. Forest Service • 66 National Park Service • 67 Tennessee Valley Authority • 68 Bureau of Land Management • 69 Bureau of Reclamation • 70 Corps of Engineers • 72 Air Force • 74 Navy/Marines • 80 Army • 96 Trafficway Not in State Inventory • 98 Not Reported • 99 Unknown



17

C12A Land Use [ACCIDENT DATA FILE] • 1 Rural • 2 Urban • 6 Trafficway Not in State Inventory

• 8 Not Reported • 9 Unknown

C12B Functional System [ACCIDENT DATA FILE] • 1 Interstate • 2 Principal Arterial – Other Freeways

and Expressways • 3 Principal Arterial – Other • 4 Minor Arterial • 5 Major Collector

• 6 Minor Collector • 7 Local • 96 Trafficway Not in State Inventory • 98 Not Reported • 99 Unknown

C15 Special Jurisdiction [ACCIDENT DATA FILE] • 0 No Special Jurisdiction • 1 National Park Service • 2 Military • 3 Indian Reservation

• 4 College/University Campus • 5 Other Federal Properties (Since 1977) • 8 Other (Since 1976) • 9 Unknown

C21B Relation to Junction- Specific Location [ACCIDENT DATA FILE] • 1 Non-Junction • 2 Intersection • 3 Intersection Related • 4 Driveway Access • 5 Entrance/Exit Ramp Related • 6 Railway Grade Crossing • 7 Crossover Related • 8 Driveway Access Related

• 16 Shared-Use Path Crossing • 17 Acceleration/Deceleration Lane • 18 Through Roadway • 19 Other Location Within Interchange

Area • 20 Entrance/Exit Ramp • 98 Not Reported • 99 Unknown

C22 Type of Intersection [ACCIDENT DATA FILE] • 1 Not an Intersection • 2 Four-Way Intersection • 3 T-Intersection • 4 Y-Intersection • 5 Traffic Circle

• 6 Roundabout • 7 Five-Point, or More • 10 L-Intersection • 98 Not Reported • 99 Unknown

PC5 Trafficway Description [VEHICLE DATA FILE] • 0 Non-Trafficway or Driveway Access • 1 Two-Way, Not Divided • 2 Two-Way, Divided, Unprotected

Median • 3 Two-Way, Divided, Positive Median

Barrier

• 4 One-Way Trafficway • 5 Two-Way, Not Divided With a

Continuous Left-Turn Lane • 6 Entrance/Exit Ramp • 8 Not Reported • 9 Unknown

18

PC6 Total Lanes in Roadway [VEHICLE DATA FILE] • 0 Non-Trafficway or Driveway Access • 1 One Lane • 2 Two Lanes • 3 Three Lanes • 4 Four Lanes

• 5 Five Lanes • 6 Six Lanes • 7 Seven or More Lanes • 8 Not Reported • 9 Unknown

NM9-PB31 Crash Location – Pedestrian [PBTYPE DATA FILE] • 1 At Intersection • 2 Intersection-Related • 3 Not At Intersection

• 4 Non-Trafficway Location • 7 Not a Pedestrian • 9 Unknown/Insufficient Information

NM9-PB31B Crash Location – Bicycle [PBTYPE DATA FILE] • 1 At Intersection • 2 Intersection-Related • 3 Not At Intersection

• 4 Non-Trafficway Location • 7 Not a Cyclist • 9 Unknown/Insufficient Information

19

Appendix C: Potential FARS Variables to Identify Risk Factors C6 County [ACCIDENT DATA FILE]

• 0 Not Applicable • 1-996 Use General Services

Administration’s (GSA) publication of worldwide Geographical Codes









C25 Light Condition [ACCIDENT DATA FILE] • 1 Daylight • 2 Dark – Not Lighted • 3 Dark – Lighted • 4 Dawn • 5 Dusk

• 6 Dark – Unknown Lighting • 7 Other • 8 Not Reported • 9 Unknown

C26 Atmospheric Conditions [ACCIDENT DATA FILE] • 0 No Additional Atmospheric Conditions • 1 Clear • 2 Rain • 3 Sleet, Hail • 4 Snow • 5 Fog, Smog, Smoke • 6 Severe Crosswinds

• 7 Blowing Sand, Soil, Dirt • 8 Other • 10 Cloudy • 11 Blowing Snow • 12 Freezing Rain or Drizzle • 98 Not Reported • 99 Unknown



20

C19 First Harmful Event [ACCIDENT DATA FILE] • 1 Rollover/Overturn • 2 Fire/Explosion • 3 Immersion (or Partial Immersion,

Since 2012) • 4 Gas Inhalation • 5 Fell/Jumped from Vehicle • 6 Injured in Vehicle (Non-Collision) • 7 Other Non-Collision • 8 Pedestrian • 9 Pedalcyclist • 10 Railway Vehicle • 11 Live Animal • 12 Motor Vehicle in Transport on Same

Roadway • 13 Motor Vehicle in Transport on Other

Roadway • 14 Parked Motor Vehicle (Not In

Transport) • 15 Non-Motorist on Personal

Conveyance • 16 Thrown or Falling Object • 17 Boulder • 18 Other Object (Not Fixed) • 19 Building • 20 Impact Attenuator/Crash Cushion • 21 Bridge Pier or Support • 23 Bridge Rail (Includes Parapet) • 24 Guardrail Face • 25 Concrete Traffic Barrier • 26 Other Traffic Barrier • 27 Highway/Traffic Sign Post • 28 Overhead Sign Support/Sign • 29 Luminary/Light Support • 30 Utility Pole/Light Support • 31 Post, Pole, or Other Supports • 32 Culvert • 33 Curb • 34 Ditch • 35 Embankment – Earth

• 36 Embankment – Rock, Stone, or Concrete

• 37 Embankment – Material Type Unk. • 38 Fence • 39 Wall • 40 Fire Hydrant • 41 Shrubbery • 42 Tree (Standing Only) • 43 Other Fixed Object • 44 Pavement Surface Irregularity (Ruts,

Potholes, Grates, etc.) • 45 Working Motor Vehicle • 46 Traffic Signal Support • 47 Vehicle Occupant Struck or Run Over

by Own Vehicle (1997-2009) • 48 Snow Bank • 49 Ridden Animal or Animal-Drawn

Conveyance (Since 1998) • 50 Bridge Overhead Structure • 51 Jackknife (Harmful to This Vehicle) • 52 Guardrail End • 53 Mail Box • 54 Motor Vehicle In-Transport Strikes or

is Struck by Cargo, Persons or Objects Set-in-Motion from/by Another Motor Vehicle In-Transport

• 55 Motor Vehicle in Motion Outside the Trafficway (Since 2008)

• 57 Cable Barrier (Since 2008) • 58 Ground • 59 Traffic Sign Support • 72 Cargo/Equipment Loss or Shift

(Harmful to This Vehicle) • 73 Object That Had Fallen From Motor

Vehicle In-Transport • 74 Road Vehicle on Rails • 91 Unknown Object Not Fixed • 93 Unknown Fixed Object • 98 Not Reported (2010 Only) • 99 Unknown

21

PC6 Total Lanes in Roadway [VEHICLE DATA FILE] • 0 Non-Trafficway or Driveway Access • 1 One Lane • 2 Two Lanes • 3 Three Lanes • 4 Four Lanes

• 5 Five Lanes • 6 Six Lanes • 7 Seven or More Lanes • 8 Not Reported • 9 Unknown

PC7 Speed Limit [VEHICLE DATA FILE] • 0 No Statutory Limit • 5-95 Speed Limit (5 mph Increments) • 98 Not Reported • 99 Unknown

PC8 Roadway Alignment [VEHICLE DATA FILE] • 0 Non-Trafficway or Driveway Access • 1 Straight • 2 Curve Right • 3 Curve Left

• 4 Curve – Unknown Direction • 8 Not Reported • 9 Unknown

PC9 Roadway Grade [VEHICLE DATA FILE] • 0 Non-Trafficway or Driveway Access • 1 Level • 2 Grade, Unknown Slope • 3 Hillcrest • 4 Sag (Bottom)

• 5 Uphill • 6 Downhill • 8 Not Reported • 9 Unknown

PC10 Roadway Surface Type [VEHICLE DATA FILE] • 0 Non-Trafficway or Driveway Access • 1 Concrete • 2 Blacktop, Bituminous, or Asphalt • 3 Brick or Block • 4 Slag, Gravel or Stone

• 5 Dirt • 7 Other • 8 Not Reported • 9 Unknown

PC11 Roadway Surface Condition [VEHICLE DATA FILE] • 0 Non-Trafficway Area or Driveway

Access • 1 Dry • 2 Wet • 3 Snow • 4 Ice/Frost • 5 Sand

• 6 Water (Standing or Moving) • 7 Oil • 8 Other • 10 Slush • 11 Mud, Dirt, Gravel • 98 Not Reported • 99 Unknown

22

PC12 Traffic Control Device [VEHICLE DATA FILE] • TRAFFIC SIGNALS

o 1 Traffic Control Signal (On Colors) Without Pedestrian Signal o 2 Traffic Control Signal (On Colors) With Pedestrian Signal o 3 Traffic Control Signal (On Colors) Not Known if Pedestrian Signal o 4 Flashing Traffic Control Signal o 8 Other Highway Traffic Signal o 9 Unknown Highway Traffic Signal

• REGULATORY SIGNS o 7 Lane Use Control Signal o 20 Stop Sign o 21 Yield Sign o 28 Other Regulatory Sign o 29 Unknown Regulatory Sign o 23 School Zone Sign/Device o 40 Warning Sign o 50 Person o 65 Railway Crossing Device o 97 Not Reported o 98 Other o 99 Unknown

23

PC19 Critical Event- Pre-crash [VEHICLE DATA FILE] • THIS VEHICLE LOSS OF CONTROL DUE TO:

o 1 Blow Out/Flat Tire o 2 Stalled Engine o 3 Disabling Vehicle Failure o 4 Poor Road Conditions o 6 Traveling Too Fast For Conditions o 8 Other Cause of Control Loss o 9 Unknown Cause of Control Loss

• THIS VEHICLE TRAVELING o 10 Over the Lane Line on Left Side of

Travel Lane o 11 Over the Lane Line on Right Side of

Travel Lane o 12 Off the Edge of the Road Left o 13 Off the Edge of the Road Right o 14 End Departure o 15 Turning Left at Intersection o 16 Turning Right at Intersection o 17 Crossing Over (Passing Through)

Intersection o 18 This Vehicle Decelerating o 19 Unknown Travel Direction

• OTHER MOTOR VEHICLE IN LANE o 50 Other Vehicle Stopped o 51 Traveling In Same Direction with Lower

Steady Speed o 52 Traveling In Same Direction while

Decelerating o 53 Traveling In Same Direction with Higher

Speed o 54 Traveling In Opposite Direction o 55 In Crossover o 56 Backing o 59 Unknown Travel Direction of the Other

Motor Vehicle in Lane • OTHER MOTOR VEHICLE ENCROACHING INTO

LANE o 60 From Adjacent Lane (Same Direction)

Over Left Lane Line o 61 From Adjacent Lane (Same Direction)

Over Right Lane Line o 62 From Opposite Direction Over Left Lane

Line

o 63 From Opposite Direction Over Right Lane Line

o 64 From Parking Lane/Shoulder, Median/Crossover, Roadside

o 65 From Crossing Street, Turning Into Same Direction

o 66 From Crossing Street, Across Path o 67 From Crossing Street, Turning Into

Opposite Direction o 68 From Crossing Street, Intended Path

Unknown o 70 From Driveway, Turning Into Same

Direction o 71 From Driveway, Across Path o 72 From Driveway, Turning Into Opposite

Direction o 73 From Driveway, Intended Path Unk. o 74 From Entrance to Limited Access

Highway o 78 Encroachment by Other Vehicle –

Details Unknown • PEDESTRIAN OR PEDALCYCLIST OR OTHER

NON-MOTORIST o 80 Pedestrian in Road o 81 Pedestrian Approaching Road o 82 Pedestrian Unknown Location o 83 Pedalcyclist/Other Non-Motorist in

Road o 84 Pedalcyclist/Other Non-Motorist

Approaching Road o 85 Pedalcyclist/Other Non-Motorist

Unknown Location • OBJECT OR ANIMAL

o 87 Animal in Road o 88 Animal Approaching Road o 89 Animal – Unknown Location o 90 Object in Road o 91 Object Approaching Road o 92 Object Unknown Location

• OTHER o 98 Other Critical Pre-crash Event o 99 Unknown

24

P16/NM15 Police Reported Alcohol Involvement [PERSON DATA FILE] • 0 No (Alcohol Not Involved) • 1 Yes (Alcohol Involved)

• 8 Not Reported • 9 Unknown (Police Reported)

P19/NM18 Police Reported Drug Involvement [PERSON DATA FILE] • 0 No (Drugs Not Involved) • 1 Yes (Drugs Involved)

• 8 Not Reported • 9 Unknown (Police Reported)

P26/NM25 Related Factors- Person Level [PERSON DATA FILE] • GENERAL

o 0 None/Not Applicable-Driver o 1 Not Visible o 2 Darting, Running or Stumbling Into Roadway (1995-2009) o 3 Improper Crossing or Roadway or Intersection o 4 Walking/Riding With or Against Traffic, Playing, Working, Sitting, Lying, Standing Etc. In

Roadway o 5 Interfering With Driver o 6 Ill, Passed Out/Blackout (1995-2009) o 7 Emotional (e.g., Depression, Angry, Disputed) o 8 Mentally Challenged (Since 1995) o 9 Construction/Maintenance/Utility Worker (Since 1995) Highway Department,

Contractor, Utility Company Personnel, etc. o 10 Alcohol and/or Drug Test Refused (Since 2017) o 11 Walking With Cane or Crutches o 12 Restricted to Wheelchair o 13 Paraplegic (1982-1994) o 13 Motorized Wheelchair Rider o 14 Impaired Due to Previous Injury o 15 Under the Influence of Alcohol, Drugs, or Medication (2008-2009) o 16 Blind o 17 Other Physical Impairment o 18 Mother of Dead Fetus/Mother of Infant Born Post Crash (Since 2011) o 19 Pedestrian

• NON-MOTOR-VEHICLE-OPERATOR-RELATED FACTORS: o 20 Running off Road (2000-2001) o 21 Overloading or Improper Loading of Vehicle with Passengers or Cargo o 22 Towing or Pushing Vehicle Improperly (1982-2003) o 23 Failing to [Dim Lights or, Since 1995] Have Lights on When Required o 24 Operating Without Required Equipment o 25 Creating Unlawful Noise or Using Equipment Prohibited by Law (1982-2002) o 26 Following Improperly o 27 Improper or Erratic Lane Changing o 28 Improper Lane Usage o 29 Intentional Illegal Driving on Road Shoulder, in Ditch, on Sidewalk, on Median

25

o 30 Making Improper Entry to or Exit from Trafficway o 32 Opening Vehicle Closure into Moving Traffic or While Vehicle is in Motion (Since

2001) o 33 Passing where Prohibited by Posted Signs, Pavement Markings, or School Bus

Displaying Warning not to Pass o 34 Passing on Wrong Side o 35 Passing with Insufficient Distance or Inadequate Visibility or Failing to Yield to

Overtaking Vehicle o 36 Operating the Vehicle in Other Erratic, Reckless, Careless or Negligent Manner (or

Operating at Erratic or Suddenly Changing Speeds, 1995-2009) o 37 Traveling on Prohibited Trafficway (Since 1995) o 38 Failure to Yield Right of Way o 39 Failure to Obey Actual Traffic Signs, Traffic Control Devices or Traffic Officers; Failure

to Obey Safety Zone Traffic Laws o 40 Passing Through or Around Barrier Positioned to Prohibit or Channel Traffic o 41 Failure to Observe Warnings or Instructions on Vehicles Displaying Them o 42 Failure to Signal Intentions o 43 Giving Wrong Signal (1982-1996) o 44 Driving Too Fast for Conditions or in Excess of Posted Maximum o 45 Driving Less Than Posted Maximum o 46 Operating at Erratic or Suddenly Changing Speeds (1982-1996) o 47 Making Right Turn From Left-Turn Lane, Left Turn from Right-Turn Lane o 48 Making Other Improper Turn o 49 Driving Wrong Way on One-Way Trafficway o 50 Driving on Wrong Side of Road (Intentional or Unintentional, 1995-2009) o 51 Operator Inexperience o 52 Unfamiliar with Roadway o 53 Stopping in Roadway (Vehicle Not Abandoned) o 54 Under-riding a Parked Truck (1982-1996) o 55 Getting Off/Out of or On/Into Moving Transport Vehicle o 56 Non-Driver Flees Scene (Since 2005) o 57 Improper Tire Pressure (Since 1995) o 58 Locked Wheel (1995-2014) o 59 Overcorrecting (Since 1995)

• VISION OBSCURED BY o 60 Rain, Snow, Fog, Smoke, Sand, Dust o 61 Reflected Glare, Bright Sunlight, Headlights o 62 Curve, Hill, or Other Design Features (Including Traffic Signs, Embankment) o 63 Building, Billboard, Other Structures (Since 1995) o 64 Trees, Crops, Vegetation o 65 Motor Vehicle (Including Load) o 66 Parked Vehicle o 67 Splash or Spray or Passing Vehicle o 68 Inadequate Lighting System

26

o 69 Obstructing Angles on Vehicle o 70 Mirrors o 71 Mirrors-Other (1982-2002) o 72 Other Visual Obstruction

• SKIDDING, SWERVING, OR SLIDING DUE TO o 73 Severe Crosswind o 74 Wind From Passing Truck o 75 Slippery or Loose Surface o 76 Tire Blow-Out or Flat o 77 Debris or Objects in Road

• OTHER FACTORS o 78 Ruts, Holes, Bumps in Road o 79 Live Animals in Road o 80 Vehicle in Road o 81 Phantom Vehicle o 82 Pedestrian, Pedalcyclist, or Persons on Personal Conveyances o 83 Ice, Snow, Slush, Water, Sand, Dirt, Oil, Wet Leaves on Road (Since 1995) o 84 Jay Walk (1982-1994) o 85 Jog (1982-1994) o 86 Emergency Services Personnel (Since 2007) o 87 Police or Law Enforcement Officer (Since 2002) o 88 Seat Back Not in Normal Upright Position, Seat Back Reclined (Since 2002) o 89 Parked Motor Vehicle With Equipment Extending into the Travel Lane (Since 2013) o 90 Non-Motorist Pushing a Vehicle o 91 Portable Electronic Devices (Since 2008) o 92 Person in Ambulance Treatment Compartment (Since 2013) o 93 Non-Motorist Wearing Motorcycle Helmet o 99 Unknown

27

NM10 Non-Motorist Location at Time of Crash [PERSON DATA FILE] • 0 Occupant of a Motor Vehicle (Includes

Railway Train Occupants Since 2006) • 1 At Intersection-In Marked Crosswalk • 2 At Intersection-Unmarked/Unknown

If Marked Crosswalk • 3 At Intersection-Not in Crosswalk • 4 Intersection-On Roadway, Crosswalk

Availability Unknown • 5 Intersection-Not on Roadway • 9 At Intersection-Unknown Location • 10 Not At Intersection-In Marked

Crosswalk • 11 Non At Intersection-On Roadway,

Not in Marked Crosswalk • 12 Non-Intersection-On Roadway,

Crosswalk Not Available • 13 Not At Intersection-On Roadway,

Crosswalk Availability Unknown

• 14 Parking Lane/Zone • 15 Non-Intersection-On Road Shoulder • 16 Bicycle Lane • 17 Non-Intersection-Outside Trafficway • 18 Non-Intersection-Other, Not a

Roadway • 19 Non-Intersection-Unknown • 20 Shoulder/Roadside • 21 Sidewalk • 22 Median/Crossing Island • 23 Driveway Access • 24 Shared-Use Path • 25 Non-Trafficway Area • 28 Other • 98 Not Reported • 99 Unknown Location

NM9-PB27 Marked Crosswalk Present [PBTYPE DATA FILE] • 0 None Noted • 1 Yes

• 9 Unknown

NM9-PB28 Sidewalk Present [PBTYPE DATA FILE] • 0 None Noted • 1 Yes

• 9 Unknown

NM9-PB32 Pedestrian Position [PBTYPE DATA FILE] • 1 Intersection Area • 2 Crosswalk Area • 3 Travel Lane • 4 Paved Shoulder/Bicycle Lane/Parking

Lane • 5 Sidewalk/Shared-Use Path/Driveway

Access

• 6 Unpaved Right-of-Way • 7 Non-Trafficway – Driveway • 8 Non-Trafficway – Parking Lot/Other • 9 Other/Unknown • 77 Not a Pedestrian

NM9-PB32B Bicyclist Position [PBTYPE DATA FILE] • 1 Travel Lane • 2 Bicycle Lane/Paved Shoulder/Parking

Lane • 3 Sidewalk/Crosswalk/Driveway Access • 4 Shared-Use Path

• 5 Non-Trafficway – Driveway • 6 Non-Trafficway – Parking Lot/Other • 7 Not a Cyclist • 8 Other • 9 Unknown

28

Appendix D: Merging Raw Data from FARS There are four primary datasets available in FARS, including the Accident file, Vehicle file, Person file, and Pbtype file. The Accident file provides one record per crash and contains information about crash characteristics and environmental conditions. The Vehicle file includes a record for each vehicle involved in each crash. Similarly, the Person file includes a record for each person involved in each crash. As such, there is a one-to-many relationship among the Accident, Vehicle, and Person files. Appendix D explains how to merge raw data from multiple FARS datasets.

As explained in the section Using FARS Data to Create Crash Trees, FARS provides an online query tool that will automatically link data from multiple datasets. This query tool is perfect for creating standard datasets to support systemic analysis; however, some users may prefer to work with the raw data to create custom categories. For example, an analyst may be interested in creating a crash tree that includes a branch for driver age with categories that include specific definitions for younger and older drivers. This would require use of variables in the Person file to obtain driver age and define age-related categories. It would then require merging this information with the Accident file to analyze against other crash-level variables.

Accessing Raw Data Files Raw FARS data files are available from NHTSA’s FTP website. The naming convention and directory structure of NHTSA’s FTP website vary per year of the data accessed, so analysts should refer to the FARS Analytical User’s Manual for more information as needed.

To download this data, select a year by accessing the corresponding directory (e.g., 2017), and then select the “National” directory. Download a copy of the data by selecting a file within the “National” directory. It is recommended that analysts use the comma separated values (CSV) file format because this format is compatible with Microsoft Excel and Access (Figure 5).

Figure 5. Example data download page for the 2017 FARS national data.

With the data downloaded, locate the files of interest (e.g., person.csv and accident.csv) and open the files with Microsoft Excel or other applicable software.

Merging Raw Data Files Raw data files are merged by using the FARS case number (ST_CASE), vehicle number (VEH_NO), and person number (PER_NO), where applicable. Each case number is unique to a single crash, each vehicle number applies to each vehicle involved in the crash, and each person number applies to each person involved in each vehicle. Again, there may be multiple vehicles per crash and multiple persons per vehicle. For example, Table 3 shows an example of cases 10004, 10005, and 10006. Case 10004 involved

ftp://ftp.nhtsa.dot.gov/fars/

https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812602

29

one vehicle and one person as indicated by the single row of data. Case 10005 involved two people as indicated by the two rows of data. Further, this case only involved one vehicle, designated by the ‘1’ in both rows under the ‘VEH_NO’ column. Case 10006 involved four people as indicated by the four rows of data and two vehicles as indicated by the ‘1’ and ‘2’ in the rows under the ‘VEH_NO’ column. Vehicle 1 included one person and vehicle 2 included three people.

Table 3. Sample of raw FARS data from the person file

STATE ST_CASE VEH_NO PER_NO 1 10004 1 1 1 10005 1 1 1 10005 1 2 1 10006 1 1 1 10006 2 1 1 10006 2 2 1 10006 2 3

using the fatality analysis reporting system (fars) for ......entered into the pedestrian and...

Documents