ThatCarHitMe.com
An Injuria.ai Company
YEAR-OVER-YEAR CRASH REPORT · HAMILTON, 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/hamilton/2025-annual-report
Yearly Traffic Safety Analysis
2,007 CRASHES IN
HAMILTON, OH
2025
Overall crash activity in Hamilton saw an increase, with total crashes rising from 1809 in the prior year to 2007 in the current year, marking a 10.95% increase. The most significant year-over-year shift was in fatalities, which more than doubled from 3 to 7, representing a 133.33% increase. Total injuries also increased by 8.52%, from 669 to 726.
2,007
▲ 10.9%was 1,809
Total Crash Events
7
▲ 133.3%was 3
Persons Killed
726
▲ 8.5%was 669
Persons Injured
418
▼ -0.7%was 421
Hit-and-Run Crashes
Note: "Persons Killed" (7) counts individual fatalities across all crash events. "Fatal" in the severity table below (5) 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
The overall trend indicates an increase in crash activity, with total crashes rising by 10.95% from 1809 to 2007 year-over-year. This upward trend also extends to fatalities and injuries, which increased by 133.33% and 8.52% respectively.
418
Hit-and-Run Crashes — 2025
▼ -0.7% vs prior (421)
Hit-and-run crashes decreased slightly from 421 in the prior year to 418 in the current year. Correspondingly, the hit-and-run rate decreased from 23.3% to 20.8%. This indicates a slight downward trend in both the number and proportion of hit-and-run incidents.
Vulnerable Road User Casualties
2
Pedestrians Killed
5
Motorists Killed
27
Pedestrians Injured
699
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 peak day for crashes shifted from Friday (346 crashes) in the prior year to Wednesday (326 crashes) in the current year. The peak hour for crashes remained 4 PM in both periods, with crashes at this hour increasing from 152 to 185. This suggests a shift in the day with the highest crash volume, while the peak hour of day remains consistent.
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
The fatal crash rate increased from 0.11% in the prior year to 0.25% in the current year. While serious injury crashes decreased slightly from 30 to 27, minor injury crashes increased from 274 to 323, and possible injury crashes saw a minor increase from 169 to 170. The proportion of crashes resulting in no injury remained stable at approximately 73.7-73.8% in both periods.
Severity is per crash event (most severe injury). 5 fatal crash events resulted in 7 persons killed.
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
Crashes occurring in clear weather conditions increased from 1120 to 1243, while those in rain decreased from 223 to 202. Crashes on snowy road surfaces saw a notable increase from 25 to 80. The number of crashes occurring in daylight increased from 1215 to 1369, and those on dry road surfaces rose from 1405 to 1545.
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
The age group with the largest increase in persons involved in crashes was 45-54, rising from 446 to 556. Chevrolet remained the most common vehicle make involved in crashes, increasing from 536 to 591, followed by Ford, which increased from 507 to 579. The top three vehicle makes involved in crashes (Chevrolet, Ford, Honda) maintained their ranking year-over-year.
Top Vehicle Makes (3,862 vehicles)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-01-01 to 2025-12-31 · Vehicle unit records
378 persons with unknown or unrecorded age excluded from age chart.
Sex Distribution (4,537 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 6, 2026
Data Coverage
- Reporting period: 2025-01-01 through 2025-12-31 (365 days)
- Geographic scope: Hamilton, OH
- Total crash records analyzed: 2,007
- Total persons involved: 4,859
- Total vehicles involved: 3,862
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). "Hamilton, OH Crash Intelligence Report: 2025." Published July 6, 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/hamilton/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 6, 2026 · All rights reserved