data collection and usage: nhtsa data systems - fars … · data collection and usage: nhtsa data...

Data Collection and Usage: NHTSA Data Systems – FARS and NASS-GES

2011 System Changes Summary 2010 Key Items Review

John McDonough

NISR, Inc. [email protected]

2011 FARS/GES Changes - 2012 TRF 1

Session Content • The 2011 data collection year completed

the harmonization of the FARS and GES data systems.

• In addition to covering 2011 data collection, this session will include a look back at some of the most significant changes in the 2010 data collection and provide an opportunity for questions and clarification.

2 2011 FARS/GES Changes - 2012 TRF

FARS/NASS GES Harmonization

D16 Fall 2007

MMUCC Spring 2008 FARS GES

3

2008 Data Collection

FARS GES Elements Attributes


Standardized terminology, rules, and Coding Manuals formats. Entry systems and some procedures based on source document access remained different.

2011 FARS/GES Changes - 2012 TRF

FARS/NASS GES Harmonization

FARS GES New

Elements / Structure

Precrash / Non-

motorist

4


FARS/GES Coding Manual

Entry System

Edit Checks


Merged manuals, entry systems, edit checks, and reviewed and adjusted data elements/attributes.


What Will Be Covered

• Selected the “most significant” items by Level (see 2011 Manual Changes handout)

• Levels refers to the data collection groupings

in FARS and GES (Crash, Vehicle, Driver, Precrash, and Person)


2011 Cross-Level System Changes 1. Entry System Structure / Process

– This “change” was made by FARS in 2010 but impacted GES in 2011.

– Allowed merging of the Coding and Validation Manuals and data entry system edit checks.

– GES adopted the FARS web-based entry system (MDE) that follows the “data levels” concept (Crash, Vehicle, Driver, etc.)


2011 GES Entry System

Overview

Crash Level

Vehicle Level

Driver Level

Precrash Level

Person Level MV Occupant

Person Level Not a MV Occupant

Ped/Bike Crash Typing

Un I t T Y P e

7

6 Forms or Levels in 2011: 1. Crash 2. Vehicle 3. Driver 4. Precrash 5. Person (MV

Occupant) 6. Person (Not a MV

Occupant)

2011 Cross-Level System Changes

2. Entry System Edit Checks


2010 FARS Edits

(1,000 +)

Adjust for

2011

Apply to GES less non-GES elements

Review & modify

based on access to

source data

Add back any needed

GES edits

2011 Cross-Level System Changes Entry System Edit Checks Process: • System Specifications and Edit Modifications


PB53 Modify If PERSON TYPE equals 06, 07, or 08 and PRE-EVENT MOVEMENT (PRIOR TO RECOGNITION OF CRITICAL EVENT) equals 10, and VEHICLE NUMBER – VEHICLE LEVEL equals NUMBER OF MOTOR VEHICLE STRIKING NON-MOTORIST, and PERSON TYPE equals 06 or 07 for the vehicle number identified in this person’s NUMBER OF MOTOR VEHICLE STRIKING NON-MOTORIST, then at least one PEDESTRIAN/ BIKE TYPING -BICYCLIST CRASH TYPE should equal 112, 151, 213, 214, 217 or 218. Comment: Modification to match reorganization of PB51 (per 3/8 email).

???? NEW 2011

(Both)

If all the harmful events in a vehicle’s SEQUENCE OF EVENTS are equal to 01-07, 16, 44, 51, 72, then AREAS OF IMPACT-MOST DAMAGED AREA must equal 00. Comment: If the vehicle is involved in only non-collision events (even multiple non-collision events), then code V28 - Area of Impact-Most Damaged non-collision.

Crash Level Changes 1. Relation to Junction attribute clarifications

as a result of 2010 data quality monitoring. 2. Addition of GES Only elements in

combined manual. – Also resulted in “FARS Only” designations.

• Principally this involves Driver Level data that comes from state driver history files and Person Level data associated with fatalities (e.g. Death Certificates, Laboratory/Coroner tests.


Relation to Junction

11

2009 and prior 2010 on


2010 Case Recoding Review • Many items in 2011 Changes Summary noted as “Updated

Remarks Section” are the result of data quality reviews of 2010 data. A good example is Relation to Junction.

• Specific problem attribute combinations are identified resulting in adjustments in the coding instructions and training (section from aggregate analysis table shown below).


Intersection & Intersection-Related

Intersection – FHE occurs within the boundaries of the intersection (i.e., curb lines or pavement edge lines)

Intersection-Related – FHE occurs on an approach to or exit from an intersection and results from an activity, behavior or control of the traffic units through the intersection


RTJ - Specific Location

14

CO

NTSR

UC

TION

ZON

E

RAMP SPEED LIMIT

25

SPEED LIMIT

55

SPEED LIMIT 75

YIELD

SPEED LIMIT

75

CONCRETE TRAFFIC BARRIER

US50

I-270

Intersection Within an Interchange Area


• 03 (Intersection-Related) means that the first harmful event: (1) occurs on an approach to or exit from an intersection, not on an entrance/exit ramp and (2) results from an activity, behavior or control related to the movement of traffic units through the intersection.

15

RTJ - Specific Location Items


• 01 (Non-Junction) is used for crashes where the first harmful event occurs outside an interchange area and does not occur in or related to a junction, ramp, rail grade crossing, crossover, or shared-use path or trail. This attribute includes crashes that occur on a parking lot way (access road) at the connection of a parking aisle. (See diagram at the end of the remarks section for this element.)

16



Relation to Junction Parking Lot / Drive way clarification

17

Fire Lane Fire Lane Fire Lane

Fire Lane ACCESS ROAD/PARKING LOT WAY

ACCE

SS R

OAD

/PAR

KIN

G LO

T W

AY

ACCE

SS R

OAD

/PAR

KIN

G LO

T W

AY

ACCESS ROAD/PARKING LOT WAY

PARK

ING

AISL

E

PARK

ING

AISL

E

PARK

ING

AISL

E

PARK

ING

AISL

E

PARK

ING

AISL

E

PARK

ING

AISL

E

PARK

ING

AISL

E

PARKING AISLE

PARK

ING

AISL

E

Rt. 172


RTJ - Specific Location Items Parking Lot / Driveway clarification


• 08 (Driveway Access Related) is used when the first harmful event: 1. occurs on the trafficway, 2. does not occur on a 04 (Driveway Access), but 3. results from an activity, behavior or control related to

the movement of traffic units onto or out of a driveway (See ANSI D16.1 Manual 2.5.9.1).

• Note: If there is not sufficient detail available to differentiate between driveway access and driveway access related, but it is known that the vehicle was coming out of (or going into) a driveway, default to 08 (Driveway Access Related). See diagram below.

19



Relation to Junction

20

Not an Intersection

“GES Only” Elements • In 2011 the move to matching entry systems

enabled the manuals to be combined. • While the systems have been “harmonized”

there still exist data elements unique to each. • As a result, the 2011 FARS/GES manual

includes: – C32 Interstate Highway – C33 Stratum – C34 Police Jurisdiction


Vehicle Level Items 1. V10 Vehicle Model

– 2 New across applicable manufacturers

2. V11 Body Type – 2 New across applicable manufacturers

3. V16 Motor Carrier Identification – Issuing Authority (GES)

4. V17 GVWR/GCWR – New to GES


Light and Medium Vehicle Models

2011 WebVIN and Recode Webinar 23

Light and Medium Vehicle Models

2011 WebVIN and Recode Webinar 24

New Model & Body Type for 2011 • New Model - 870 Medium/Heavy Van-Based Vehicle

• New Body Type - 55 Van-Based Bus GVWR > 10,000 lbs.


Make / Model / Body Type

Ford (12) Econoline E-350 Example

26

2010 Coding 2011 Coding

12 – Ford 461 – E-Series Van Econoline 21 - Large Van

12 – Ford 870 - Medium/Heavy Van-Based Vehicle 55 - Van-based Bus GVWR greater than 10,000 lbs.


Make / Model / Body Type Ford (12) Econoline E-350 Example

27

2010 Coding 2011 Coding



12 – Ford 881 – Medium/Hvy CBE 61 - Single-Unit Straight Truck 10,000 <GCWR <or= 19,500

12 – Ford 870 - Medium/Heavy Van-Based Vehicle 61 - Single-Unit Straight Truck 10,000 <GCWR <or= 19,500

9,500 GVWR

12,500 GVWR


Model / Body Type

28

• New Model for LSV/NEV – 598 Other (Low Speed Vehicle (LSV) /

Neighborhood Electric Vehicle (NEV)) • New Body for LSV/NEV

– 94 Low Speed Vehicle (LSV) / Neighborhood Electric Vehicle (NEV)


Model / Body Type

29

• New Body Type: 94 Low Speed Vehicle (LSV) /

Neighborhood Electric Vehicle (NEV)

New Manual Guidance for 2011:


V16 Motor Carrier Identification Number


NEW to GES

V16 Motor Carrier Identification Number • Issuing Authority and code 8 (None) under Identification

Number are new to GES

• This element is applicable in FARS/GES for the following qualifying vehicles: – Light trucks pulling a trailer with gross combination

weight rating (GCWR) greater than 10,000 lbs. – Medium/Heavy Trucks: GVWR greater than 10,000 lbs. – Buses with 9 or more seats (including the driver). – Light Trucks, Vans and Passenger Vehicles displaying a

hazardous materials placard.


“Commercial” vs. Qualifying • FARS/GES truck and bus elements are based on size

(GVWR/GCWR), seating (≥9), or presence of hazmat.


Motor Carrier ID # Availability on Reports

The Motor Carrier Identification Number is recorded on the Truck Supplement or Police Accident Report (PAR) next to the appropriate Source (Issuing Authority.) This information should available on with other elements required by the Federal Motor Carrier Safety Administration (FMCSA) and identified in MMUCC.

33

Alabama Truck & Bus Supplement

300354 190901 IA T-86828


V16 Motor Carrier Identification Number • Federal regulations require almost all trucks/buses operating in

commerce across state lines (i.e., interstate) have Identification Numbers except those hauling “exempt” commodities (e.g., unprocessed agricultural products). This will be a US DOT or MC/MX (ICC) Number.

• Some states issue “Intrastate” motor carriers a state number that can also be recorded here. Some may have the state’s abbreviation at the end.

34

8 6 8 2 8

In the FARS/GES data, the Issuing Authority field identifies the “kind” of number recorded in the Identification Number field (i.e. in using this data both are necessary to know what kind you are looking at.

0 6

CA’s State Number in FARS/GES


V17 GVWR/GCWR • Added to GES in 2011

• Gross Vehicle Weight Rating (GVWR) is the value specified by the manufacturer as the recommended maximum loaded weight of a single motor vehicle.

• Gross Combination Weight Rating (GCWR) is the value specified by the manufacturer(s) as the recommended maximum loaded weight of a combination (articulated) motor vehicle. This is for truck tractors and single-unit trucks pulling a trailer(s). GCWR is the sum of the gross vehicle weight ratings (GVWR) of all units, power unit and its trailer(s).


V17 GVWR/GCWR 0 - Not Applicable should be used for vehicles 10,000 lbs.

or less, not displaying a hazardous materials placard, for buses less than 9 seats (including driver), and for all motor homes.

1 - 10,000 lbs. or less should be used for passenger cars and light trucks 10,000 lbs. or less GVWR/GCWR when displaying a hazardous materials placard or for buses with 9 or more seats (including driver) with 10,000 lbs. GVWR or less.


Non-qualifying vehicles

GCWR Impact

1. Light trucks, 10,000 lbs. or less, pulling trailers (truck/trailers) (greater than 10,000 lbs. GCWR)

2. Single-unit trucks, less

than 26,000 lbs., pulling trailers (truck/trailers) (greater than 26,000 lbs. GCWR)

37

GVWR: Truck = 12,000 lbs. /Trailer = 20,000 lbs. GCWR = 32,000 lbs.

GVWR: Truck = 8,400 lbs. /Trailer = 16,500 lbs. GCWR = 24,900 lbs.


Person Level Items • P18 Alcohol Test

– (GES) Merged from separate data elements into one combined element with 3 Subfields

– FARS/GES attribute text matching

• P21 Drug Test – (GES) Merged from separate data elements

into one combined element with 3 Subfields – FARS/GES attribute text matching and GES

code values matched with FARS. 2011 FARS/GES Changes - 2012 TRF 38

P18 Alcohol Test


GES Attributes FARS Attributes Test Not Given Blood Breath (Breathalyzer “BAC”) Preliminary Breath Test (PBT) Urine Other Test Type Unknown Test Type Unknown if Tested/Not Reported

Test Not Given Blood Breath (Breathalyzer “BAC”) Preliminary Breath Test (PBT) Urine Other Test Type Vitreous Blood Plasma/Serum Blood Clot Liver Unknown Test Type Unknown if Tested/Not Reported

Found on coroner or toxicology reports

P21 Drug Test


P21 Drug Test


GES Attributes FARS Attributes Test Not Given Tested, No Drugs Found/Negative Positive Tested for Drugs, Results Unknown Unknown If Tested/Not Reported

Test Not Given Tested, No Drugs Found/Negative Specific Drug Listings: (100-295 Narcotic, 300-395 Depressant 400-495 Stimulant, etc.) Tested for Drugs, Drugs Found, Type Unknown/Positive 996 Other Drug Tested for Drugs, Results Unknown Unknown If Tested/Not Reported

Found on coroner or toxicology reports

FARS/GES KEY CHANGES 2010


Related Factors Elements • In 2010 there were a number of elements that

were added to FARS as new distinct data elements that are similar to information previously captured in “Related Factors”.

• For example, the set of “Pre-existing Vehicle

Defects” previously in Vehicle Level Related Factors is now captured in the Precrash Level data element PC4 Contributing Circumstances, Motor Vehicle.

2011 FARS/GES Changes - 2012 TRF 43 2010

Crash Level Changes

1. Addition of new system driven Crash Events Table for each crash that drives coding of later data elements such as First Harmful Event and Sequence of Events.

2. (FARS) Trafficway descriptor data elements

(e.g. Alignment, Grade, Speed Limit) moved to new Precrash Level so now coded per vehicle.


Crash Events - Summary

• Records in chronological sequence the set of events resulting from an unstabilized situation that constitutes a motor vehicle traffic crash. – The “crash” is concluded in time when all

events which originate from the unstabilized situation are stabilized.

– The element Sequence of Events in FARS previously was limited to 6 events per vehicle.


Crash Events Example #1 Example Case: • V1 (a compact passenger car) went out of

control on a wet roadway and struck the median guardrail with the front left side. The vehicle was redirected by the guardrail and re-entered the roadway, where it struck V2 (a large pickup truck) on the driver side door with its front. V1 spun to a stop in the roadway. V2, out-of-control, ran off the right side of the roadway, struck a pedestrian with its front and rolled over.


Crash Events Example Event # Vehicle #

(This Vehicle) AOI

(This Vehicle) SOE Vehicle #

(Other Veh.) AOI

(Other Veh.)

1 1 - Run off Rdwy, Left

- -

2 1 12 Guardrail Face - -

3 1 - Re-enter Roadway

-

-

4 1 12 MVIT 2 09

5 2 - Run off Rdwy, Right

-

-

6 2 12 Pedestrian - -

7 2 00 Rollover/ Overturn

-

-

47

V1 went out of control on a wet roadway and struck the median guardrail with the front left side.

The vehicle was redirected by the guardrail and re-entered the roadway, where it struck V2 on the driver side door with its front. V2, out-of-control, ran off the right side of the roadway, struck a pedestrian with its front and rolled over.

Crash Events Example Event # Vehicle #

(This Vehicle) AOI

(This Vehicle) SOE Vehicle #

(Other Veh.) AOI

(Other Veh.)

1 1 - Run off Rdwy, Left

- -

2 1 11 Guardrail Face - -

3 1 - Re-enter Roadway

-

-

4 1 12 MVIT 2 09

5 2 - Run off Rdwy, Right

-

-

6 2 12 Pedestrian - -

7 2 00 Overturn/ Rollover

-

-

48

V1 64 24 69 12

V2 12 63 08 01 2010

Trafficway Characteristics in 2010 • Nine elements previously collected once for the

crash’s location based on the First Harmful Event (FHE) collected for each motor vehicle in-transport on the new Precrash Level.

• There is no change in the Trafficway Assignment elements in FARS that include National Highway System, Roadway Function Class, Route Signing, and Trafficway Identifier


Vehicle Level Changes 1. Data element reorganization

2. Areas of Impact (modified FARS,

new for GES)

3. Bus Use (modified FARS, new for GES)


Areas of Impact • FARS:

– Old element (V22) Impact Point – Initial/Principal

– New element: (V28) Areas of Impact – Initial Damage Area / Most Damaged Area

• GES: – 2 New elements (V37) Areas of Impact

– Initial Damage Area, (V38) Areas of Impact – Most Damaged Area


AOI Attributes (Initial Damage / Most Damaged) AOI Attributes

(Left) AOI Vehicle Diagram AOI Attributes

(Right)

61 Left 62 Left front half 63 Left back half

81 Right 82 Right front half 83 Right back half


Other attributes: 00 - Non – Collision, 13 – Top, 14 – Undercarriage, 18 – Set In-motion (Not a clock point), 98 – Not Reported, 99 – Unknown

Note – the 60’s and 80’s values were new to FARS and not in MMUCC.

2010

Precrash Level • New level in FARS for 2010 with 23 data

elements – 9 moved from Crash Level, 3 moved from Vehicle

Level (PC4, PC17, PC20), 3 moved from Driver Level (PC14, PC15, PC16), and 8 New elements

• GES has always been collecting Precrash data. – In GES in 2010 the data elements are split between

the Vehicle and Driver. – There were a number of attribute modifications and

additions. (e.g. “Non-trafficway Area”).


Precrash Data • Precrash data designed to address “Crash

Avoidance” – Data to identify countermeasures or

intervention opportunities to prevent the crash from occurring or mitigate injury/damage.

• FARS and GES data collected from police

crash reports is descriptive (provides counts), it is not reconstructive.

54 2011 FARS/GES Changes - 2012 TRF 2010

Critical Crash Envelope (CCE) • Each vehicle involved has a CCE(s)

– A key to correctly coding Precrash is identification of the CCE (timeline)

• Begins when the driver recognizes impending danger or when the vehicle is in an imminent path of a collision.

• Ends when driver made a successful

avoidance, and has full steering control, and the vehicle is tracking; or the vehicle has an impact (harmful event).

55 2011 FARS/GES Changes - 2012 TRF 2010

Complex Single CCE • Example: A pedestrian steps from the curb into

the path a V1. V1 steers to the left, avoids the pedestrian and strikes V2 in the opposing travel lane.

56 Recognition of Danger Impact

V1

V1

V1’s Critical Event relates to the pedestrian, V2’s relates to V1’s action (encroachment)


Element Summary Example

1. What was the vehicle doing? 2. What happened? 3. What did the driver do about it? 4. How did the vehicle respond? 5. Where did it go after that? 6. How would you summarize this?


Critical Crash Envelope

Pre-Event

Movement

Critical Precrash

Category / Event

Attempted

Avoidance

Maneuver

Pre-Impact

Stability Crash Type Pre-Impact

Location

2010

Element Summary Example

1. What was the vehicle doing? 2. What happened? 3. What did the driver do about it? 4. How did the vehicle respond? 5. Where did it go after that? 6. How would you summarize this? 58

Critical Crash Envelope

Driver

Distracted

Pre-Event

Movement

Critical Precrash

Category / Event

Attempted

Avoidance

Maneuver

Pre-Impact

Stability Crash Type

Pre-Impact

Location

V1 was rounding a right-hand curve traveling north on SR 298. V1 attempted to avoid a deer in the roadway. V1 ran off right side of roadway into the ditch and then crossed back over the roadway and up an embankment off the left side of roadway. V1 then rolled over after colliding with a utility pole.

2010

Precrash Form

• “Trafficway Characteristics” element set are coded with respect to the vehicle’s Precrash location (prior to the Critical Event).


Trafficway Characteristics

• If a vehicle is in a junction just prior to its critical precrash event, the trafficway selected for coding the trafficway characteristics is the one it’s on before entering the junction.


V#2 - CCE

Intersection Crashes

2010

Non-Trafficway Areas • In some cases a vehicle will be outside the

boundaries of the trafficway prior to its critical event.

• Is such a case, the Precrash trafficway characteristics are identified as “Non-trafficway Area”

• Code will apply to all trafficway characteristics

• Trafficway Description • Total Lanes in Roadway • Speed Limit • Roadway Alignment and Grade • Roadway Surface Type and Conditions • Traffic Control Device / Functioning


V#1 locks his brakes on his private driveway, swerves unsuccessfully and hits a bicyclist on the driveway access.

2010

Person Level (MV Occupant) • New level in FARS for 2010 with 26 data

elements. • 10 elements specific to Motor Vehicle

Occupants – Eg. Seating Position, Restraint System / Helmet

Use, Indications of Misuse (NEW), Air Bag Deployed, Ejection, Extrication

• 16 duplicate with Not a MV Occupant form – E.g. Age, Sex, Injury Severity, Alcohol Test, Drug

Test, Transported to Medical Facility By, Death Date, Death Time


Any Indication of Mis-use of Restraint System or Helmet Use

• Added in the 3rd Edition of MMUCC • New to both FARS (P11) and GES (P24) Attributes: • Yes - case materials indicate misuse of the

applicable restraint (must be using a restraint)

• No – case materials indicate the applicable restraint was properly used or there is no indication of mis-use.

63 2010 2011 FARS/GES Changes - 2012 TRF

Any Indication of Mis-use of Restraint System or Helmet Use

Example (P10) Restraint System Use (P11) Mis-use

Narrative states that the driver of Vehicle 1 had the shoulder belt portion of the seatbelt behind his back.

Lap Belt Only Used Yes

The investigating officer states in the crash report that two persons were secured in back of a pickup using a rope.

Not Applicable No

The investigating officer states a child in a rear-facing restraint system was not properly secured in the vehicle.

Child Restraint System - Rear Facing

Yes

The investigating officer states that a child that should have been in a booster seat was unrestrained.

None Used – Motor Vehicle Occupant

No

64 2010 2011 FARS/GES Changes - 2012 TRF

Person Level (Not a MV Occupant) • New level in FARS for 2010 with 25 data

elements • 9 specific to “Persons Not in a Motor Vehicle” 5

of which were New. – E.g. - Number of Motor Vehicle Striking Non-

motorist, Non-motorist Location, Non-motorist Safety Equipment

– Addition of Ped/Bike Typing for pedestrians and pedal cyclists. (New in FARS and significantly modified in GES)

• 16 duplicate with Not a MV Occupant form – E.g. Age, Sex, Injury Severity, Alcohol Test, etc.


Excerpt taken from the narrative: At approximately 8:35 p.m. Unit 1 (vehicle) was traveling Northbound on Highway 64 near Kooler Drive. Unit 2 (pedestrian) was jogging Northbound before attempting to cross the highway. Unit 2 crossed the Southbound lane and was struck in the Northbound lane of Highway 64 by Unit 1. The streetlight was out in this wooded area where Unit 2 was crossing. This would make it unlikely Unit 1 could have seen Unit 2 before Unit 2 ran into its path.

Case Example NM Elements

66

N

NM10 Non-motorist Location

NM11 Non-Motorist Action Prior to Crash

NM12 Non-Motorist Action At Time of Crash

11 - Non-Intersection-On Roadway, Not in Marked Crosswalk

03 - Crossing Roadway 04 - Jogging/Running

01 - Dart / Dash 19 – Not Visible (Dark Clothing, No Lighting, etc.)


Ped/Bike Typing • Pedestrian and Bicycle Crash Type

describes the pre-crash actions of the involved parties to better define the sequence of events and precipitating actions leading to crashes between motor vehicles and pedestrians or bicyclists. – Applicable to the Person Types: Bicyclist,

Other Cyclist, Pedestrian, Person on Personal Conveyance.



FARS/GES uses an application where on-screen prompts and “clicked” choices direct the data entry without “coding” as in other elements.

Questions? [email protected]


mailto:[email protected]�

data collection and usage: nhtsa data systems - fars … · data collection and usage: nhtsa data...

Documents