1 / 71

2009 KANSAS Motor vehicle accident forms

2009 KANSAS Motor vehicle accident forms. TRAINING. OVERVIEW. ADS WORKFLOW / PRODUCTS BACKGROUND SYSTEM CHANGES IMPACT FOR LAW ENFORCEMENT FORMS CONTENT / LAYOUT DISCUSSION OF EACH FORM. ACCIDENT DATA processing. PRODUCTS ANNUAL FACTS AD HOC REQ. STUDIES OTHER. WORKFLOW LEA

lew
Download Presentation

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 • ADS WORKFLOW / PRODUCTS • BACKGROUND • SYSTEM CHANGES • IMPACT FOR LAW ENFORCEMENT • FORMS CONTENT / LAYOUT • DISCUSSION OF EACH FORM

  3. ACCIDENT DATA processing • PRODUCTS • ANNUAL FACTS • AD HOC REQ. • STUDIES • OTHER WORKFLOW LEA KDOT KCI KDOT THE WORLD

  4. 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

  5. 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

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

  7. 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)

  8. SYSTEM CHANGES • KDOT: • UPGRADING DATABASE (KCARS), ALL ASSOCIATED SOFTWARE, NEW FORMS, CODING MANUAL, ETC.

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

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

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

  12. TRS Portal – Index Concept

  13. TRS Portal - Overview

  14. TRS Portal –Site Structure

  15. IMPACT FOR LAW ENFORCEMENT • ELECTRONIC SUBMISSION FOR LE FORMS THROUGH ONE PORTAL • DATA AND REPORT ACCESS • Report Images, data for analysis, lat/long for accidents • VALIDATION OF REPORTS • WORKFLOW ADJUSTMENTS

  16. QUESTIONS - OVERVIEW

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

  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

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

  22. QUESTIONS

  23. 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.

  24. 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.

  25. ON ROAD CHANGE (pg 18) • 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

  26. ON ROAD NAME (pg 18) • Ensure On Road Names are consistently reported within your agency • Use the Hierarchy of road names and the name shown on street signs. • Parking lots, Multiple junctions, etc.

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

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

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

  30. ACC. LOCATION (pg 24) • 1ST HARMFUL EVENT: Key word – “Harm” • PLUS sign: See Intersection Type • New Codes: • Toll Plaza • Shoulder (separated)

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

  32. ACCIDENT CLASS (pg 6) • AccClass 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 30) • FHE / MHE: • Ensure that CWOV agrees with Accident Class • If AC FHE = 03, CWOV FHE is required. Same with MHE

  34. FIXED OBJECT (pg 30) • 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 according to the location of the accident.

  39. DIAGRAM (pg 33) • An accident diagram is required for all accidents (where possible) • “Vehicles moved” is not reason to leave blank

  40. 850A - QUESTIONS?

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

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

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

  44. 850B – DRIVERs Table (pg 41) • New: two phone numbers • New age specs. – same as KBI • Safety Equip: Do not use ‘Y’ (Yes) • Need wording for Child & Booster seats • Airbag coding

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

  46. 850B – DRIVER INFO (pg 44) • STATE CODES – Check list • DL – Accuracy is very important • DL Class: Record the “class” shown on the DL • Record “ID” if non-DL number is entered in DL field • For Permits: Enter the Class and then a P (like “CP”) • 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 46) • Driver’s License Compliance (Status) • Record the code that applies at the time of the accident. • The law determines the comply (status) code. • If not licensed for the type of vehicle they are diving, record 00.

  48. 850B – DRIVER INFO (pg 46) • Restrictions: Yes or No • List each restriction (on DL) • Mark if they complied with the Restriction • Note: a Permit is a “restricted” license which is different from having restrictions on the DL.

  49. 850B – DRIVER INFO (pg 46) • Mark the Endorsements that apply to the CDL license • At least one Endorsement is required per CDL even if it is Z - None. Leave blank for non-CDL DL

  50. 850B – DRIVER INFO (pg 47) • Method of Determination • Mark both sides for each driver involved • Mark all that apply • Ensure that these markings agree with CCs, Substance Use and Impairment Tests.

More Related