Yearly Traffic Safety Analysis

2 CRASHES IN
CATAWBA, OH
2025

All metrics benchmarked against2024

Total crashes in Catawba decreased by 50% year-over-year, from 4 crashes in the prior period to 2 crashes in the current period. This reduction was accompanied by a 100% decrease in total injuries, falling from 1 to 0. A notable shift was observed in speeding-related crashes, which increased from 0 in the prior period to 2 in the current period.

2

-50.0%was 4

Total Crash Events

0

Persons Killed

0

-100.0%was 1

Persons Injured

0

-100.0%was 2

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. 2 crashes with unreported severity are not shown in the severity breakdown.

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

The overall trend indicates a significant decrease in crash activity, with total crashes falling by 50% from 4 to 2. Total injuries also decreased, moving from 1 injury in the prior period to 0 injuries in the current period. Fatalities remained stable at 0 in both periods.

When Crashes Happen

The peak crash day remained Saturday in both periods, with 1 crash recorded on this day in each period. However, the peak crash hour shifted from 11 p.m. in the prior period to 2 p.m. in the current period. Crashes in the current period occurred only on Sunday and Saturday, a change from the prior period which also saw crashes on Monday, Tuesday, and Wednesday.

Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-01-01 to 2025-12-31 · Crash date field aggregated by weekday

Road & Environmental Conditions

There was a shift in prevailing weather conditions for crashes, moving from predominantly clear weather in the prior period (3 out of 4 crashes) to adverse conditions like cloudy and snow in the current period (1 cloudy, 1 snow for 2 crashes). Similarly, road surface conditions shifted from mostly dry in the prior period (3 out of 4 crashes) to snow and wet conditions in the current period (1 snow, 1 wet for 2 crashes). Lighting condition data was only available for the prior period, preventing a year-over-year comparison for this metric.

Weather

Cloudy1 (50.0%)
Snow1 (50.0%)

Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-01-01 to 2025-12-31 · Weather condition at time of crash

Road Surface

Snow1 (50.0%)
Wet1 (50.0%)

Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-01-01 to 2025-12-31 · Road surface condition field

Vehicles & Demographics

Top Vehicle Makes (2 vehicles)

1
GMC1 (50%)
2
TOYOTA1 (50%)

Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2025-01-01 to 2025-12-31 · Vehicle unit records

Sex Distribution (2 persons with recorded sex)

Female1 (50.0%)
-50.0%prior 2
Male1 (50.0%)
-66.7%prior 3

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: Catawba, OH
  • Total crash records analyzed: 2
  • Total persons involved: 2
  • Total vehicles involved: 2

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). "Catawba, 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/catawba/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

Catawba, OH Crash Report — 2025 | ThatCarHitMe.com