2023 Crash Locations
Reported traffic crashes in Ohio during 2023, mapped to where they happened, with the severity, circumstances and contributing factors recorded on each crash report.
- Published by
- ODOT Highway Safety Program
- Source
- Ohio Department of Transportation TIMS
- Original data
- tims.dot.state.oh.us
- Terms of use
- Public information, no warranty (ODOT)
- On the map
- Points
Ask State Planner a question about this data in plain language, and get the answer as a written explanation and a map.
Sign up to askFrom the publisher
Crash locations for the year 2023. ODOT’s crash data system uses the OH1 Report provided by DPS and law enforcement agencies around the state to compile crash data and break it down by different attributes. These attributes are used in AASHTOWare Safety crash analysis tool to summarize crash trends around the state.
Questions answered with this data
- Color every state-highway segment by its fatal and serious-injury crash rate per 100 million vehicle miles over 2021–2025, in quintiles, and mark the worst 25 stretches on top.
- For the MORPC area around Columbus, compute fatalities, serious injuries, each as a count and as a rate per 100 million vehicle miles, and non-motorized fatalities and serious injuries, for each of the last five years, and map where they fall.
- For the MVRPC metropolitan planning area around Dayton (the MVRPC polygon in the MPO data set, which covers Montgomery, Miami, Greene and the northern part of Warren County), count fatal and serious-injury crashes for each year from 2021 through 2025, counting each crash report once by its crash severity. Use the same scope as MVRPC's Safety Action Plan: leave out crashes on restricted-access freeways (functional class 1 and 2, which covers I-70, I-75, I-675 and the freeway sections of US 35 and SR 4), crashes on freeway ramps, and crashes with no location. Split each year into urban and rural, where urban means inside ODOT's Adjusted Urbanized Areas. Show one table with a row per year and columns for urban fatal, rural fatal, urban serious injury, rural serious injury, and total fatal plus serious injury. Then show a second table, by year, of the fatal and serious-injury crashes that the freeway and ramp exclusions removed. Map the counted crashes colored by severity, draw the excluded freeway crashes in gray, and outline the MVRPC boundary and the urbanized areas.
- The NOACA area around Cleveland has $10 million for safety improvements on state routes. Choose where to spend it to prevent the most fatal and serious-injury crashes, using 2021–2024 crashes and two countermeasures. The first is centerline and shoulder rumble strips at $25,000 per mile, which cut lane-departure crashes by 30% on two-lane segments posted 45 mph or higher. The second is roundabouts at $2 million each, which cut angle crashes by 60% at intersections. Rank candidates by crashes prevented per dollar, pick the best mix within the budget, and map the chosen segments and intersections with the expected crashes prevented at each.
Fields
What each record holds, as the publisher describes it: 19 fields.
| Field | Description |
|---|---|
Document Number DOCUMENT_NBR | Unique number assigned to each crash. It will be the same for the crash level record, unit level record and people level record. The first four numbers will designate the crash year. |
Year CRASH_YR | Year of crash |
Month MONTH_OF_CRASH | Month of crash |
Day in Week DAY_IN_WEEK_CD | Number associated with the day of week the crash occurred. Number associated with the day of week the crash occurred. 1-SUNDAY, 2-MONDAY, 3-TUESDAY, 4-WEDNESDAY, 5-THURSDAY, 6-FRIDAY, 7-SATURDAY |
Hour HOUR_OF_CRASH | Hour of crash |
Severity Code CRASH_SEVERITY_CD | Code indicating the five-level severity of the crash |
Severity CRASH_SEVERITY_TXT | Severity of the crash |
Crash Type Code CRASH_TYPE_CD | Code indicating ODOT's calculated crash type, similar to manner of collision but expanded for engineering purposes |
Crash Type CRASH_TYPE_TXT | ODOT's calculated crash type |
ODOT Crash Location Code ODOT_CRASH_LOCATION_CD | Code indicating the type of location that best describes where the first event of the crash occurred |
ODOT Crash Location ODOT_CRASH_LOCATION_TXT | Type of location that best describes where the first event of the crash occurred |
Functional Class FUNCTIONAL_CLASS_CD | The roadway classes for the FHWA approved Functional Class system. This is based upon assignment of roads into systems according to the character of service they provide in relation to the total road network upon which the crash occurred. |
ODOT Number of Lanes ODOT_LANES_NBR | The number of lanes in both directions carrying through traffic upon which the crash occurred |
County Code COUNTY_CD | County abbreviation for the section of roadway in which the crash occurred |
ODOT District ODOT_DISTRICT | From 1-12 plus Central Office – the counties are grouped into districts in Ohio for ease of maintenance and funding. |
Latitude ODOT_LATITUDE_NBR | Latitude (Y) coordinate at which the crash occurred, in decimal degrees. |
Longitude ODOT_LONGITUDE_NBR | Longitude (X) coordinate at which the crash occurred, in decimal degrees. |
NLFID | ODOT’s Network Linear Feature ID for the route upon which the crash occurred |
CLT Begin Number CTL_BEGIN_NBR | The County True Log representing the point along the route at which the crash occurred |