ThatCarHitMe.com
An Injuria.ai Company
YEAR-OVER-YEAR CRASH REPORT · HEATH, 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/heath/2025-annual-report
Yearly Traffic Safety Analysis
356 CRASHES IN
HEATH, OH
2025
Heath experienced a notable increase in crash incidents, with total crashes rising from 255 in the prior year to 356 in the current year, marking a 39.61% increase. This period also saw a 100% increase in total fatalities, from 1 to 2, and a 54.17% increase in hit-and-run crashes.
356
▲ 39.6%was 255
Total Crash Events
2
▲ 100.0%was 1
Persons Killed
97
▲ 15.5%was 84
Persons Injured
37
▲ 54.2%was 24
Hit-and-Run Crashes
Note: "Persons Killed" (2) counts individual fatalities across all crash events. "Fatal" in the severity table below (1) 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 crash trends in Heath indicate a significant rise year-over-year. Total crashes increased by 39.61%, from 255 to 356. This upward trend is also reflected in total fatalities, which doubled from 1 to 2, and total injuries, which increased by 15.48% from 84 to 97.
37
Hit-and-Run Crashes — 2025
▲ 54.2% vs prior (24)
Hit-and-run incidents increased significantly, with the number of hit-and-run crashes rising from 24 to 37, representing a 54.17% increase. Concurrently, the hit-and-run rate also saw an upward trend, increasing from 9.4% in the prior year to 10.4% in the current year.
Vulnerable Road User Casualties
0
Pedestrians Killed
2
Motorists Killed
1
Pedestrians Injured
96
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 distribution of crashes shifted, with the peak day moving from Monday in the prior year (54 crashes) to Friday in the current year (71 crashes). The peak crash hour also changed, occurring at 3 PM with 30 crashes in the prior year, compared to 5 PM with 47 crashes in the current year. This indicates a shift in when the highest volume of crashes occurs.
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
While the total number of fatalities increased from 1 to 2, the fatal crash rate decreased from 0.39% to 0.28% due to a larger overall increase in crashes. Serious injury crashes (severity 'A') saw a significant rise, increasing from 2 incidents (0.8% of total) to 10 incidents (2.8% of total). Possible injury crashes (severity 'C') saw a slight increase in count from 29 to 30, but their proportion of total crashes decreased from 11.4% to 8.4%.
Severity is per crash event (most severe injury). 1 fatal crash events resulted in 2 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 under various conditions increased year-over-year, aligning with the overall rise in crash incidents. Notably, crashes in snowy conditions increased from 4 to 19, and those on wet road surfaces increased from 44 to 60. Crashes in daylight conditions also rose from 196 to 272 incidents.
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 by 38.03%, from 497 to 686. Passenger cars, SUVs, and pickup trucks all saw increases in their involvement, while motorcycle crashes decreased from 8 to 5. Among demographics, persons in the 0-15 age group involved in crashes more than doubled from 49 to 103, and those in the 16-20 age group increased by 82.35% from 68 to 124.
Top Vehicle Makes (686 vehicles)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-01-01 to 2025-12-31 · Vehicle unit records
44 persons with unknown or unrecorded age excluded from age chart.
Sex Distribution (892 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: Heath, OH
- Total crash records analyzed: 356
- Total persons involved: 926
- Total vehicles involved: 686
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). "Heath, 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/heath/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