ThatCarHitMe.com
An Injuria.ai Company
YEAR-OVER-YEAR CRASH REPORT · BEAVER, OH · 2025
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/beaver/2025-annual-report
Yearly Traffic Safety Analysis
305 CRASHES IN
BEAVER, OH
2025
Current total crashes for 2025 were 305, an increase from 280 crashes in 2024, representing an 8.93% rise. Despite this increase, the most notable year-over-year shift was a significant decrease in total fatalities, from 3 in 2024 to 1 in 2025. This represents a 66.67% reduction in fatalities. Additionally, total injuries decreased by 8.67% year-over-year.
305
▲ 8.9%was 280
Total Crash Events
1
▼ -66.7%was 3
Persons Killed
137
▼ -8.7%was 150
Persons Injured
17
▲ 13.3%was 15
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 · 2025-01-01 to 2025-12-31 · Aggregate counts from crash, person, and vehicle records
Trend Summary
Overall, crashes in Beaver saw an upward trend year-over-year, increasing by 25 crashes from 280 in 2024 to 305 in 2025. This constitutes an 8.93% rise in total crash incidents. Despite the increase in total crashes, total injuries decreased from 150 to 137, an 8.67% reduction.
17
Hit-and-Run Crashes — 2025
▲ 13.3% vs prior (15)
Hit-and-run crashes increased slightly from 15 in 2024 to 17 in 2025. The hit-and-run rate also showed a marginal increase, rising from 5.4% in 2024 to 5.6% in 2025. This indicates a slight upward trend in the proportion of crashes involving a hit-and-run incident.
Vulnerable Road User Casualties
1
Motorists Killed
137
Motorists Injured
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-01-01 to 2025-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 remained Friday in both periods, with 63 crashes in 2025 compared to 59 in 2024. Similarly, the peak hour for crashes was 4 PM in both 2025 and 2024, with 32 and 29 crashes respectively. These patterns indicate consistency in the busiest times for crash occurrences year-over-year.
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-01-01 to 2025-12-31 · Crash date field aggregated by weekday
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-01-01 to 2025-12-31 · Crash time field aggregated by hour (0-23)
Crash Severity Breakdown
Fatal crashes decreased from 2 in 2024 to 1 in 2025, leading to a reduction in the fatal crash rate from 0.7% to 0.3% of total crashes. Total fatalities also decreased from 3 to 1 year-over-year. The proportion of serious injury crashes (code 'A') significantly dropped from 5% (14 crashes) in 2024 to 1.3% (4 crashes) in 2025. Overall, total injuries decreased by 13, from 150 in 2024 to 137 in 2025.
Outcome by Severity (Crash Events)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-01-01 to 2025-12-31 · KABCO injury classification scale
Severity Distribution (Crash Events)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-01-01 to 2025-12-31 · Most severe injury per crash record
Road & Environmental Conditions
Clear weather remained the most common condition for crashes, increasing from 156 crashes in 2024 to 172 in 2025. Crashes during daylight hours also increased from 179 to 196 year-over-year. The number of crashes on wet road surfaces increased from 58 in 2024 to 69 in 2025, while crashes on snowy surfaces rose from 24 to 28. Conversely, crashes during 'Dark - Roadway Not Lighted' conditions decreased from 72 to 59.
Weather
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-01-01 to 2025-12-31 · Weather condition at time of crash
Lighting
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-01-01 to 2025-12-31 · Lighting condition field
Road Surface
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-01-01 to 2025-12-31 · Road surface condition field
Vehicles & Demographics
The total number of vehicles involved in crashes increased from 453 in 2024 to 516 in 2025. Passenger cars and sport utility vehicles remained the most frequently involved vehicle types in both years, with passenger cars increasing from 181 to 191 and SUVs from 138 to 158. Chevrolet and Ford continued to be the top two vehicle makes involved in crashes, both seeing an increase in their counts year-over-year.
Top Vehicle Makes (516 vehicles)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-01-01 to 2025-12-31 · Vehicle unit records
38 persons with unknown or unrecorded age excluded from age chart.
Sex Distribution (688 persons with recorded sex)
Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-01-01 to 2025-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: 2025-01-01 through 2025-12-31
- Report generated: July 5, 2026
Data Coverage
- Reporting period: 2025-01-01 through 2025-12-31 (365 days)
- Geographic scope: Beaver, OH
- Total crash records analyzed: 305
- Total persons involved: 701
- Total vehicles involved: 516
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). "Beaver, OH Crash Intelligence Report: 2025." Published July 5, 2026. Reporting period: 2025-01-01 to 2025-12-31. Data source: Ohio Crash Data (ODOT TIMS), Csv Open Data. Available at: https://thatcarhitme.com/crash-data/ohio/beaver/2025-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: 2025-01-01 – 2025-12-31
Generated: July 5, 2026 · All rights reserved