Crash Database Improvement


The Wisconsin Department of Transportation (WisDOT), in collaboration with local law enforcement representatives and other stakeholders, embarked on an agency wide initiative to improve crash data collection and safety analysis capabilities by updating the Wisconsin MV4000 crash report form. The redesigned form rolled out on January 1, 2017 and serves as the basis for a new crash database management system that was deployed at the same time. Several important changes accompanied the rollout of the new crash report form including a requirement for all law enforcement agencies to submit crash reports electronically through the Wisconsin Badger TraCS system and an internal WisDOT reorganization that transferred stewardship of the crash data from the Division of Motor Vehicles to the Division of State Patrol. This article provides a summary of important information about the crash report redesign and what it means for analysts and other end users of Wisconsin crash data.

What is it?

A new crash report form (DT4000) and a new crash database were developed to more fully capture the conditions at the crash scene. The new form and database were developed using national standards from US DOT ( to improve safety from a national perspective. Additionally, the new form allows for more direct safety comparisons from state to state. The Badger TraCS online help manual and training were updated to ease the transition by law enforcement to the new crash report form.

The new form includes several new fields, including 77 at the crash level, 36 at the vehicle level, and 35 at the person level. At the same time 14 existing fields were deleted from the crash level, and four from the vehicle level. Additionally, at the crash level 11 fields have additions, 15 past fields have additions at the vehicle level, and 18 fields have additions at the person level.

An example of an existing field with additional choices being added is the location of a pedestrian at a crash. On the past form there were 5 choices for an officer at the scene of a crash to select. The  DT4000 includes 15 choices. A comparison is shown below.

Choices Chart

Why is it important?

The updates to the MV4000 and crash database are used to improve safety on Wisconsin roadways.

Previously, $12 million was granted to law enforcement to improve safety on the roads. Crash history is also a critical input for state and local safety engineering project planning and is an increasingly important requirement for MAP 21 performance measures. With more complete information about traffic crashes and a more complete crash database, unsafe roadways can be more easily and accurately identified, and the problems can be rectified with the ultimate goal of achieving zero deaths on Wisconsin roadways: Zero In Wisconsin.


EMS Run Number: The EMS run number is an important addition to the DT4000 because it allows for easier linkage between the crash information completed by the law enforcement officers, and hospital data from medical practitioners. The hospital data contains the health outcome of the patient and can provide more accurate and complete understanding of injury severity and the costs of traffic crashes.

What were the problems and how were they addressed?

The MV4000 crash report form did not contain specific fields for some common crash characteristics that would be beneficial to improving the safety of roadways in Wisconsin. Some of the characteristics not specifically on the MV4000 included guardrail crashes, roundabout crashes, and cell phone use during a crash. To determine whether one of these attributes were involved in a crash, report forms needed to be evaluated carefully and thoroughly, specifically the narrative written by the officer at the scene of the crash.

The DT4000 and crash database contain additional fields and choices for an officer to select from. These new fields make a more complete picture of the crash scene, both from the roadway characteristics (if a guardrail was involved, if the crash was at a roundabout) and from a human factors perspective (what the crash victims were doing at the time of the crash/ what caused the crash).

The addition of guardrails, and more intersection control choices (roundabouts, signals, stop signs) allow for safety analyses to be completed more easily, and ensures that all crashes, or crash types, at a particular location are accounted for.

Additionally, several fields were slightly changed to add more information allowing for a more complete picture of what happened before the crash (such as where the driver was located on the roadway and whether they were distracted, intoxicated, etc.), during the crash (such as the manner of collision, and the belt usage or safety equipment used by the crash victim, if any) , and a more complete picture of what happened to the crash victim(s) after a crash occurred (such as their injury severity, the EMS run number, and health outcomes assessed by medical practitioners).

How were existing analysis processes impacted?

The new crash report form and database provided more complete and descriptive information about the crash scene, but also introduced several challenges for previous processes. Applications that incorporated crash data from the Wisconsin Department of Transportation and/or the Traffic Operations and Safety (TOPS) Laboratory needed to be modified to accommodate the new set of elements. In addition, multiyear analyses that span the new and old forms needed to account for changes to crash report form field definitions and field choices. WisDOT provided guidance on how to best align new and old data elements.

What it’s not? The new crash report form and database were created for a more complete understanding of every crash to benefit the safety of the roadway, and highway users, i.e. safety equipment used or not used by motorcyclists, pedestrians, and vehicle occupants involved in a crash. The new form is not created for insurance purposes.

Text and information from ITE Wisconsin Newsletter and Wisconsin Traffic Safety Reporter.

Data Center



  • 2015 CIB Conference Crash Data (PPT, PDF)
  • 2015 TraCS User Group Conference Crash Data (PPT, PDF)
  • Gov Conf Safety Crash Data SP (PPT, PDF)


  • Crash Database Data Dictionary-February 2018 (XLSX)
  • February 2016 Report (PDF)
  • April 2016 Report (PDF)
  • May 2016 Report (PDF)
  • June 2016 Report (PDF)
  • July 2016 Report (PDF)
  • August 2016 Report (PDF)
  • September 2016 Report (PDF)
  • December 2016 Report (PDF)
  • May 2017 Newsletter (PDF)


  • DT4000 Forms (PPT) (Warning: large file)
  • DT4000 Forms Help (PDF)
  • Crash Documentation (PDF)
  • Crash Scenarios (PDF)
  • Handouts (PDF)
  • Milwaukee PD Crash Location Summary (PDF)


For questions with regards to the new crash report form, please contact:

For questions with regards to the new crash database, please contact