Yearly Traffic Safety Analysis

5 CRASHES IN
ALEXANDRIA, OH
2022

All metrics benchmarked against2021

Total crashes in Alexandria decreased by 37.5% from 8 crashes in 2021 to 5 crashes in 2022. This notable decline in overall crash incidents was accompanied by a significant increase in the hit-and-run crash rate, which rose from 12.5% to 40% year-over-year.

5

-37.5%was 8

Total Crash Events

0

Persons Killed

0

Persons Injured

2

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

Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2022-01-01 to 2022-12-31 · Aggregate counts from crash, person, and vehicle records

Trend Summary

Overall, crash incidents in Alexandria showed a downward trend, decreasing from 8 total crashes in 2021 to 5 total crashes in 2022. This represents a 37.5% reduction in the total number of crashes year-over-year.

2

Hit-and-Run Crashes — 2022

100.0% vs prior (1)

The number of hit-and-run crashes increased from 1 incident in 2021 to 2 incidents in 2022. Consequently, the hit-and-run rate saw a substantial increase, rising from 12.5% of total crashes in 2021 to 40% in 2022.

When Crashes Happen

The peak day for crashes shifted from Thursday in 2021, with 4 incidents, to Friday in 2022, with 2 incidents. The peak hour remained 4 p.m. in both years, though the number of crashes at this hour decreased from 2 in 2021 to 1 in 2022.

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

Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2022-01-01 to 2022-12-31 · Crash time field aggregated by hour (0-23)

Road & Environmental Conditions

Crashes occurring in clear weather increased from 3 incidents in 2021 to 4 incidents in 2022, while cloudy weather crashes decreased from 4 incidents to 1 incident. In terms of lighting, crashes during daylight decreased from 6 in 2021 to 4 in 2022, while dawn/dusk crashes remained at 1 incident for both periods.

Weather

Clear4 (80.0%)
Cloudy1 (20.0%)

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

Lighting

Daylight4 (80.0%)
-33.3%prior 6
Dawn/Dusk1 (20.0%)

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

Vehicles & Demographics

Top Vehicle Makes (10 vehicles)

1
CHEVROLET3 (30%)
2
FORD2 (20%)
-60.0%prior 5
3
JOHN DEERE2 (20%)
4
ACURA1 (10%)
5
KIA1 (10%)
6
TOYOTA1 (10%)

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

Sex Distribution (10 persons with recorded sex)

Male9 (90.0%)
0.0%prior 9
Female1 (10.0%)
-75.0%prior 4

Source: Ohio Crash Data (ODOT TIMS) · Csv Open Data · 2022-01-01 to 2022-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: 2022-01-01 through 2022-12-31
  • Report generated: July 5, 2026

Data Coverage

  • Reporting period: 2022-01-01 through 2022-12-31 (365 days)
  • Geographic scope: Alexandria, OH
  • Total crash records analyzed: 5
  • Total persons involved: 10
  • Total vehicles involved: 10

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). "Alexandria, OH Crash Intelligence Report: 2022." Published July 5, 2026. Reporting period: 2022-01-01 to 2022-12-31. Data source: Ohio Crash Data (ODOT TIMS), Csv Open Data. Available at: https://thatcarhitme.com/crash-data/ohio/alexandria/2022-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

Alexandria, OH Crash Report — 2022 | ThatCarHitMe.com