Yearly Traffic Safety Analysis

21 CRASHES IN
DENNISON, OH
2024

All metrics benchmarked against2023

Overall crash data for Dennison shows a significant increase in 2024 compared to 2023, with total crashes rising by 133.3% from 9 to 21. This period also saw a 100% increase in total injuries, from 4 to 8. Notably, the proportion of crashes resulting in serious injuries appeared in 2024, whereas none were reported in 2023.

21

133.3%was 9

Total Crash Events

0

Persons Killed

8

100.0%was 4

Persons Injured

2

-33.3%was 3

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

The overall trend indicates a substantial increase in crash activity year-over-year, with total crashes rising from 9 in 2023 to 21 in 2024, representing a 133.3% increase. Concurrently, total injuries doubled from 4 in 2023 to 8 in 2024. Fatalities remained at zero in both periods.

2

Hit-and-Run Crashes — 2024

-33.3% vs prior (3)

Hit-and-run incidents decreased in both count and rate year-over-year. The number of hit-and-run crashes fell from 3 in 2023 to 2 in 2024. Consequently, the hit-and-run crash rate significantly decreased from 33.3% of total crashes in 2023 to 9.5% in 2024.

Vulnerable Road User Casualties

0

Motorists Killed

Prior: 00.0%

8

Motorists Injured

Prior: 4100.0%

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 distribution of crashes shifted year-over-year; the peak day for crashes moved from Monday in 2023 (4 crashes) to Friday in 2024 (5 crashes). The peak hour also changed from 7 PM in 2023 (2 crashes) to 3 PM in 2024 (3 crashes). Additionally, crash occurrences were distributed across more months in 2024 compared to 2023.

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

There was a notable shift in crash severity, with 2024 reporting 1 serious injury crash (4.8% of total crashes), a category not present in 2023. While minor injury crashes increased in count from 2 to 4, their proportion of total crashes slightly decreased from 22.2% in 2023 to 19% in 2024. The total number of injury-involved crashes (A+B+C) increased from 2 in 2023 to 6 in 2024.

Outcome by Severity (Crash Events)

Serious Injury1serious injury crashes4.8%
Minor Injury4minor injury crashes19%
100.0%prior 2
Possible Injury1possible injury crashes4.8%
No Injury15no injury crashes71.4%
114.3%prior 7

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

Weather conditions saw 'Clear' remain the dominant factor in both periods, although 'Cloudy' and 'Fog; Smog; Smoke' conditions were reported in 2024 but not 2023. Lighting conditions showed a shift, with 'Dark - Lighted Roadway' being the most frequent in 2023 (5 crashes) and 'Daylight' becoming the most frequent in 2024 (12 crashes). Road surface conditions remained predominantly 'Dry' in both years, with a slight increase in 'Wet' conditions from 2 to 3 crashes.

Weather

Clear16 (76.2%)
128.6%prior 7
Cloudy2 (9.5%)
Fog; Smog; Smoke1 (4.8%)
Other/Unknown1 (4.8%)
Rain1 (4.8%)

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

Lighting

Daylight12 (57.1%)
Dark - Lighted Roadway4 (19.0%)
-20.0%prior 5
Dawn/Dusk4 (19.0%)
Other/Unknown1 (4.8%)

Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2024-01-01 to 2024-12-31 · Lighting condition field

Road Surface

Dry17 (81.0%)
142.9%prior 7
Wet3 (14.3%)
Other/Unknown1 (4.8%)

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

Vehicles & Demographics

Top Vehicle Makes (38 vehicles)

1
CHEVROLET11 (28.9%)
2
TOYOTA4 (10.5%)
3
FORD4 (10.5%)
-33.3%prior 6
4
HONDA4 (10.5%)
5
DODGE3 (7.9%)
6
KIA2 (5.3%)
7
LINCOLN2 (5.3%)
8
NISSAN2 (5.3%)
9
MITSUBISHI1 (2.6%)
10
CADILLAC1 (2.6%)

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

1 persons with unknown or unrecorded age excluded from age chart.

Sex Distribution (39 persons with recorded sex)

Male21 (53.8%)
133.3%prior 9
Female18 (46.2%)
50.0%prior 12

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: Dennison, OH
  • Total crash records analyzed: 21
  • Total persons involved: 41
  • Total vehicles involved: 38

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). "Dennison, 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/dennison/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

Dennison, OH Crash Report — 2024 | ThatCarHitMe.com