1 / 74

2009 KANSAS Motor vehicle accident forms

2009 KANSAS Motor vehicle accident forms. TRAINING. OVERVIEW. BACKGROUND SYSTEM CHANGES IMPACT FOR LAW ENFORCEMENT FORMS CONTENT / LAYOUT DISCUSSION OF EACH FORM. BACKGROUND. 2005 FEDERAL TRAFFIC RECORDS ASSESSMENT FOR KANSAS ATTENDEES:

ion
Télécharger la présentation

2009 KANSAS Motor vehicle accident forms

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 2009 KANSAS Motor vehicle accident forms TRAINING

  2. OVERVIEW • BACKGROUND • SYSTEM CHANGES • IMPACT FOR LAW ENFORCEMENT • FORMS CONTENT / LAYOUT • DISCUSSION OF EACH FORM

  3. BACKGROUND • 2005 FEDERAL TRAFFIC RECORDS ASSESSMENT FOR KANSAS • ATTENDEES: • LAW ENFORCEMENT, KDOT, KDOR, KDHE, KBI, MARC, COURTS, EMS, INSURANCE, TRAMA, ETC • IDENTIFIED STRENGTHS AND WEAKNESSES

  4. DEFICIENCY FINDINGS • STATE DATABASES DO NOT TALK TO EACH OTHER (LACK OF DATA SHARING) • NO STATEWIDE DATABASES FOR CITATIONS, EMS, OR COURTS • LACK OF BAC REPORTING

  5. STATE IMPACT • INABILITY TO RETREIVE DATA EFFICIENTLY FROM STATE DATABASES IMPACTING CUSTOMERS, GOVERNMENT PARTNERS, AND DAY TO DAY PROCESSES. • LOSS OF…. $$$$$

  6. SYSTEM CHANGES • TRCC • Traffic Records Coordinating Committee • NEW DATABASES WILL BE ADDED • CURRENT STATE DATABASES WILL BE UPGRADED • DEVELOPMENT OF THE TRAFFIC RECORDS SYSTEM (TRS)

  7. SYSTEM CHANGES • KDOT: • UPGRADING THE KANSAS CRASH ANALYSIS AND REPORTING SYSTEM (KCARS), ALL ASSOCIATED SOFTWARE, NEW REPORTING FORMS, CODING MANUAL, ETC.

  8. SYSTEM CHANGES • KDOR: • NEW DATABASES FOR VEHICLES AND DRIVERS

  9. SYSTEM CHANGES • EMS: • NEW STATEWIDE DATABASE • COURTS: • WORKING TOWARDS A STATEWIDE SYSTEM

  10. SYSTEM CHANGES • CITATIONS: • NEW STATEWIDE DATABASE IS COMING ALONG WITH A STATEWIDE STANDARD FOR CITATIONS • KBI: • WORKING TOWARDS DATABASE AND FORMS CHANGES

  11. TRS Portal – Index Concept

  12. TRS Portal - Overview

  13. TRS Portal –Site Structure

  14. IMPACT FOR LAW ENFORCEMENT • ELECTRONIC SUBMISSION FOR LE FORMS THROUGH ONE PORTAL • DATA AND REPORT ACCESS • Report Images, data for analysis, latitude & longitude for accidents • VALIDATION OF REPORTS • INTERNAL WORKFLOW ADJUSTMENTS

  15. QUESTIONS - OVERVIEW • Questions can be answered by going to • ww.kstrs.org • emailing accidentdata@ksdot.org • or calling Rex McCommon at 785-296-5169

  16. FORMS LAYOUT / CONTENT • REVISION METHODOLOGY • Held meetings to discuss the current content /layout and determine what was to be added and/or subtracted • Every field was questioned • Committee: LEAs, state agencies, legal staff, safety advocacy groups, etc.

  17. FORMS LAYOUT / CONTENT • Additional Content: • All data considerations were evaluated • Law enforcement input • State requirements • Federal standards: ANSI D16, MMUCC, FARS, NCIC, CJIS, etc • Not everything was included: “Was it reasonable and prudent?”

  18. FORMS LAYOUT / CONTENT • 850A – ACCIDENT LEVEL DATA • 850B – DRIVERS AND VEHICLES • 851 – ACCIDENT NARRATIVE • 852 – TRUCK / BUS SUPPLEMENT • 854 – PASSENGER / PEDESTRIAN SUPP. • 855 – CODE SHEET

  19. FORMS LAYOUT / CONTENT • Design advantages: • Data for each subject is together • Supplemental forms per subject • Officers can “divide and conquer” on site • Assembling the reports later is a snap • Two versions: Paper & Electronic

  20. LOOK AT FORMS(overview)

  21. QUESTIONS

  22. 850A – ACCIDENT LEVEL DATA • Only one 850A per accident • Small diagram removed; large on back • Removed the State Use Only Fields • Paper Reports: • Circles indicate ONE selection; checkboxes can have multiple selections.

  23. REPORTING SEVERITY (pg 2) • Only one of the top 4 choices may be checked. • Private Property can be checked along with one of the other choices.

  24. ON ROAD CHANGE (pg 14) • BLOCK NO. – Record the specific address • DIR PFX – Only used if a road has a direction prefix in its name • DIR SFX – Only used if a road has a direction suffix in its name

  25. ON ROAD NAME (pg 14) • Ensure On Road Names are consistently reported • Use the Hierarchy of road names and the name shown on street signs. • Parking lots (p15) Multiple junctions (p19)

  26. ROAD TYPES (pg 17) • ROAD TYPE: Use these codes for roadways with such designations. Do not put the Road Type in the On Road Name field.

  27. AT/FROM CODING (pg 18) • When should From Distance, Ft/Mi, or From Direction contain values? • Answer: If the Accident Location is not ‘12’ and the FROM circle is marked.

  28. ACC. LOCATION (pg 22) • 1ST HARMFUL EVENT: Key word - Harm • PLUS sign: See Intersection Type • New Codes: • Toll Plaza • Shoulder (separated)

  29. WORK ZONES (pg 20-21) • TYPE: Should always contain a value. Mark the KDOT box for 01 & 02 only • Location: See Manual • Category: Mark the code that best applies

  30. INTERSECTION TYPE (pg 28) • Required for… Accident Location 12, 13, and 15 • L - Intersection: • See manual (pg 28) • Roundabouts/Traffic Circles • 08-Interchange: Should be coded with AL - 15

  31. Roundabout Coding (pg 28) • Required for… Accident Location 12, 13, and 15 • L - Intersection: • See manual (pg 28) • Roundabouts/Traffic Circles • 08-Interchange: Should be coded with AL - 15

  32. ACCIDENT CLASS (pg 30) • FHE / MHE: • BOTH must be coded per accident • They may differ or they can be the same • Ensure that CWOV and FxdObj agree with Accident Class

  33. CWOV (pg 31) • FHE / MHE: • Ensure that CWOV agrees with Accident Class • If AC FHE = 03, CWOV FHE is required. Same with MHE

  34. FIXED OBJECT (pg 33) • FHE / MHE: • Ensure that FxdObj agrees with Accident Class • If AC FHE = 08, FxdObj FHE is required. Same with MHE

  35. Questions 850A – Front?

  36. SPECIAL EVENT / DATA (pg 33) • EVENT: • State Fair • Football game • Festival • Data: • Misc. info.

  37. ROADWAY # LANES (pg 34) • INCLUDE BOTH DIRECTIONS: • If the roadway is under construction, record only the open lanes. • At Road data for AL = 12

  38. SPECIAL JURIS. (pg 34) • Formally on the 851 form…now recorded for all accidents

  39. DIAGRAM (pg 36) • An accident diagram is required for all accidents (where possible)

  40. 850A - QUESTIONS?

  41. 850B – DRIVER/PASS. DATA (pg 41) • 2 Drivers / Traffic Units per 850B • 4 Passengers – Passenger Table • No Pedestrians (use 854) • No Witnesses (use 851) • Coding Order – by Traffic Unit Type

  42. 850B – DRIVER DATA (pg 41) • Violations / Citations • Contributing Circumstances (CCs) • At least one per accident / driver / pedestrian even if it is 99 – unknown • Importance: Countermeasures • Inattention overuse – ineffective coding • CODES ARE RENUMBERED!!!

  43. 850B – DRIVERs Table (pg 43) • Two lines per driver • Seat Type is ALWAYS 01 in this table • Middle Name / Date of Birth Added • New Address? checkbox

  44. 850B – DRIVERs Table (pg 43) • New: two phone numbers • New age specs. – same as KBI (page 44) • Safety Equip: Do not use ‘Y’ (Yes) • Airbag coding

  45. 850B – DRIVERs Table (pg 45) • Ejection Path: for Partial and full ejections • Extrication: If someone is “Trapped”, they likely require extrication. • Transport Unit: Used only for vehicles taking someone to a hospital. (A,B,C,D,E,…)

  46. 850B – DRIVER INFO (pg 47) • STATE CODES – Check list • DL – Accuracy is very important • DL Class: Record the “class” shown on the DL • If the CMV driver is “on duty”, check the box • If the driver has a CDL DL, check the box

  47. 850B – DRIVER INFO (pg 91) • STATE/COUNTRY CODE CHANGES

  48. 850B – DRIVER INFO (pg 49) • Driver’s License Compliance (Status) • Record the code that applies at the time of the accident. • The law determines the status code. • If not licensed for the type of vehicle they are diving, record 00.

  49. 850B – DRIVER INFO (pg 49) • Restrictions: Yes or No • List each restriction (on DL) • Mark if they complied with the Restriction

  50. 850B – DRIVER INFO (pg 50) • Mark the Endorsements that apply to the CDL license • Endorsements are optional per CDL but required dependant on the driver’s function.

More Related