TruckCodex
Hubs

Crash Record OH0216124933

FMCSA crash record in HARRISON (TOWNSHIP OF) on Jul 12, 2021.

Injury Federal Recordable

What happened

On July 12, 2021, FMCSA recorded an injury crash with one person hurt in HARRISON (TOWNSHIP OF), Ohio. The vehicle was operated by UNIVERSAL DEDICATED OF FORT WAYNE IN LLC (USDOT 3222281). Recorded conditions: 1 / 1 / 1 pavement. FMCSA reference OH0216124933.

Carrier pattern note

This is the carrier's 11 crashes in the past 24 months — above the typical pattern (median 0) for fleets of 51–500 power units.

Geographic note

This crash is part of an active corridor: 112 crashes occurred in the same city in the past 24 months.

Fatalities
0
Injuries
1
Vehicles
2
Carrier
UNIVERSAL DEDICATED OF FORT WAYNE IN LLC
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
11
1 fatal · 3 injury
Crashes per 100 power units (24 mo)
4.5
14 crashes · 314 units
Days since prior carrier crash
69
Last on May 4, 2021
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,680 carriers

Geographic context

How this crash sits in its setting.

Within HARRISON (TOWNSHIP OF), Ohio, 112 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

Contributing factors

What the responding officer recorded.

Light
1
Weather
1
Road surface
1

Conditions are mixed. The data does not assign causation; this section reports only what was recorded by the responding officer.

Crash details

Key facts from the FMCSA crash record.

Report #:
OH0216124933
Date:
Jul 12, 2021
Time:
1510
State:
Ohio
City:
HARRISON (TOWNSHIP OF)
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
UNIVERSAL DEDICATED OF FORT WAYNE IN LLC (3222281)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
2 9 12 3HSDWTZR3LN806503 2875395 (IN) UNIVERSAL DEDICATED OF FORT WAYNE IN LLC 3 No

Crash event

Event sequence description.

1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5121982 Mar 16, 2026 MI Tow-Away 0 0
cr_5122746 Mar 10, 2026 OH Tow-Away 0 0
cr_5105498 Jan 26, 2026 IN Injury 0 1
cr_5083271 Dec 10, 2025 IN Tow-Away 0 0
cr_5048080 Oct 10, 2025 MI Injury 0 1
cr_5025469 Aug 26, 2025 IN Tow-Away 0 0
cr_5000753 May 26, 2025 MI Tow-Away 0 0
cr_4936782 Mar 27, 2025 IN Tow-Away 0 0
cr_4906184 Feb 12, 2025 IN Injury 0 1
cr_4899720 Feb 5, 2025 MI Tow-Away 0 0

Related records

Carrier
UNIVERSAL DEDICATED OF FORT WAYNE IN LLC
USDOT 3222281 · 47 crashes · 211 inspections
Vehicle
VIN: 3HSDWTZR3LN806503
Decode this VIN for make, model, year, and recall data.
State
Crashes in Ohio
Statewide crash records.
City
Crashes in HARRISON (TOWNSHIP OF), OH
All crashes on file for this city.
Index
All Crash Records
Browse FMCSA commercial vehicle crash records.
Database
Roadside Inspections
Inspection history and violation details.
Database
NHTSA Recalls
Active recall campaigns.

Frequently asked questions about FMCSA crash records

What does this crash report tell me about the carrier? ▾
An individual FMCSA crash record tells you that a commercial vehicle operated by this carrier was involved in a reportable crash on the date listed, along with the severity (fatalities / injuries / tow-away) and the responding agency. A single crash record does not tell you whether the carrier was at fault, whether the driver was cited, or how the crash affected the carrier's safety scores. To evaluate the carrier, compare the full multi-year crash history against the carrier's fleet size, miles driven, and cohort peers.
Was this crash the carrier's fault? ▾
FMCSA crash records do not assign fault. Fault attribution requires reviewing the police report, any litigation outcome, and FMCSA's preventability determination if one was requested. If you need a fault determination, request the underlying state police crash report (PAR) — the carrier or its insurer can pull this through standard channels.
How does this crash affect the carrier's safety scores? ▾
Crash records feed FMCSA's Crash Indicator BASIC inside the Safety Measurement System (SMS). Each FMCSA-reportable crash counts for two years from the crash date and is weighted by severity (fatal / injury / tow-only). The Crash Indicator score is normalized against the carrier's power-unit count and exposure, so larger fleets need more crashes to score the same percentile as smaller ones. Non-reportable crashes do not enter the score.
Will this crash show up on the carrier's CSA SMS scores? ▾
If the federal_recordable flag on this record is true, yes — it will appear in the carrier's Crash Indicator BASIC for two years from the crash date. Crashes flagged state-only (state_recordable) are visible on the public crash file but do not enter the federal score.
How do I check the carrier's full crash history? ▾
Click through to the carrier profile (the USDOT link near the top of this page). The carrier's profile lists every crash on file, severity counts, and links into the SMS detail when an MC docket is on record. You can also visit FMCSA's SAFER and SMS portals directly using the carrier's USDOT number.
What if details look wrong — how do I correct an FMCSA crash record? ▾
FMCSA's DataQs system handles corrections to crash records. Either the carrier or an interested third party can file a Request for Data Review (RDR) with supporting documentation (police report, court records, witness statements). Corrections are processed by the originating state agency and propagate to the federal file within roughly 60–120 days when accepted.