ThatCarHitMe.com
An Injuria.ai Company
YEAR-OVER-YEAR CRASH REPORT · CLEVES, 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/cleves/2025-annual-report
Yearly Traffic Safety Analysis
54 CRASHES IN
CLEVES, OH
2025
Total crashes in Cleves increased by 5.88%, from 51 in the prior year to 54 in the current year. A notable shift was the 100% increase in hit-and-run crashes, rising from 6 to 12 incidents year-over-year. Concurrently, DUI crashes decreased by 60%, from 5 to 2.
54
▲ 5.9%was 51
Total Crash Events
0
▼ -100.0%was 1
Persons Killed
10
▼ -9.1%was 11
Persons Injured
12
▲ 100.0%was 6
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-01-01 to 2025-12-31 · Aggregate counts from crash, person, and vehicle records
Trend Summary
Overall, total crashes in Cleves showed a slight increase, rising from 51 in the prior year to 54 in the current year. This represents a 5.88% increase in crash incidents year-over-year. The data indicates a minor upward trend in overall crash frequency.
12
Hit-and-Run Crashes — 2025
▲ 100.0% vs prior (6)
Hit-and-run crashes increased significantly, doubling from 6 in the prior year to 12 in the current year. This resulted in the hit-and-run crash rate rising from 11.8% to 22.2%, an increase of 10.4 percentage points. The data indicates a clear upward trend in hit-and-run incidents.
Vulnerable Road User Casualties
0
Motorists Killed
10
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 with 9 crashes in the prior year to Tuesday with 12 crashes in the current year. The peak hour also changed, moving from 10 p.m. with 6 crashes in the prior year to 5 p.m. with 7 crashes in the current year. This suggests a shift in when and on which days crashes are most frequent.
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
Fatalities decreased from 1 in the prior year to 0 in the current year, indicating no fatal crashes occurred. Total injuries also saw a slight decrease, from 11 to 10. While serious injuries remained stable at 1, minor injuries decreased from 4 to 2, and possible injuries increased from 4 to 6.
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 decreased from 34 to 29, while those in rainy conditions doubled from 5 to 10, and snow-related crashes increased from 2 to 7. Regarding lighting, crashes during daylight hours slightly increased from 30 to 32, but crashes in dark-lighted roadway conditions decreased from 13 to 7, while those in dark-roadway not lighted conditions more than doubled from 4 to 9. For road surface conditions, crashes on dry roads decreased from 40 to 33, whereas crashes on wet roads increased from 10 to 13, and those on snow-covered roads rose from 1 to 6.
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 total number of vehicles involved in crashes increased slightly from 91 to 94. While passenger cars remained relatively stable (45 to 44), sport utility vehicle involvement decreased from 21 to 15, cargo van involvement doubled from 3 to 6, and passenger van involvement increased from 1 to 6. Among top makes, Ford and Honda saw increased involvement, while Chevrolet and Jeep saw decreased involvement. The age group 65+ experienced a significant increase in persons involved, rising from 2 to 13, while the 16-20 age group saw a decrease from 23 to 14.
Top Vehicle Makes (94 vehicles)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-01-01 to 2025-12-31 · Vehicle unit records
10 persons with unknown or unrecorded age excluded from age chart.
Sex Distribution (102 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: Cleves, OH
- Total crash records analyzed: 54
- Total persons involved: 111
- Total vehicles involved: 94
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). "Cleves, 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/cleves/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