Safety

Crash Data

 

Crash Data Intelligence

 

 

 

Photo by Shane Chevalier, CDOT R1

Crash Data Process | Events

Crash Data News

2018 Crash Data is now available. See below for information on obtaining summary data.

The Colorado Department of Transportation (CDOT) maintains a crash database for purposes of improving traffic and highway safety as required by 23 U.S.C. 148, 23 U.S.C. Section 405, requirements of the Fatality Analysis Reporting System (FARS) as well as other federal and state rules and guidance.

Crash Data Process

Process

When a crash occurs, after an officer investigates and fills out a crash form (DR2447), the form is sent to the Department of Revenue (DOR). DOR processes the records and enters them into a database called DRIVES where the official, legal record is maintained. CDOT receives data from the DRIVES system for all crashes, excluding private property and counter reports. (Counter reports are self-reported by drivers and are not investigated by a law enforcement officer.)

CDOT processes or “cleanse” the crash data received from DOR. This process adds an additional field for crash type, corrects common errors, updates location information where available, and normalizes the data. This cleansing process creates a working database that CDOT then analyzes for various programs and safety projects. Some examples of how this data is used is to identify crash patterns, over representation of crashes for a specific roadway type or volume, statewide planning, development of crash mitigation projects, identification of behavioral patterns for the development of behavioral programs such as “click it or ticket” and Holiday DUI campaigns.

CDOT typically compiles data and releases the data in 6 month increments, with approximately a 3 month delay when data is available. CDOT may delay the release of data to address known deficiencies allowing for data corrections or to download additional data that is delayed through the DOR process.

FARS is a separate database containing only fatal records and contains more detailed fields than the more general state database that includes all crashes. FARS is a nationwide census providing the National Highway Traffic Safety Administration (NHTSA), Congress, and the American public yearly data regarding fatal injuries suffered in motor vehicle traffic crashes. Fatal data is finalized and published on December 31 of the following year. For example, 2015 fatal data was published on December 31, 2016. This allows for a thorough examination of records to ensure the most accurate data possible. The information in the FARS database is collected through a variety of sources, including coroner toxicology results, death certificates, initial fatal blotter notifications, and fatal supplement information. Fatal crashes included in the database meet the NHTSA definition of a fatal crash, which may not include all crashes involving a death. Examples of crashes that are not in the FARS database include deaths not resulting from the injuries sustained in the crash such as suicides or medical conditions.

Data Requests:

CDOT provides summary data upon request. Summary data is in tabular format and is provided for a specific location or geographic area, filtered for a specific type of crash, weather condition, and/or date range.

CDOT does not release personal identifying information including names, driver’s license numbers, addresses, birth dates, license plate numbers, VIN numbers, local and state identifiers such as case numbers, etc.

CDOT only provides summary data and does not provide or publish the database in its entirety.

To improve timeliness and help ensure that the data provided meets the requestor’s needs, it is recommended that the following information be included by the requestor:

Location. The location that data is being requested for. Provide mile posts if possible for highways or at a minimum, cross street information for the beginning and end points on a corridor. LAT/Long and GIS data is not available for most non highway crashes so if local roads are included in the request, CDOT will attempt to provide the data as close to what is requested as possible.

Date. Beginning and end dates for the request, such as January 1, 2015 – June 30, 2015, or the most recent five years of data.  For engineering analysis, we generally recommend 3 years of data for high volume roadways in urban areas and 5 years of data for more rural, low volume roadways. This typically provides sufficient information for safety analyses and is a general rule of thumb for engineering analysis.

CDOT does have older data, but the data formats have changed, and not all fields were collected historically or the data may require research or manipulation to obtain. Contact the CDOT Traffic Engineering Branch, Data Unit, if you have larger requests going back more than 10 years to discuss your specific data needs and determine if CDOT has the data desired.


Upcoming Traffic & Safety Engineering Branch Events

Contact Us
Mission & Vision
  • Our mission is to strategically reduce traffic crashes and resulting deaths, injuries, and property damage, and improve the flow of traffic via traffic engineering principles.

  • Our vision is to become the state agency sought-out leader for applying traffic engineering principles to improve traffic safety and maximize the operations of the highway system, and the foremost resource for crash data, analysis, and engineering strategies - and mitigation for improving highway safety and operational efficiency.
Colorado: The Official State Web Portal