ThatCarHitMe.com
An Injuria.ai Company
YEAR-OVER-YEAR CRASH REPORT · OHIO, OH · 2024
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/2024-annual-report
Yearly Traffic Safety Analysis
625 CRASHES IN
OHIO, OH
2024
In Holmes County, total traffic crashes increased by 6.1%, from 589 in 2023 to 625 in 2024. While the number of fatalities remained stable at four, total injuries rose by 16.8% from 226 to 264. The most notable shift was a 45% increase in crashes resulting in serious injuries, which grew from 20 incidents in the prior year to 29 in the current year.
625
▲ 6.1%was 589
Total Crash Events
4
Persons Killed
264
▲ 16.8%was 226
Persons Injured
28
▼ -12.5%was 32
Hit-and-Run Crashes
Note: "Persons Killed" (4) counts individual fatalities across all crash events. "Fatal" in the severity table below (4) 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 · 2024-01-01 to 2024-12-31 · Aggregate counts from crash, person, and vehicle records
Trend Summary
Overall traffic safety trends in Holmes County show an increase in collisions and injuries year-over-year. Total crashes rose by 6.1% (from 589 to 625), and the number of people injured increased by 16.8% (from 226 to 264). The number of fatalities, however, held steady at four for both periods.
28
Hit-and-Run Crashes — 2024
▼ -12.5% vs prior (32)
Hit-and-run incidents showed a downward trend compared to the prior year. The total number of hit-and-run crashes decreased from 32 to 28. This resulted in a lower hit-and-run rate, which fell from 5.4% of all crashes in 2023 to 4.5% in 2024.
Vulnerable Road User Casualties
0
Pedestrians Killed
4
Motorists Killed
5
Pedestrians Injured
259
Motorists Injured
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2024-01-01 to 2024-12-31 · Mode classified from person records (driver/passenger → motorist; pedestrian; bicyclist → cyclist; in-line skater / unspecified → other)
When Crashes Happen
The peak day for crashes shifted from Thursday (103 crashes) in 2023 to Friday (115 crashes) in 2024. The peak hour for collisions also moved slightly later in the day, from the 3 p.m. hour in the prior period to the 4 p.m. hour in the current period, with 56 crashes. Both peak hours occurred during the afternoon commute.
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2024-01-01 to 2024-12-31 · Crash date field aggregated by weekday
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2024-01-01 to 2024-12-31 · Crash time field aggregated by hour (0-23)
Crash Severity Breakdown
The severity of crashes worsened slightly compared to the previous year. The fatal crash rate increased from 0.51% to 0.64%, and the proportion of crashes involving a serious injury rose from 3.4% to 4.6%. Consequently, the share of crashes resulting in no injury decreased from 72.5% in 2023 to 70.4% in 2024.
Outcome by Severity (Crash Events)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2024-01-01 to 2024-12-31 · KABCO injury classification scale
Severity Distribution (Crash Events)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2024-01-01 to 2024-12-31 · Most severe injury per crash record
Road & Environmental Conditions
The distribution of crashes across lighting, weather, and road surface conditions remained broadly consistent year-over-year. The majority of collisions in both periods occurred during daylight (69.4% in 2024 vs. 66.4% in 2023) and on dry roads (78.9% vs. 79.6%). There was a small proportional decrease in crashes in dark, unlighted conditions, which accounted for 21.1% of crashes in 2024 compared to 26.5% in 2023.
Weather
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2024-01-01 to 2024-12-31 · Weather condition at time of crash
Lighting
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2024-01-01 to 2024-12-31 · Lighting condition field
Road Surface
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2024-01-01 to 2024-12-31 · Road surface condition field
Vehicles & Demographics
Sport Utility Vehicles were involved in 316 crashes, surpassing Passenger Cars (266 crashes) as the most common vehicle type, a reversal from the prior year. Ford (238 vehicles) and Chevrolet (157 vehicles) remained the top two vehicle makes involved in collisions, with both showing an increase in counts. The age demographics of persons involved in crashes were stable, with no significant shifts between the two periods.
Top Vehicle Makes (1,035 vehicles)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2024-01-01 to 2024-12-31 · Vehicle unit records
59 persons with unknown or unrecorded age excluded from age chart.
Sex Distribution (1,445 persons with recorded sex)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2024-01-01 to 2024-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: 2024-01-01 through 2024-12-31
- Report generated: July 5, 2026
Data Coverage
- Reporting period: 2024-01-01 through 2024-12-31 (366 days)
- Geographic scope: ohio, OH
- Total crash records analyzed: 625
- Total persons involved: 1,465
- Total vehicles involved: 1,035
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: 2024." Published July 5, 2026. Reporting period: 2024-01-01 to 2024-12-31. Data source: Ohio Crash Data (ODOT TIMS), Csv Open Data. Available at: https://thatcarhitme.com/crash-data/ohio/statewide/2024-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: 2024-01-01 – 2024-12-31
Generated: July 5, 2026 · All rights reserved