ThatCarHitMe.com
An Injuria.ai Company
YEAR-OVER-YEAR CRASH REPORT · OHIO, OH · 2025
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/2025-annual-report
Yearly Traffic Safety Analysis
642 CRASHES IN
OHIO, OH
2025
In 2025, Highland County recorded 642 total crashes, an 8.3% decrease from the 700 crashes reported in 2024. This downward trend was accompanied by a significant drop in traffic fatalities, which fell from 6 in the prior period to 2 in the current period. Total injuries remained relatively stable, with 273 in 2025 compared to 279 in 2024.
642
▼ -8.3%was 700
Total Crash Events
2
▼ -66.7%was 6
Persons Killed
273
▼ -2.2%was 279
Persons Injured
39
▼ -39.1%was 64
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 · 2025-01-01 to 2025-12-31 · Aggregate counts from crash, person, and vehicle records
Trend Summary
Overall, traffic crashes in Highland County showed a notable decrease year-over-year. The total number of crashes fell by 8.3%, from 700 in 2024 to 642 in 2025. This improvement was most pronounced in severe outcomes, with fatalities decreasing by 67% from 6 to 2.
39
Hit-and-Run Crashes — 2025
▼ -39.1% vs prior (64)
Hit-and-run incidents saw a significant decrease in 2025. The total number of hit-and-run crashes fell from 64 in 2024 to 39 in 2025. Consequently, the hit-and-run rate dropped from 9.1% of all crashes in the prior period to 6.1% in the current period, marking a clear downward trend.
Vulnerable Road User Casualties
0
Pedestrians Killed
2
Motorists Killed
2
Pedestrians Injured
271
Motorists Injured
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-01-01 to 2025-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 shifted between the two periods. In 2025, the peak day for crashes was Monday with 114 incidents, a change from Friday (122 incidents) in the prior year. Similarly, the peak hour for collisions moved to the 5 PM hour with 59 crashes in the current period, compared to the 2 PM hour with 51 crashes in 2024.
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-01-01 to 2025-12-31 · Crash date field aggregated by weekday
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-01-01 to 2025-12-31 · Crash time field aggregated by hour (0-23)
Crash Severity Breakdown
Crash severity decreased in 2025 compared to the previous year. The fatal crash rate fell from 0.57% to 0.31%, as the number of fatal crashes dropped from 4 to 2. The proportion of serious injury crashes also declined, accounting for 2.8% of all crashes in 2025 versus 4.4% in 2024. Crashes resulting in no injuries constituted the majority in both periods, at 71.0% in 2025 and 69.9% in 2024.
Outcome by Severity (Crash Events)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-01-01 to 2025-12-31 · KABCO injury classification scale
Severity Distribution (Crash Events)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-01-01 to 2025-12-31 · Most severe injury per crash record
Road & Environmental Conditions
The distribution of crashes across lighting conditions remained nearly identical year-over-year, with daylight crashes accounting for 65.3% in both periods. However, there was a shift in conditions related to precipitation. Crashes on wet roads decreased from 20.1% to 14.8% of the total, while crashes on snowy roads increased as a proportion of all incidents, rising from 2.1% in 2024 to 7.8% in 2025.
Weather
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-01-01 to 2025-12-31 · Weather condition at time of crash
Lighting
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-01-01 to 2025-12-31 · Lighting condition field
Road Surface
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-01-01 to 2025-12-31 · Road surface condition field
Vehicles & Demographics
Vehicle involvement patterns showed consistency year-over-year. Chevrolet (205 vehicles) and Ford (175 vehicles) remained the top two makes involved in crashes, though both saw a reduction in counts from 2024. The age demographics of persons involved in crashes also remained stable, with the 65+ and 16-20 age groups representing the largest cohorts in both periods.
Top Vehicle Makes (995 vehicles)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-01-01 to 2025-12-31 · Vehicle unit records
34 persons with unknown or unrecorded age excluded from age chart.
Sex Distribution (1,335 persons with recorded sex)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-01-01 to 2025-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: 2025-01-01 through 2025-12-31
- Report generated: July 5, 2026
Data Coverage
- Reporting period: 2025-01-01 through 2025-12-31 (365 days)
- Geographic scope: ohio, OH
- Total crash records analyzed: 642
- Total persons involved: 1,356
- Total vehicles involved: 995
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: 2025." Published July 5, 2026. Reporting period: 2025-01-01 to 2025-12-31. Data source: Ohio Crash Data (ODOT TIMS), Csv Open Data. Available at: https://thatcarhitme.com/crash-data/ohio/statewide/2025-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: 2025-01-01 – 2025-12-31
Generated: July 5, 2026 · All rights reserved