ThatCarHitMe.com
An Injuria.ai Company
CRASH INTELLIGENCE REPORT · BRICE, 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/brice/2023-annual-report
Yearly Traffic Safety Analysis
2 CRASHES IN
BRICE, OH
2023
In Brice during 2023, there were 2 total crashes, resulting in 1 fatality and 0 injuries. A notable finding is that 50% of these crashes were fatal, indicating a high severity for the incidents recorded in this period.
2
Total Crash Events
1
Persons Killed
0
Persons Injured
50.0%
Hit-and-Run Rate
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
1
Hit-and-Run Crashes — 2023
One of the 2 crashes recorded in Brice during 2023 was identified as a hit-and-run, representing 50% of all crashes. This hit-and-run status is based on the responding officer's initial determination at the scene.
Vulnerable Road User Casualties
In Brice during 2023, 1 pedestrian was killed, while no pedestrians were injured. There were no fatalities or injuries reported for cyclists or motorists in the crashes.
1
Pedestrians Killed
0
Pedestrians 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
Crashes in Brice during 2023 exclusively occurred on Monday, with 2 incidents. The peak hour for crashes was 10 PM, with 1 crash recorded. Regarding lighting conditions, 1 crash occurred in daylight and 1 crash occurred in dark conditions where the roadway was not lighted.
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2023-01-01 to 2023-12-31 · Crash date field aggregated by weekday
Crash Severity Breakdown
Of the 2 crashes in Brice during 2023, 1 crash (50%) was fatal, and 1 crash (50%) resulted in no injuries. There was 1 fatality across all crashes, which aligns with the single fatal crash recorded.
Outcome by Severity (Crash Events)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2023-01-01 to 2023-12-31 · Severity derived from reported fatal/injury indicators (no KABCO A/B/C codes)
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
During 2023 in Brice, lighting conditions were evenly split, with 1 crash occurring in daylight and 1 crash occurring in dark conditions where the roadway was not lighted. Data on weather and road surface conditions for crashes were not available.
Lighting
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2023-01-01 to 2023-12-31 · Lighting condition field
Vehicles & Demographics
Top Vehicle Makes (4 vehicles)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2023-01-01 to 2023-12-31 · Vehicle unit records
Sex Distribution (6 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: Brice, OH
- Total crash records analyzed: 2
- Total persons involved: 7
- Total vehicles involved: 4
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: 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/brice/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