ThatCarHitMe.com
An Injuria.ai Company
YEAR-OVER-YEAR CRASH REPORT · ASHTABULA, OH · 2023
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/ashtabula/2023-annual-report
Yearly Traffic Safety Analysis
420 CRASHES IN
ASHTABULA, OH
2023
In Ashtabula, total crashes decreased slightly by 1.87%, from 428 in the prior year to 420 in the current year. Fatalities saw a significant decrease of 50%, falling from 2 to 1. Conversely, total injuries increased by 37.6%, rising from 125 to 172.
420
▼ -1.9%was 428
Total Crash Events
1
▼ -50.0%was 2
Persons Killed
172
▲ 37.6%was 125
Persons Injured
52
▼ -11.9%was 59
Hit-and-Run Crashes
Note: "Persons Killed" (1) 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 · 2023-01-01 to 2023-12-31 · Aggregate counts from crash, person, and vehicle records
Trend Summary
Overall, total crashes in Ashtabula showed a slight downward trend, decreasing by 1.87% year-over-year from 428 to 420. This indicates a relatively stable number of crash incidents, with a minor reduction. Despite the decrease in total crashes, the number of injured persons increased significantly.
52
Hit-and-Run Crashes — 2023
▼ -11.9% vs prior (59)
The number of hit-and-run crashes decreased by 11.86%, from 59 in the prior year to 52 in the current year. Concurrently, the hit-and-run crash rate decreased from 13.8% to 12.4%. This indicates a downward trend in both the count and proportion of crashes involving a hit-and-run.
Vulnerable Road User Casualties
0
Pedestrians Killed
1
Motorists Killed
3
Pedestrians Injured
169
Motorists Injured
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2023-01-01 to 2023-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 75 crashes in the prior year to Thursday with 77 crashes in the current year. The peak hour also changed, moving from 3 PM with 43 crashes in the prior year to 4 PM with 51 crashes in the current year. Notably, crashes on Monday decreased by 30.7% (from 75 to 52), while crashes on Saturday increased by 50% (from 50 to 75).
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2023-01-01 to 2023-12-31 · Crash date field aggregated by weekday
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2023-01-01 to 2023-12-31 · Crash time field aggregated by hour (0-23)
Crash Severity Breakdown
The fatal crash rate decreased from 0.47% in the prior year to 0.24% in the current year, corresponding to a 50% reduction in fatal crashes from 2 to 1. While serious injury crashes decreased from 12 to 10, minor injury crashes significantly increased by 53.2%, rising from 47 to 72. Overall, the total number of injury crashes (A, B, C) increased by 22.7% from 97 to 119.
Outcome by Severity (Crash Events)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2023-01-01 to 2023-12-31 · KABCO injury classification scale
Severity Distribution (Crash Events)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2023-01-01 to 2023-12-31 · Most severe injury per crash record
Road & Environmental Conditions
Crashes occurring in clear weather decreased from 268 to 229, while rain-related crashes increased by 60.6%, from 33 to 53. Regarding lighting conditions, crashes in 'Dark - Roadway Not Lighted' increased by 34.8% from 23 to 31. Crashes on wet road surfaces increased by 11.4% from 88 to 98, while those on snow-covered roads decreased by 25% from 24 to 18.
Weather
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2023-01-01 to 2023-12-31 · Weather condition at time of crash
Lighting
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2023-01-01 to 2023-12-31 · Lighting condition field
Road Surface
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2023-01-01 to 2023-12-31 · Road surface condition field
Vehicles & Demographics
There was a notable shift in the types of vehicles involved in crashes, with passenger cars decreasing by 14.5% (from 393 to 336) and SUVs increasing by 21.5% (from 181 to 220). Ford became the top make involved in crashes with 116 incidents, an increase of 27.5% from 91, surpassing Chevrolet which saw a 13% decrease from 131 to 114. Honda also experienced a decrease in crash involvement, falling by 19.2% from 73 to 59.
Top Vehicle Makes (766 vehicles)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2023-01-01 to 2023-12-31 · Vehicle unit records
38 persons with unknown or unrecorded age excluded from age chart.
Sex Distribution (1,006 persons with recorded sex)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2023-01-01 to 2023-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: 2023-01-01 through 2023-12-31
- Report generated: July 6, 2026
Data Coverage
- Reporting period: 2023-01-01 through 2023-12-31 (365 days)
- Geographic scope: Ashtabula, OH
- Total crash records analyzed: 420
- Total persons involved: 1,047
- Total vehicles involved: 766
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). "Ashtabula, OH Crash Intelligence Report: 2023." Published July 6, 2026. Reporting period: 2023-01-01 to 2023-12-31. Data source: Ohio Crash Data (ODOT TIMS), Csv Open Data. Available at: https://thatcarhitme.com/crash-data/ohio/ashtabula/2023-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: 2023-01-01 – 2023-12-31
Generated: July 6, 2026 · All rights reserved