ThatCarHitMe.com
An Injuria.ai Company
YEAR-OVER-YEAR CRASH REPORT · BRYAN, OH · 2024
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/bryan/2024-annual-report
Yearly Traffic Safety Analysis
131 CRASHES IN
BRYAN, OH
2024
Total crashes in Bryan, OH, increased by 11.02%, from 118 in 2023 to 131 in 2024. While fatalities remained at zero in both periods, the number of persons injured rose by 28%, from 25 to 32. The most notable year-over-year shift was a 150% increase in motorcycle crashes, rising from 2 in 2023 to 5 in 2024.
131
▲ 11.0%was 118
Total Crash Events
0
Persons Killed
32
▲ 28.0%was 25
Persons Injured
12
▼ -7.7%was 13
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 · 2024-01-01 to 2024-12-31 · Aggregate counts from crash, person, and vehicle records
Trend Summary
Overall, crash incidents in Bryan, OH, show an upward trend year-over-year, with total crashes increasing from 118 in 2023 to 131 in 2024, representing an 11.02% rise. Concurrently, the total number of injuries saw a more significant increase of 28%, from 25 injured persons in 2023 to 32 in 2024. Despite the rise in incidents and injuries, fatal crashes remained stable at zero in both periods.
12
Hit-and-Run Crashes — 2024
▼ -7.7% vs prior (13)
The number of hit-and-run crashes decreased slightly year-over-year, from 13 incidents in 2023 to 12 in 2024. Consequently, the hit-and-run crash rate also saw a decline, dropping from 11% of total crashes in 2023 to 9.2% in 2024.
Vulnerable Road User Casualties
0
Pedestrians Killed
0
Motorists Killed
3
Pedestrians Injured
29
Motorists Injured
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2024-01-01 to 2024-12-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 shifted between the two periods. The peak day for crashes moved from Friday in 2023, with 21 incidents, to Wednesday in 2024, which recorded 33 crashes. Similarly, the peak hour for crashes changed from 1 PM in 2023, with 15 incidents, to 3 PM in 2024, which saw 19 crashes.
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2024-01-01 to 2024-12-31 · Crash date field aggregated by weekday
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2024-01-01 to 2024-12-31 · Crash time field aggregated by hour (0-23)
Crash Severity Breakdown
Fatalities remained at 0 in both 2023 and 2024, indicating no change in fatal crash outcomes. However, the number of crashes involving serious injuries (Severity A) increased from 0 in 2023 to 3 in 2024. The proportion of all injury crashes (Serious, Minor, Possible) rose from 12.71% (15 out of 118 total crashes) in 2023 to 21.37% (28 out of 131 total crashes) in 2024.
Outcome by Severity (Crash Events)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2024-01-01 to 2024-12-31 · KABCO injury classification scale
Severity Distribution (Crash Events)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2024-01-01 to 2024-12-31 · Most severe injury per crash record
Road & Environmental Conditions
Crashes occurring in clear weather conditions increased in count from 83 to 90, though their proportion of total crashes slightly decreased from 70.3% to 68.7%. Crashes on snow-covered roads saw a substantial increase, rising from 2 in 2023 to 6 in 2024. Additionally, crashes occurring in 'Dark - Lighted Roadway' conditions nearly doubled, increasing from 7 incidents in 2023 to 13 in 2024.
Weather
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2024-01-01 to 2024-12-31 · Weather condition at time of crash
Lighting
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2024-01-01 to 2024-12-31 · Lighting condition field
Road Surface
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2024-01-01 to 2024-12-31 · Road surface condition field
Vehicles & Demographics
The types of vehicles involved in crashes saw notable shifts, with Sport Utility Vehicle involvement increasing significantly from 61 in 2023 to 86 in 2024. Conversely, Passenger Van (minivan) involvement decreased from 18 to 10 incidents. Among vehicle makes, Ford and Toyota saw increased involvement, with Ford rising from 43 to 58 and Toyota from 7 to 14, while GMC and KIA saw decreased involvement.
Top Vehicle Makes (249 vehicles)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2024-01-01 to 2024-12-31 · Vehicle unit records
15 persons with unknown or unrecorded age excluded from age chart.
Sex Distribution (300 persons with recorded sex)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2024-01-01 to 2024-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: 2024-01-01 through 2024-12-31
- Report generated: July 5, 2026
Data Coverage
- Reporting period: 2024-01-01 through 2024-12-31 (366 days)
- Geographic scope: Bryan, OH
- Total crash records analyzed: 131
- Total persons involved: 309
- Total vehicles involved: 249
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). "Bryan, OH Crash Intelligence Report: 2024." Published July 5, 2026. Reporting period: 2024-01-01 to 2024-12-31. Data source: Ohio Crash Data (ODOT TIMS), Csv Open Data. Available at: https://thatcarhitme.com/crash-data/ohio/bryan/2024-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: 2024-01-01 – 2024-12-31
Generated: July 5, 2026 · All rights reserved