ThatCarHitMe.com
An Injuria.ai Company
YEAR-OVER-YEAR CRASH REPORT · OHIO, OH · DECEMBER 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/december-2025-report
Monthly Traffic Safety Analysis
311 CRASHES IN
OHIO, OH
DECEMBER 2025
In December 2025, Allen County recorded 311 total vehicle crashes, a 23.4% increase from the 252 crashes reported in December 2024. While fatalities remained at zero for both periods, total injuries rose from 68 to 80. The most significant year-over-year shift was a 60% increase in hit-and-run incidents, which grew from 25 to 40.
311
▲ 23.4%was 252
Total Crash Events
0
Persons Killed
80
▲ 17.6%was 68
Persons Injured
40
▲ 60.0%was 25
Hit-and-Run Crashes
Note: "Persons Killed" (0) counts individual fatalities across all crash events. "Fatal" in the severity table below (0) 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-12-01 to 2025-12-31 · Aggregate counts from crash, person, and vehicle records
Trend Summary
Crash data for Allen County indicates a rising trend in December when comparing 2025 to the previous year. Total crashes increased by 23.4%, from 252 to 311. Similarly, the number of people injured in these incidents rose by 17.6%, from 68 to 80, while fatalities held steady at zero in both periods.
40
Hit-and-Run Crashes — December 2025
▲ 60.0% vs prior (25)
Hit-and-run crashes showed a significant upward trend year-over-year. The absolute number of hit-and-run incidents increased by 60%, from 25 in December 2024 to 40 in December 2025. The hit-and-run rate, which measures these incidents as a percentage of total crashes, also rose from 9.9% to 12.9%.
Vulnerable Road User Casualties
0
Motorists Killed
80
Motorists Injured
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-12-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 shifted year-over-year. The peak day for crashes moved from Friday (53 crashes) in the prior period to Monday (61 crashes) in the current period. The peak hour also changed, shifting from 5 p.m. (21 crashes) in December 2024 to 2 p.m. (31 crashes) in December 2025.
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-12-01 to 2025-12-31 · Crash date field aggregated by weekday
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-12-01 to 2025-12-31 · Crash time field aggregated by hour (0-23)
Crash Severity Breakdown
There were no fatal crashes in either December 2025 or December 2024. The number of crashes resulting in serious injuries was unchanged at 3 for both periods. While the total number of injury-involved crashes increased from 53 to 57, they represented a smaller portion of all crashes, decreasing from 21.0% in the prior year to 18.3% in the current year.
Outcome by Severity (Crash Events)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-12-01 to 2025-12-31 · KABCO injury classification scale
Severity Distribution (Crash Events)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-12-01 to 2025-12-31 · Most severe injury per crash record
Road & Environmental Conditions
Year-over-year, the proportion of crashes on non-dry road surfaces increased from 39.7% to 46.0%, with notable increases in incidents on snow and ice. Conversely, the share of crashes occurring in adverse weather conditions decreased from 27.4% to 22.2%, despite the absolute number of such crashes remaining identical at 69. The percentage of crashes in dark or low-light conditions also fell from 56.7% to 46.3% of the total.
Weather
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-12-01 to 2025-12-31 · Weather condition at time of crash
Lighting
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-12-01 to 2025-12-31 · Lighting condition field
Road Surface
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-12-01 to 2025-12-31 · Road surface condition field
Vehicles & Demographics
Ford (85 vehicles) and Chevrolet (82 vehicles) were the top two vehicle makes involved in crashes during the current period, consistent with the prior year. The number of Chevrolets involved in crashes saw a notable increase from 53 to 82. An analysis of persons involved shows the proportion of individuals aged 16-25 decreased from 25.2% of the total in December 2024 to 20.7% in December 2025.
Top Vehicle Makes (518 vehicles)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-12-01 to 2025-12-31 · Vehicle unit records
51 persons with unknown or unrecorded age excluded from age chart.
Sex Distribution (671 persons with recorded sex)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-12-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-12-01 through 2025-12-31
- Report generated: July 6, 2026
Data Coverage
- Reporting period: 2025-12-01 through 2025-12-31 (31 days)
- Geographic scope: ohio, OH
- Total crash records analyzed: 311
- Total persons involved: 716
- Total vehicles involved: 518
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: December 2025." Published July 6, 2026. Reporting period: 2025-12-01 to 2025-12-31. Data source: Ohio Crash Data (ODOT TIMS), Csv Open Data. Available at: https://thatcarhitme.com/crash-data/ohio/statewide/december-2025-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-12-01 – 2025-12-31
Generated: July 6, 2026 · All rights reserved