ThatCarHitMe.com
An Injuria.ai Company
CRASH INTELLIGENCE REPORT · EDISON, OH · 2021
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/edison/2021-annual-report
Yearly Traffic Safety Analysis
5 CRASHES IN
EDISON, OH
2021
In Edison, OH, during 2021, there were 5 total crashes, resulting in 0 fatalities and 0 injuries. The most frequent collision type was rear-end, accounting for 60% of all crashes.
5
Total Crash Events
0
Persons Killed
0
Persons Injured
0
Fatal Crash Events
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. 5 crashes with unreported severity are not shown in the severity breakdown.
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2021-01-01 to 2021-12-31 · Aggregate counts from crash, person, and vehicle records
When Crashes Happen
Crashes in 2021 were most frequent on Wednesdays and Thursdays, with 2 crashes occurring on each of these days. The peak hour for crashes was 3 PM, which saw 3 incidents. The majority of crashes, 4 out of 5, occurred during daylight conditions, with only 1 crash happening in the dark on an unlighted roadway.
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2021-01-01 to 2021-12-31 · Crash date field aggregated by weekday
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2021-01-01 to 2021-12-31 · Crash time field aggregated by hour (0-23)
Road & Environmental Conditions
Regarding lighting conditions, 4 of the 5 crashes (80%) occurred during daylight hours. One crash (20%) was recorded in dark conditions on a roadway that was not lighted. Data for weather and road surface conditions were not available.
Lighting
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2021-01-01 to 2021-12-31 · Lighting condition field
Vehicles & Demographics
Top Vehicle Makes (10 vehicles)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2021-01-01 to 2021-12-31 · Vehicle unit records
1 persons with unknown or unrecorded age excluded from age chart.
Sex Distribution (19 persons with recorded sex)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2021-01-01 to 2021-12-31 · Person-level records linked to crash events
Traffic Control Device
Among the recorded instances of traffic control, 'No Control' was the most frequent designation, accounting for 5 instances. Signalized locations were associated with 3 instances, while stop signs were noted in 2 instances.
Traffic Control Device
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2021-01-01 to 2021-12-31 · Vehicle unit records
Pre-Crash Driver Action
Immediately prior to crashes, the most common driver actions were 'Straight Ahead' in 4 instances and 'Slowing or Stopped In Traffic' in 3 instances. These two actions collectively represent 70% of the recorded pre-crash actions for vehicles involved.
Pre-Crash Driver Action
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2021-01-01 to 2021-12-31 · Vehicle unit records
Vehicle Type
Pick up trucks were the most frequently involved vehicle type, accounting for 4 out of 10 vehicles. Passenger Cars were involved in 3 instances, and Sport Utility Vehicles in 2 instances. Pick up trucks represent a notable 40% of all vehicles involved.
Vehicle Type
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2021-01-01 to 2021-12-31 · Vehicle unit records
Person Type
Drivers were the dominant role among persons involved in crashes, with 10 drivers out of 19 total persons. Occupants accounted for the remaining 9 persons. No pedestrians or cyclists were recorded as being involved.
Person Type
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2021-01-01 to 2021-12-31 · Crash-level records
Occupant Safety Equipment
Safety equipment use was recorded for all 19 persons involved in crashes. 'Shoulder and Lap Belt Used' was reported for 16 individuals, while 'Child Restraint System - Forward Facing' was used by 3 individuals. There were no instances of reported non-use of safety equipment.
Occupant Safety Equipment
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2021-01-01 to 2021-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: 2021-01-01 through 2021-12-31
- Report generated: July 5, 2026
Data Coverage
- Reporting period: 2021-01-01 through 2021-12-31 (365 days)
- Geographic scope: Edison, OH
- Total crash records analyzed: 5
- Total persons involved: 19
- Total vehicles involved: 10
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). "Edison, OH Crash Intelligence Report: 2021." Published July 5, 2026. Reporting period: 2021-01-01 to 2021-12-31. Data source: Ohio Crash Data (ODOT TIMS), Csv Open Data. Available at: https://thatcarhitme.com/crash-data/ohio/edison/2021-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: 2021-01-01 – 2021-12-31
Generated: July 5, 2026 · All rights reserved