ThatCarHitMe.com
An Injuria.ai Company
YEAR-OVER-YEAR CRASH REPORT · OHIO, OH · 2023
Purpose: Machine-readable JSON endpoint for AI agents, LLMs, researchers, and programmatic consumers. Returns all underlying crash data and AI-generated commentary without HTML.
Authentication: None required. Public endpoint.
GET: https://thatcarhitme.com/api/crash-data/reports/data/ohio/statewide/2023-annual-report
Yearly Traffic Safety Analysis
1,095 CRASHES IN
OHIO, OH
2023
In Auglaize County, total traffic crashes remained nearly stable, with 1,095 incidents in 2023 compared to 1,091 in 2022, an increase of less than half a percent. While crash and injury totals were consistent, the most notable year-over-year shift was a significant reduction in traffic fatalities, which decreased from seven in 2022 to two in 2023.
1,095
▲ 0.4%was 1,091
Total Crash Events
2
▼ -71.4%was 7
Persons Killed
268
▲ 0.4%was 267
Persons Injured
94
▲ 28.8%was 73
Hit-and-Run Crashes
Note: "Persons Killed" (2) counts individual fatalities across all crash events. "Fatal" in the severity table below (2) counts crash events where at least one fatality occurred. A single crash can result in multiple fatalities.
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2023-01-01 to 2023-12-31 · Aggregate counts from crash, person, and vehicle records
Trend Summary
The overall trend in crash volume in Auglaize County was stable year-over-year, with a minor increase of just four incidents. Similarly, the number of people injured was almost unchanged, rising from 267 to 268. However, the severity of outcomes improved, as the number of fatalities recorded in 2023 was less than a third of the total from the prior year.
94
Hit-and-Run Crashes — 2023
▲ 28.8% vs prior (73)
Hit-and-run incidents trended upward in 2023. The total number of hit-and-run crashes increased by 28.8%, rising from 73 in 2022 to 94 in 2023. As a percentage of all collisions, the hit-and-run rate also grew, climbing from 6.7% to 8.6% year-over-year.
Vulnerable Road User Casualties
0
Pedestrians Killed
2
Motorists Killed
1
Pedestrians Injured
267
Motorists Injured
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2023-01-01 to 2023-12-31 · Mode classified from person records (driver/passenger → motorist; pedestrian; bicyclist → cyclist; in-line skater / unspecified → other)
When Crashes Happen
The timing of crashes showed a distinct shift between the two periods. In 2023, the peak day for crashes was Friday with 181 incidents, changing from Monday (190 incidents) in the previous year. The daily peak hour also moved from the afternoon to the morning, shifting from 3 p.m. in 2022 (83 crashes) to 7 a.m. in 2023 (74 crashes).
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2023-01-01 to 2023-12-31 · Crash date field aggregated by weekday
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2023-01-01 to 2023-12-31 · Crash time field aggregated by hour (0-23)
Crash Severity Breakdown
Crash severity decreased notably from the prior year. The fatal crash rate dropped from 0.55% in 2022 to 0.18% in 2023, with fatal incidents falling from six to two. The proportion of serious injury crashes also declined from 2.0% to 1.3% of all crashes. Conversely, crashes involving possible injuries increased from 3.9% to 5.9% of the total.
Outcome by Severity (Crash Events)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2023-01-01 to 2023-12-31 · KABCO injury classification scale
Severity Distribution (Crash Events)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2023-01-01 to 2023-12-31 · Most severe injury per crash record
Road & Environmental Conditions
Driving conditions reported in crashes varied significantly year-over-year, particularly concerning adverse weather. Crashes on snowy or icy road surfaces saw a substantial decrease, accounting for only 2.6% of incidents (28 crashes) in 2023 compared to 11.2% (122 crashes) in 2022. In contrast, crashes on wet roads increased from 145 to 181, and incidents on dry roads rose from 820 to 875.
Weather
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2023-01-01 to 2023-12-31 · Weather condition at time of crash
Lighting
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2023-01-01 to 2023-12-31 · Lighting condition field
Road Surface
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2023-01-01 to 2023-12-31 · Road surface condition field
Vehicles & Demographics
The top vehicle makes involved in crashes shifted, with Chevrolet (253 vehicles) surpassing Ford (241 vehicles) in 2023; in the prior year, Ford was the most common make with 314 vehicles involved. Analysis of persons involved shows a notable demographic shift, as the 0-15 age group's representation grew from 10.3% of all persons in 2022 to 15.5% in 2023.
Top Vehicle Makes (1,600 vehicles)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2023-01-01 to 2023-12-31 · Vehicle unit records
78 persons with unknown or unrecorded age excluded from age chart.
Sex Distribution (2,063 persons with recorded sex)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2023-01-01 to 2023-12-31 · Person-level records linked to crash events
Data Sources & Methodology
Primary Data Source
All crash data in this report is sourced from Ohio Crash Data (ODOT TIMS), accessed programmatically via the Csv Open Data API (SODA). This dataset contains official police-reported motor vehicle traffic crash records maintained by the reporting jurisdiction's law enforcement agency. Records are published to the open data portal by the municipality and are subject to the portal's terms of use.
Data Retrieval
- Access method: Csv Open Data API (SoQL queries)
- Data format: Structured JSON via REST API
- Record types queried: Crash events, person records, and vehicle unit records
- Date filter applied: 2023-01-01 through 2023-12-31
- Report generated: July 5, 2026
Data Coverage
- Reporting period: 2023-01-01 through 2023-12-31 (365 days)
- Geographic scope: ohio, OH
- Total crash records analyzed: 1,095
- Total persons involved: 2,133
- Total vehicles involved: 1,600
Analytical Methodology
- Severity classification: Uses the KABCO injury scale (K=Fatal, A=Incapacitating injury, B=Non-incapacitating injury, C=Possible injury, O=No injury/property damage only), the standard classification in U.S. Model Minimum Uniform Crash Criteria (MMUCC). Severity is assigned per crash event based on the most severe injury in that crash. A single fatal crash (K) may involve multiple fatalities; therefore the "Persons Killed" count in the headline KPIs may differ from the "Fatal" crash count in the severity breakdown.
- Contributing factors: Reflect the officer-determined primary contributory cause recorded at the time of the crash report. These are preliminary determinations and may not reflect final investigation findings.
- Hit-and-run classification: Based on the hit-and-run indicator field in the official crash report, as determined by the responding officer at the scene.
- Temporal analysis: Day-of-week and hour-of-day distributions are computed from the crash date/time timestamp in each record.
- Demographics: Age and sex distributions are drawn from person-level records linked to each crash event. A single crash may involve multiple persons.
- Vehicle data: Make information is drawn from vehicle unit records linked to each crash event.
- AI commentary: Narrative sections are generated by Google Gemini (large language model) based on the structured data. Commentary is descriptive, not predictive, and should not be interpreted as expert opinion.
Limitations & Disclaimers
- Only crashes reported to and documented by law enforcement are included. Minor incidents, unreported crashes, and near-misses are not captured in this dataset.
- Data reflects conditions at the time of the initial police report and may be subject to subsequent corrections, reclassifications, or supplements by the reporting agency.
- Open data portal records may experience a publication lag - recently occurring crashes may not yet appear in the dataset at the time of report generation.
- AI-generated commentary is produced by a large language model and is intended to highlight patterns in the data. It does not constitute legal, medical, or professional analysis.
- Percentages are calculated from reported data and are subject to rounding.
Non-Affiliation Disclosure
This report is produced independently by ThatCarHitMe.com (Injuria.ai). It is not affiliated with, endorsed by, or produced in partnership with any law enforcement agency, municipal government, state department of transportation, or the National Highway Traffic Safety Administration (NHTSA). Data is sourced from publicly available government open data portals.
Data License
The underlying crash data is provided under the municipality's Open Data Terms of Use and is made available to the public for unrestricted use. This analysis and report is © 2026 Injuria.ai and may be cited with attribution using the suggested citation below.
Corrections & Feedback
If you believe any data in this report is inaccurate or have questions about our methodology, please contact: data@injuria.ai. We are committed to accuracy and will issue corrections promptly.
Suggested Citation
ThatCarHitMe.com (Injuria.ai). "ohio, OH Crash Intelligence Report: 2023." Published July 5, 2026. Reporting period: 2023-01-01 to 2023-12-31. Data source: Ohio Crash Data (ODOT TIMS), Csv Open Data. Available at: https://thatcarhitme.com/crash-data/ohio/statewide/2023-annual-report
About the Publisher
ThatCarHitMe.com is a crash data intelligence platform developed by Injuria.ai, a legal technology company specializing in traffic safety analytics. We aggregate and analyze publicly available government crash data to produce structured intelligence reports for communities, researchers, journalists, and legal professionals. Our reports combine programmatic data retrieval from official open data portals with AI-assisted narrative analysis.
Questions about this report's data or methodology: data@injuria.ai
ThatCarHitMe.com · An Injuria.ai Company
ThatCarHitMe.com
An Injuria.ai Company
Crash Data Intelligence
Data: Ohio Crash Data (ODOT TIMS) · Csv
Period: 2023-01-01 – 2023-12-31
Generated: July 5, 2026 · All rights reserved