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
259 CRASHES IN
OHIO, OH
2025
In 2025, Harrison County recorded 259 total crashes, a 3.2% increase from the 251 crashes documented in 2024. While the total number of injuries remained stable, decreasing by one from 112 to 111, the most significant year-over-year change was the doubling of fatalities from 2 in 2024 to 4 in 2025.
259
▲ 3.2%was 251
Total Crash Events
4
▲ 100.0%was 2
Persons Killed
111
▼ -0.9%was 112
Persons Injured
19
▼ -9.5%was 21
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 · 2025-01-01 to 2025-12-31 · Aggregate counts from crash, person, and vehicle records
Trend Summary
Overall traffic crashes in Harrison County saw a slight increase, rising from 251 in 2024 to 259 in 2025. Despite this modest rise in total incidents, the number of injuries remained nearly unchanged, decreasing from 112 to 111. However, fatalities increased from 2 to 4 over the same period.
19
Hit-and-Run Crashes — 2025
▼ -9.5% vs prior (21)
Hit-and-run incidents trended downward in the most recent period. The total number of hit-and-run crashes decreased from 21 in 2024 to 19 in 2025. As a percentage of all crashes, the hit-and-run rate also declined, falling from 8.4% to 7.3%.
Vulnerable Road User Casualties
4
Motorists Killed
111
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 temporal patterns of crashes showed minor shifts year-over-year. The peak day for crashes moved from Thursday in 2024 (42 crashes) to Wednesday in 2025 (42 crashes). The peak hour for collisions shifted slightly later in the day, from the 4 p.m. hour in the prior year (20 crashes) to the 5 p.m. hour in the current year (21 crashes).
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 shifted year-over-year, with fatal crashes doubling from 2 to 4, and the corresponding fatal crash rate increasing from 0.8% to 1.5%. While the total number of crashes involving any injury was identical at 81 for both periods, their composition changed significantly. Crashes resulting in serious injuries fell from 24 to 11, whereas crashes involving minor injuries rose from 41 to 57.
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 environmental conditions remained largely consistent between the two periods. The number of crashes on dry road surfaces was identical at 186, and incidents on wet roads were also stable with 54 in 2025 versus 53 in 2024. Crashes during daylight hours accounted for a slightly larger share of the total, rising from 138 to 153. The most notable change was an increase in crashes during snowfall, which grew from 9 in 2024 to 16 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
Ford and Chevrolet remained the top two vehicle makes involved in crashes, with counts for both increasing from the prior year. The involvement of Peterbilt vehicles doubled from 12 to 24. An analysis of persons involved in crashes reveals a demographic shift; there was a decrease in the 26-34 age group (from 76 to 66 people), while the number of people in the 45-54 and 65+ age groups increased from 45 to 66 and 41 to 62, respectively.
Top Vehicle Makes (367 vehicles)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-01-01 to 2025-12-31 · Vehicle unit records
15 persons with unknown or unrecorded age excluded from age chart.
Sex Distribution (445 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: 259
- Total persons involved: 455
- Total vehicles involved: 367
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