ThatCarHitMe.com
An Injuria.ai Company
YEAR-OVER-YEAR CRASH REPORT · OHIO, OH · JULY 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/july-2025-report
Monthly Traffic Safety Analysis
201 CRASHES IN
OHIO, OH
JULY 2025
In July 2025, Allen County recorded 201 total crashes, an 8.7% increase from the 185 crashes reported in July 2024. The most notable year-over-year change was the increase in traffic fatalities, which rose from zero in the prior period to three in the current period. Correspondingly, the number of people injured in crashes increased from 79 to 93.
201
▲ 8.6%was 185
Total Crash Events
3
Persons Killed
93
▲ 17.7%was 79
Persons Injured
25
▲ 19.0%was 21
Hit-and-Run Crashes
Note: "Persons Killed" (3) counts individual fatalities across all crash events. "Fatal" in the severity table below (3) 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-07-01 to 2025-07-31 · Aggregate counts from crash, person, and vehicle records
Trend Summary
Overall, crash trends in Allen County are rising year-over-year. Total crashes increased by 8.7% from 185 in July 2024 to 201 in July 2025. This upward trend is also reflected in the number of people injured, which rose from 79 to 93, and fatalities, which increased from zero to three.
25
Hit-and-Run Crashes — July 2025
▲ 19.0% vs prior (21)
Hit-and-run incidents increased in both count and proportion year-over-year. The number of hit-and-run crashes rose from 21 in July 2024 to 25 in July 2025. This corresponds to an increase in the hit-and-run rate, which climbed from 11.4% to 12.4% of all crashes.
Vulnerable Road User Casualties
0
Pedestrians Killed
3
Motorists Killed
2
Pedestrians Injured
91
Motorists Injured
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-07-01 to 2025-07-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 some shifts between the two periods. The peak day for crashes moved from Wednesday in July 2024 to Tuesday in July 2025, though the peak volume remained identical at 42 crashes. The peak hour of the day shifted significantly, moving from the 4 p.m. hour in the prior period (17 crashes) to the 12 p.m. hour in the current period (21 crashes).
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-07-01 to 2025-07-31 · Crash date field aggregated by weekday
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-07-01 to 2025-07-31 · Crash time field aggregated by hour (0-23)
Crash Severity Breakdown
Crash severity worsened in July 2025 compared to the previous year. The county recorded three fatal crashes, accounting for 1.5% of all incidents, whereas there were no fatal crashes in July 2024. The proportion of crashes resulting in serious injuries also increased from 3.8% (7 crashes) to 6.0% (12 crashes) year-over-year. Consequently, the share of crashes with no reported injuries decreased from 69.7% to 68.2%.
Outcome by Severity (Crash Events)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-07-01 to 2025-07-31 · KABCO injury classification scale
Severity Distribution (Crash Events)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-07-01 to 2025-07-31 · Most severe injury per crash record
Road & Environmental Conditions
Crash conditions remained largely consistent year-over-year, with the majority of incidents in both periods occurring in daylight and on dry roads. In July 2025, 77.1% of crashes happened in daylight, compared to 73.0% in the prior year. There was a slight increase in the proportion of crashes occurring on wet roads, rising from 16.2% in July 2024 to 19.4% in July 2025.
Weather
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-07-01 to 2025-07-31 · Weather condition at time of crash
Lighting
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-07-01 to 2025-07-31 · Lighting condition field
Road Surface
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-07-01 to 2025-07-31 · Road surface condition field
Vehicles & Demographics
The makes of vehicles involved in crashes remained consistent, with Chevrolet and Ford being the top two in both periods; they tied for first place with 58 vehicles each in July 2025. The age distribution of persons involved in crashes saw some shifts; the 35-44 age group became the most frequently involved group in the current period with 69 people, an increase from 55 the previous year. The 16-20 age group also saw a slight increase in involvement from 58 to 61 people.
Top Vehicle Makes (370 vehicles)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-07-01 to 2025-07-31 · Vehicle unit records
19 persons with unknown or unrecorded age excluded from age chart.
Sex Distribution (437 persons with recorded sex)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-07-01 to 2025-07-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-07-01 through 2025-07-31
- Report generated: July 6, 2026
Data Coverage
- Reporting period: 2025-07-01 through 2025-07-31 (31 days)
- Geographic scope: ohio, OH
- Total crash records analyzed: 201
- Total persons involved: 455
- Total vehicles involved: 370
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: July 2025." Published July 6, 2026. Reporting period: 2025-07-01 to 2025-07-31. Data source: Ohio Crash Data (ODOT TIMS), Csv Open Data. Available at: https://thatcarhitme.com/crash-data/ohio/statewide/july-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-07-01 – 2025-07-31
Generated: July 6, 2026 · All rights reserved