ThatCarHitMe.com
An Injuria.ai Company
YEAR-OVER-YEAR CRASH REPORT · BRICE, 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/brice/2024-annual-report
Yearly Traffic Safety Analysis
5 CRASHES IN
BRICE, OH
2024
Total crashes in Brice increased by 150% year-over-year, rising from 2 crashes in the prior period to 5 crashes in the current period. This increase in incidents was accompanied by a decrease in total fatalities from 1 to 0, while total injuries rose from 0 to 2. The most notable shift is the substantial increase in overall crash frequency.
5
▲ 150.0%was 2
Total Crash Events
0
▼ -100.0%was 1
Persons Killed
2
Persons Injured
0
▼ -100.0%was 1
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 Brice show a significant upward trend year-over-year, with total crashes increasing by 150%. This represents a rise from 2 crashes in the prior period to 5 crashes in the current period. Despite this increase in incidents, fatal crashes decreased from 1 to 0, though total injuries rose from 0 to 2.
Vulnerable Road User Casualties
0
Motorists Killed
2
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 peak day for crashes shifted from Monday in the prior period, which recorded 2 crashes, to Wednesday in the current period, also with 2 crashes. In the current period, crashes were more distributed throughout the week, occurring on Sunday, Tuesday, Wednesday, and Saturday, compared to only on Monday in the prior period. Due to insufficient data for the prior period, a comparison of peak hours cannot be made.
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
Fatal crashes decreased from 1 in the prior period to 0 in the current period, resulting in no fatalities in the current year compared to 1 fatality previously. Conversely, total injuries increased from 0 in the prior period to 2 in the current period. The severity distribution shifted from 50% fatal crashes and 50% no-injury crashes in the prior period, to 40% injury crashes (minor and possible) and 60% no-injury crashes in the current period.
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
The proportion of crashes occurring in daylight conditions increased from 1 out of 2 crashes (50%) in the prior period to 4 out of 5 crashes (80%) in the current period. Correspondingly, crashes in dark conditions remained at 1 crash in both periods, but decreased in proportion from 50% to 20%. Data for weather and road surface conditions were not available for a meaningful comparison.
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
Vehicles & Demographics
Top Vehicle Makes (11 vehicles)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2024-01-01 to 2024-12-31 · Vehicle unit records
Sex Distribution (18 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 6, 2026
Data Coverage
- Reporting period: 2024-01-01 through 2024-12-31 (366 days)
- Geographic scope: Brice, OH
- Total crash records analyzed: 5
- Total persons involved: 18
- Total vehicles involved: 11
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). "Brice, OH Crash Intelligence Report: 2024." Published July 6, 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/brice/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 6, 2026 · All rights reserved