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

Transcription

1 Data Collection and Usage: NHTSA Data Systems FARS and NASS-GES 2010 System Changes Summary John McDonough NISR, Inc FARS/GES Changes TRF 1

2 FARS/NASS GES Harmonization In 2006, the Data Standardization Work Group was formed to address changes concurrent with revisions to ANSI D16 7 th Edition (2007) and MMUCC, Third Edition (2008) work dealt mostly with alignment with D16 and MMUCC and impacted the 2008 data collection year FARS/GES Changes TRF 2

3 FARS/NASS GES Harmonization 2009 data collection year moved to a standardization effort where data elements, attribute sets, and definitions were made identical (where possible). Involved 45 elements that were present in both FARS and GES. Standardized terminology, rules, and Coding Manuals formats The entry systems and some procedures based on source document access remained different FARS/GES Changes TRF 3

4 2010 Summary The 2010 collection year changes involved standardization of attribute sets and definitions in the remainder of the data elements in the two systems that were not addressed in Implemented new data elements into the two systems prior to a new elements freeze following the volume of change in FARS/GES Changes TRF 4

5 2010 Summary The 2010 changes finished the alignment of the data elements however due to the data entry systems still being different there still are some attribute differences. For example in 2010 FARS has split Person Level Data in the data entry system These last alignment items will be resolved in 2011 when FARS and GES are on the same entry system FARS/GES Changes TRF 5

6 2010 Changes Handouts 2010 FARS and GES Changes Summaries FARS 2010 Changes Summary document is 26 pages long System Specifications and Edit Checks document was 134 pages long Coding Forms (highlighted) Any question on a particular element or change not covered in the presentation can be addressed at the end of the session FARS/GES Changes TRF 6

7 What Will Be Covered Try to strike a balance between an overview of items and the detail to understand the more complex changes. Selected the most significant items by Level by working down through the forms handout. Levels refers to the data collection groupings in FARS and GES (Crash, Vehicle, Driver, Precrash, and Person) Further detail on any items is available in the 2010 Coding and Validation manuals for FARS and GES 2010 FARS/GES Changes TRF 7

8 Cross-Level System and Element Changes 1. Case Structuring in FARS Will apply to GES in Inclusion of a Not Reported attribute in MMUCC elements 3. Some FARS Related Factors attributes shifted to data elements 2010 FARS/GES Changes TRF 8

9 FARS Structure Changes The structuring of a case is when the FARS analysts preps the system for the entry of the case. It identifies how many vehicles and persons are involved so the system can establish the appropriate forms for the case. Prior to 2010 FARS had 4 forms or levels: Crash, Vehicle, Driver, and Person 2010 FARS/GES Changes TRF 9

10 2010 System Overview Driver Presence Hit & Run Vehicle Level Driver Level Crash Level Precrash Level U n I t T Y P e 6 Forms or Levels in 2011: 1. Crash 2. Vehicle 3. Driver 4. Precrash 5. Person (MV Occupant) 6. Person (Not a MV Occupant) Injury Severity Person Level MV Occupant Person Level Not a MV Occupant Injury Severity Ped/Bike Crash Typing 10

11 Case Structure Questions #1 How many person s not in a motor vehicle? #2 How many motor vehicle s? #3 How many persons in each motor vehicle? Populates element C3 Generates Person Level (Not a MV Occupant) forms. Populates element C4 Generates Vehicle and Driver Level forms for each. Populates C5 Generates Person Level (MV Occupant) form for each FARS/GES Changes TRF 11

12 Case Structure Element (C3) C3 Number of Forms Submitted for Persons Not in Motor Vehicles Person Types of: 04 - Occupant of a Non-Motor Vehicle Transport Device, 05 - Pedestrian, 06 - Bicyclist, 07- Other Cyclist, 08 - Person on Personal Conveyance, 10 - Person In/On Building, 19 - Unknown Type of Non-motorist Person Level Not a MV Occupant 2010 FARS/GES Changes TRF 12

13 Case Structure Element (C3) Counting Rule: Person s attempting to get in or on a motor vehicle must maintain the same person type as at the start of the unstabilized situation. For example, Pedestrian would be coded if: D1 exited his vehicle, the vehicle started to roll backwards. D1 tried to reenter the vehicle to set the brake and in the process fell and was run over by his vehicle. Person Level Not a MV Occupant 2010 FARS/GES Changes TRF 13

14 Case Structure Element (C4) Populated by case structure question #2 and reflects how many contact motor vehicles are in this case. Non-contact vehicles are not counted even when included on the report (e.g. driver charged with a violation). Contact vehicles included in the case need not make contact with one another, only have a harmful event as part of the unstabilized situation. Vehicle Level As one unstabilized situation, this is a 3 vehicle crash even though V3 never struck V1 or V FARS/GES Changes TRF 14

15 Case Structure Element (C5) C5 Number of Motor Vehicle Occupant Forms Submitted Populated in MDE by case structure question #3 This count will reflect how many Person Level (MV Occupant) Forms apply to this case. Loads of vehicles include Persons: upon, or set in motion boarding or alighting attached to and in position to move with the vehicle Person Level MV Occupant 2010 FARS/GES Changes TRF 15

16 Case Structure Element (C5) Counting Rule: Person s attempting to get out of or off of a motor vehicle must maintain the same person type as at the start of the unstabilized situation. For example, a vehicle occupant would be counted if: D1 slowed to allow his friend (who was walking to the store) to get onto the hood of his vehicle to ride the remaining distance to his destination. The vehicle s speed was too great and the rider fell striking his head when he jumped off at his destination. Person Level MV Occupant 2010 FARS/GES Changes TRF 16

17 Addition of Not Reported A Not Reported attribute has been added in FARS/GES to MMUCC elements. The intent of the addition is to provide an attribute to be used in the event that the source documents lack the information needed to complete a FARS/GES case. 1. The state s crash report and/or other case materials do not capture the requested data. 2. Law Enforcement has left information blank or incomplete. SWT 2009 October 26th-30th 17

18 Standard Definition Not Reported If a state s crash report manual instructs to leave blank data blocks that are not applicable, then a blank in those data blocks are NOT considered Not Reported. Code Not Reported in these situations: 1. No coded data block exists on the report, and/or 2. A coded data block exists and it is left blank, and/or 3. No other information is available (e.g., narrative, diagram or case materials) Qualifier All Conditions MUST Apply Not Reported SWT 2009 October 26th-30th 18

19 Related Factors Elements FARS includes Related Factors elements on the Crash, Vehicle, Driver, and Person Levels. Elements reflect information provided in the narrative or Contributing/Related Factors fields on the Crash Report by the investigating officer. For example on the Crash Level: 05 Surface Under Water 06 Inadequate Construction or Poor Design of Roadway, Bridge, etc. 07 Surface Washed Out (caved-in, road slippage) 13 Aggressive Driving / Road Rage by Non-Contact Vehicle Driver 2010 FARS/GES Changes TRF 19

20 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 at the top of Pg. 9 of the Changes Summary, 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 FARS/GES Changes TRF 20

21 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. 3. Type of Intersection added as a new data element in FARS and GES 2010 FARS/GES Changes TRF 21

22 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 Crash Events table is not limited in the number of events that can be recorded and is designed to provide a coded sequence of all qualifying events which occurred in the crash. The element Sequence of Events in FARS previously was limited to 6 events per vehicle FARS/GES Changes TRF 22

23 Crash Events Table 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. 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. V1 FHE FHE Unstabilized Situation MHE RRL Guardrail Face Reenter Roadway MVIT MHE V2 MVIT RRR Pedestrian Rollover 2010 FARS/GES Changes TRF 23

24 Crash Events - Process Entry of data on the entire crash in Crash Events, requires analysis and includes the data to code other related elements. To prevent double coding of data, the Crash Events table is used to derive the following data elements: First Harmful Event (FHE) Sequence of Events (SOE) Area(s) of Impact, Initial (AOI/Initial) 2010 FARS/GES Changes TRF 24

25 Crash Events - Process Crash Events Event # Vehicle # (This) AOI (This) SOE Column Vehicle # (Other) AOI (Other) Elements Derived FHE SOE AOI/Initial Elements Guided or Controlled (edit checks) Manner of Collision Relation to Trafficway Crash Type 2010 FARS/GES Changes TRF 25

26 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 FARS/GES Changes TRF 26

27 Event # Vehicle # (This Vehicle) Crash Events Example AOI (This Vehicle) Run off Rdwy, Left SOE Vehicle # (Other Veh.) AOI (Other Veh.) Guardrail Face Re-enter Roadway MVIT Run off Rdwy, Right Pedestrian Rollover/ Overturn

28 Event # Vehicle # (This Vehicle) Crash Events Example AOI (This Vehicle) SOE Vehicle # (Other Veh.) AOI (Other Veh.) Run off Rdwy, Left Guardrail Face Re-enter Roadway MVIT Run off Rdwy, Right Pedestrian Overturn/ Rollover - - V V

29 Sources for Coding A hierarchy is used for resolving ambiguous information when recording Crash Events data including the AOI (contact point for each harmful event). 1. Narrative 2. Diagram Clearly written description of the events takes precedence. If detailed, can augment information included in the narrative. 3. Report Field If present, should match narrative and diagram. Likely to lack detail needed for Crash Events FARS/GES Changes TRF 29

30 Sources for Coding The Crash Events table does not represent reconstructed vehicle movements based on the position of a vehicle in resting place diagram and does not attempt to calculate exact areas of impact. Example: V1 ran the stop sign on 1st at Main. V1 struck V2 in the right side with its front. V1 came to final rest on the right roadside. V2 came to final rest in the opposing travel lane on Main. Crash Events AOI for V2 would be 81 Right Side. Don t assume V2 yaw marks mean it must have been a 4 or 5 clock point impact FARS/GES Changes TRF 30

31 Sources for Coding If the language in the narrative is ambiguous AND the diagram or other case information don t provide resolution, the area indicated first in the narrative is used for coding the AOI. Examples: Front, left = 12 Left, front = 62 Front, corner = 12 Right, rear = 83 Back, right side = FARS/GES Changes TRF 31

32 Type of Intersection NEW element GES (A28) / FARS (C21) MMUCC data element Value selected is based on the location of the FHE Attributes: Not an Intersection Four-Way Intersection T-Intersection Y-Intersection Traffic Circle Roundabout Five-Point, or More Not Reported Unknown 2010 FARS/GES Changes TRF 32

33 Type of Intersection Applicable to both interchange and noninterchange areas, but only when Relation to Junction is coded: Intersection Intersection-Related Sidewalk V2 PARKING METER 2010 FARS/GES Changes TRF 33

34 Type of Intersection Four-Way Intersection refers to two roadways which cross or connect FARS/GES Changes TRF 34

35 Type of Intersection T-Intersection refers to an intersection where two roadways connect and one roadway does not continue across the other roadway. The roadways form a T. (At-grade Intersections) STOP STOP 2010 FARS/GES Changes TRF 35

36 Trafficway Characteristics in 2010 Nine trafficway elements previously collected once for the crash s location based on the First Harmful Event (FHE) are now collected for each motor vehicle in-transport on the new Precrash Level. New attributes for Roadway Alignment, Roadway Grade and Surface Condition and restructured codes for Traffic Control Device All nine elements have new codes for Non- Trafficway Area and Not Reported 2010 FARS/GES Changes TRF 36

37 Trafficway Assignment Elements There is no change in the Trafficway Assignment elements in FARS that include National Highway System, Roadway Function Class, Route Signing, and Trafficway Identifier. Non-Junction Crashes (Crash Level C10-13): Assigned to the trafficway on which the First Harmful Event (FHE) occurred. Intersection Crashes (Crash Level C10-13): At-intersection crashes are assigned to the highest functional class of trafficway at the intersection FARS/GES Changes TRF 37

38 Vehicle Level Changes 1. Data element reorganization 2. Areas of Impact (modified FARS, new for GES) 3. Bus Use (modified FARS, new for GES) 2010 FARS/GES Changes TRF 38

39 Vehicle Level V6 Hit and Run (V37) - system key Vehicle Identifier Information V7 Registration State (V6) V8 Registered Vehicle Owner (V7) V9 Vehicle Make (V8) V10 Vehicle Model (V9) V11 Body Type (V10) V12 Model Year (V11) V13 Vehicle Identification Number (V12) 2010 FARS/GES Changes TRF 39

40 Vehicle Level Truck and Bus Related Information V14 Vehicle Trailing (V29) V15 Jackknife (V21) V16 Motor Carrier Identification Number (V27) V17 GVWR/ GCWR (V30) V18 Vehicle Configuration (V28) V19 Cargo Body Type (V31) V20 H.M. Involvement/Placard (V32) V21 Bus Use (V13) 2010 FARS/GES Changes TRF 40

41 Vehicle Level Special Circumstances V22 Special Use (V4) V23 Emergency Use (V15) V24 Travel Speed (V16) V25 Vehicle Role (Removed) V25 Underride/Override (V24) V26 Rollover (V19) V27 Location of Rollover (V20) 2010 FARS/GES Changes TRF 41

42 Vehicle Level Event and Damage Related Data Elements V28 Areas of Impact - Initial / Most Damaged (V22) Previously called Impact Points Initial/Principal V29 Extent of Damage (V25) V30 Vehicle Removal (V26) V31 Sequence of Events (V33) Read-Only from Crash Events, All that apply element V32 Most Harmful Event (V34) V33 Related Factors Vehicle Level (V35) Modified by attribute removal (Pre-existing Vehicle Defects) V34 Fire Occurrence (V36) 2010 FARS/GES Changes TRF 42

43 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 2010 FARS/GES Changes TRF 43

44 AOI Attributes (Initial Damage / Most Damaged) AOI Attributes (Left) 61 Left AOI Vehicle Diagram AOI Attributes (Right) 81 Right 62 Left front half 82 Right front half 63 Left back half 83 Right back half Other attributes: 00 - Non Collision, 13 Top, 14 Undercarriage, 18 Set Inmotion (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 FARS/GES Changes TRF 44

45 Areas of Impact Area(s) of Impact Initial Damage Area (AOI/Initial) is derived from Crash Events. The first recorded AOI value for each vehicle in the table is populated on the vehicle level as the AOI/Initial. Identifies the area on each vehicle that produced the first instance of injury to occupants of the vehicle, non-motorists, or resulted in damage to the vehicle or other property FARS/GES Changes TRF 45

46 Areas of Impact Area(s) of Impact / Most Damaged Area: identifies the impact point for the area on this vehicle that was most damaged during an event it underwent in the crash. The most damaged area may or may not be associated with the Most Harmful Event for this vehicle. This is a significant change from the concept of Principal Impact which was associated with the Most Harmful Event for vehicles that only experienced collision events in the crash FARS/GES Changes TRF 46

47 AOI Attributes (Initial Damage / Most Damaged) Code Areas of Impact Most Damaged Principal 1 Blank % % 0 Non--Collision % % 1 1 Clock Point % % 2 2 Clock Point % % 3 3 Clock Point % % 4 4 Clock Point % % 5 5 Clock Point % % 6 6 Clock Point % % 7 7 Clock Point % % 8 8 Clock Point % % 9 9 Clock Point % % Clock Point % % Clock Point % % Clock Point % % 13 Top % % 14 Undercarriage % % 18 Set--In- Motion % % 61 Left % N/A x 62 Left--Front Half % N/A x 63 Left--Back Half % N/A x 81 Right % N/A x 82 Right--Front Half % N/A x 83 Right--Back Half % N/A x 98 Not Reported % N/A x 99 Unknown % %

48 Areas of Impact (Most Damaged) This is a MMUCC element, but the data has varied presentation on Crash Report forms. 12 States have AOI Mapping diagram that matches the 12 clock point diagram in the FARS/GES manual 20 States address something called Most Damaged Area on the report Difficult to establish expectations or identify problems when looking at the data. Arkansas D.C. Louisiana Shade Initial Circle all Damage Area Damaged 1 st, 2 nd, 3 rd 2010 FARS/GES Changes TRF 48

49 Areas of Impact Most Damaged Area.??? After implementation, experience in attempting to code Most Damaged in FARS and GES and checking of the data collected resulted in this data element being recommended for review and possible update in MMUCC for MMUCC Workshop is this afternoon from 1-5pm. V1 = 03??, 13 Top??? V2 =??? 2010 FARS/GES Changes TRF 49

50 Bus Use FARS - Previously (V13)/New Element (V21) GES New Element (V39) Definition: This data element describes the common type of bus service this vehicle was being used as at the time of the crash. Buses are any motor vehicle with seats to transport nine (9) or more people, including the driver s seat. This element does not include vans that are owned and operated for personal use FARS/GES Changes TRF 50

51 New Attributes for

52 Bus Use: Not A Bus Not a Bus is used for vehicles that do not have a bus Body Type AND are not being used as a bus in the crash. This should be used for vehicles with less than 9 seats (including the driver) and personal-use vans with 9 or more seats (including the driver) FARS/GES Changes TRF John + Kate + 8 = 10-Not a Bus John + Kate + 8 = 9 (Still Not a Bus!) 52

53 Bus Use vs. Body Type Bus Use Element: Describes if a vehicle is being used for common forms of bus service. Motor Vehicle Body Type: The category indicating the general configuration or shape of a motor vehicle Intercity is used when a company is providing for-hire, long-distance passenger transportation between cities over fixed routes with regular schedules (for example; Greyhound bus service between major cities). Charter/Tour is used when a company is providing transportation on a for-hire basis and demand-response basis, usually round-trip service for a tour group or outing. Body Type is Motorcoach Body Type is Motorcoach 2010 FARS/GES Changes TRF 53

54 Driver Level Condition (Impairment) at Time of Crash FARS: NEW element on the Driver and Not a Motor Vehicle Occupant Levels (D23/NM14) Duplicate attributes pulled from Driver and Person Level Related Factors. GES: P18 PERSON S PHYSICAL IMPAIRMENT (Drivers / Non-motorists) element renamed. New and modified attributes 2010 FARS/GES Changes TRF 54

55 Condition (Impairment) at Time of Crash Definition: This element attempts to identify physical impairments to this driver or non-motorist which may have contributed to the cause of the crash. These impairments can appear anywhere in the case materials--in the narrative section, in the violations section, in a column entitled Contributing Factors or Driver Action, etc. None/Apparently Normal Ill, Blackout Asleep or Fatigued Walking with a Cane or Crutches Paraplegic Or Restricted To Wheelchair Impaired Due To Previous Injury Deaf Blind Emotional (depressed, angry, disturbed, etc) Under the Influence of Alcohol, Drugs or Medication Physical Impairment No Details Other Physical Impairment Not Reported Unknown If Physically Impaired 2010 FARS/GES Changes TRF 55

56 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 ) FARS/GES Changes TRF 56

57 Precrash Data Implementing Precrash data in FARS allows FARS data to be used 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 FARS/GES Changes TRF 57

58 Precrash Level This form is available only for Motor Vehicles In-transport (Unit Type = 1) Captures data related to the vehicle itself, its driver, and its environment prior to it becoming a contact vehicle in the crash. As a process, the entire crash should first be completed from the perspective of one vehicle, then from the perspective of a second vehicle, if any, and so forth FARS/GES Changes TRF 58

59 Precrash Level The elements on this form are organized in a logical order: PC4 Relevant information about the vehicle before the crash PC5-PC13 Data relevant to the vehicle s environment before the Critical Event. PC14-PC17 Data relevant to the vehicle s driver before the Critical Event FARS/GES Changes TRF 59

60 Precrash Level The elements on this form are organized in a logical order: PC18, PC19 Event that made the situation critical for the vehicle. PC20-PC22 What the vehicle/driver did in response to the Critical Event. PC23 Summarizes the crash based on the vehicle/driver actions and FHE FARS/GES Changes TRF 60

61 Precrash Level The elements on this form all relate to the Critical Crash Envelope (CCE). Either before the CCE, e.g. PC4 Contributing Circumstances Motor Vehicle, PC17 Pre-Event Movement Or in response to the Critical Event, e.g. PC20 Attempted Avoidance, PC21 Pre- Impact Stability 2010 FARS/GES Changes TRF 61

62 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) FARS/GES Changes TRF 62

63 Simple Single CCE Example V1 runs the stop sign and strikes V2. Critical V1 V2 Category This vehicle traveling Other motor vehicle encroaching into lane Event Crossing over (passing through) intersection From crossing street across path No recognition CCE = Imminent path of a collision to Impact FARS/GES Changes TRF 63

64 Complex Single CCE Example: A pedestrian steps from the curb into the path of V1. V1 steers to the left, avoids the pedestrian and strikes V2 in the opposing travel lane. V1 V1 Recognition of Danger Impact 2010 FARS/GES Changes TRF V1 s Critical Event relates to the pedestrian, V2 s relates to V1 s action (encroachment) 64

65 Multiple CCE s Example: A pedestrian steps from the curb into the path of V1. V1 steers to the left, avoids the pedestrian and returns to its travel lane. V1 then enters the intersection and is struck by V2. V1 V1 V1 Recognition Control Impact 2010 FARS/GES Changes TRF V1 s CCE 1 relates to the pedestrian, V1 s CCE 2 relates to V2 and would be coded. 65

66 Precrash Level In terms of the timeline of a crash the information on this form ends when the vehicle has a harmful event. A vehicle becomes a contact vehicle in the crash (gets counted in the case) when it has a harmful event as part of the unstabilized situation. When a vehicle has a harmful event it ends the CCE for that vehicle FARS/GES Changes TRF 66

67 Precrash Level Unstabilized Situation versus CCE 2010 FARS/GES Changes TRF 67

68 Method for Determining Precrash Data First, determine the CCE and then the Critical Precrash Event The rest of the data pertain to this event Driver Distracted Pre-Event Movement Attempted Avoidance Maneuver Pre-Impact Stability Pre-Impact Location Crash Type PC16-PC FARS/GES Changes TRF 68

69 Determining Precrash Data Example 1 V1 was northbound on Edison Rd. V1 failed recognize slowing traffic ahead and steered into the southbound lane where it was struck by V2. Driver of V1 was unbelted and pronounced dead at the scene. V1 - V2 - CCE Starts D1 recognizes danger (prior to steering avoidance) When in imminent path of collision w/ V1 Event Related To: Non-contact vehicle slowing V1 s movement into its lane 2010 FARS/GES Changes TRF 69

70 Determining Precrash Data Example 2 V1 was northbound on Edison Rd in slow traffic. V1 driver was inattentive and entered into the southbound lane where it was struck by V2. Driver of V1 was unbelted and pronounced dead at the scene. V1 - V2 - CCE Starts When in imminent path of collision w/ V2 When in imminent path of collision w/ V1 Event Related To: Drifting over the lane line V1 s movement into its lane 2010 FARS/GES Changes TRF 70

71 Element Summary Example Critical Crash Envelope Pre-Event Movement Critical Precrash Category / Event Attempted Avoidance Maneuver Pre-Impact Stability Pre-Impact Location Crash Type 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? 2010 FARS/GES Changes TRF 71

72 Element Summary Example Critical Crash Envelope Driver Distracted Pre-Event Movement Critical Precrash Category / Event Attempted Avoidance Maneuver Pre-Impact Stability Pre-Impact Location Crash Type 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. 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? 72

73 Precrash Form Trafficway Characteristics element set are coded with respect to the vehicle s Precrash location (prior to the Critical Event) FARS/GES Changes TRF 73

74 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. Intersection Crashes V#2 - CCE 2010 FARS/GES Changes TRF 74

75 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 Nontrafficway Area Code will apply to all trafficway characteristics Trafficway Description Total Lanes in Roadway V#1 locks his brakes on his private Speed Limit driveway, swerves unsuccessfully and hits a bicyclist on the driveway access. Roadway Alignment and Grade Roadway Surface Type and Conditions Traffic Control Device / Functioning 2010 FARS/GES Changes TRF 75

76 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 2010 FARS/GES Changes TRF 76

77 Any Indication of Mis-use of Restraint System or Helmet Use Added in the 3 rd 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. SWT 2009 October 26th-30th 77

78 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. The investigating officer states in the crash report that two persons were secured in back of a pickup using a rope. The investigating officer states a child in a rear-facing restraint system was not properly secured in the vehicle. The investigating officer states that a child that should have been in a booster seat was unrestrained. Lap Belt Only Used Not Applicable Child Restraint System - Rear Facing None Used Motor Vehicle Occupant Yes No Yes No SWT 2009 October 26th-30th 78

79 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 Nonmotorist, 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 FARS/GES Changes TRF 79

80 5 New Elements Select All That Apply Select All That Apply 80

81 Case Example NM Elements N 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. NM10 Non-motorist Location 11 - Non-Intersection-On Roadway, Not in Marked Crosswalk NM11 Non-Motorist Action Prior to Crash 03 - Crossing Roadway 04 - Jogging/Running 2010 FARS/GES Changes TRF NM12 Non-Motorist Action At Time of Crash 01 - Dart / Dash 19 Not Visible (Dark Clothing, No Lighting, etc.) 81

82 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. In FARS and GES, Pedestrian and Bicycle Crash Typing is accomplished through a software application so that by simply following on-screen prompts and clicking on choices, the analyst/coder successfully enters data into the file without actually coding as in other elements FARS/GES Changes TRF 82

83 2010 FARS/GES Changes TRF 83

84 Ped/Bike Typing Limitations This application: Uses definitions specific to PBCAT Some will not match FARS/GES Does not use the full PBCAT application in FARS/GES Does not provide scenarios for multiple vehicles impacting the same person First contact is used 2010 FARS/GES Changes TRF 84

85 Questions? 2010 FARS/GES Changes TRF 85