CRASH REPORTING DATA SYSTEM

1
CRASH REPORTING DATA SYSTEM

• SDARS General Data Entry Process

2
(No Transcript)
3
Receive Crash Report from reporting officer
4
AMERICAN NATIONAL STANDARD (ANSI.D16)

• Reports are analyzed using the AMERICAN NATIONAL
  STANDARD (ANSI.D16) as a guideline.
• There are over 20 data fields checked during this
  process.
• Reports with problems are either returned to the
  officer or the officer is called for
  clarification.

5
Review of Crash Reports before Processing

• Check Damage Amount exceeds 1,000 or has an
  Injury or death involved
• Check if its a fatal -- issue a Fatality Card
  (when needed)
• Check All Boxes are coded if not a wild animal
• Check Accident Location is complete
• Check Box 9 - Drug Use is coded 0-1 or 99
• Check Box 10 - Drug Test Status is coded 1-6 or
  99
• Check Box 13 - Travel Direction Before Accident
  (compare with diagram narrative)
• Check Box 16 - Vehicle Maneuver (compare with
  diagram narrative)
• Check Insurance Info is completed -- Mark with
  zeros if blank.
• Total Occupants needs to be 1 or higher if
  theres a driver listed
• Est Travel Speed should be coded 98, if left
  blank on report
• Check Emergency Vehicle Use? Should it really be
  checked YES? Most often is coded incorrectly
• Cross OFF Non-Contact Vehicles
• Mark Unit Type 5, 6 or 7 on front of report for
  Pedestrian, Bicyclist or Train
• Check Work Zone Related, Workers Present School
  Bus is completed
• Check Sequence of Events for completeness
  correctness (Box B has to match for single veh
  accident)
• Most Harmful First Harmful Event use codes 7-66
  ONLY
• Check Box A code (0) only if a single veh
  accident
• Check Box A B -- for correct coding for a
  Parked Car (0) (7)

6
Reports are sorted by County and then by Date of
Crash
7
REGISTRATION / SCANNING

• The next process is to register and scan the
  report.
• During this process the crash number is assigned,
  report is scanned allowing reports to be
  retrieved printed when needed.

8
DATA ENTRY

• The report is now ready to be entered into the
  South Dakota Accident Records (SDARS) System.
• During this process over one hundred fields are
  populated for a single vehicle, driver only,
  traffic crash.

9
VERIFY

• The report is now ready for Verification.
• The Verify process compares the officers coding
  on the crash report to SDARS allowable codes for
  out-of-range errors.
• Example When there is a code 5 in a field
  where there are only 4 options.

10
VALIDATE

• The report then moves into the Validation
  Process.
• Here codes are checked for consistency errors.
• EXAMPLE
• A crash occurring at 1300 hrs with Light
  Condition -Dark
  or
• Manner of Collision -- Head-on with only one
  vehicle involved
• Other common errors are Sequence of Events (25)
  Motor Vehicle in Transport is reported, when a
  wild animal is the First Harmful Event. Most
  Harmful Event/First Harmful Event (0-6) are
  reported, these codes are not considered harmful
  events.

11
DRIVERS LICENSE AUTHENTICATION

• Driver License Authentication is the next step.
• During this process the data entry information is
  fed to a mainframe drivers license database where
  a notation is made (for every driver involved) on
  the drivers history indicating the date, location
  and report number.
• Exact Drivers Name, Driver License Number and
  Date of Birth are required for an update to be
  made.

12
VEHICLE REGISTRATION AUTHENTICATION

• The next step is Vehicle Registration
  Authentication.
• During this process the officers vehicle codes
  are compared to the mainframe database vehicle
  registration file allowing Accident Records staff
  to correct Vehicle Identification Numbers (VIN)
  or License Plate Numbers.

13
CERTIFICATION

• The final processing procedure is Certification.
• In Certification the certifier uses the officers
  description of where the crash occurred to find
  the GIS Coordinates.
• This process includes an electronic map of every
  location in the state. The Certifier finds the
  location, updates the map with a click of the
  mouse.
• The click of the mouse automatically places the
  coordinates to the system. This final step
  updates the SDARS System and allows all data
  fields to be retrieved.

14
(No Transcript)
15

• CRASHES ARE A FILING SYSTEM
• and not connected or linked to the
• Judicial System.