Skip to main content
TruckCodex
Hubs

Crash Record OH0255049988

FMCSA crash record in TROY (TOWNSHIP OF) on Mar 19, 2025.

Tow-Away Federal Recordable

What happened

On March 19, 2025, FMCSA recorded a tow-away crash with no reported injuries in TROY (TOWNSHIP OF), Ohio. The vehicle was operated by UNITED PARCEL SERVICE INC (USDOT 21800). Recorded conditions: 5 / 1 / 1 pavement. FMCSA reference OH0255049988.

Carrier pattern note

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

Geographic note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
UNITED PARCEL SERVICE INC
USDOT 21800
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
2,597
81 fatal · 921 injury
Crashes per 100 power units (24 mo)
1.5
1,682 crashes · 112,321 units
Days since prior carrier crash
1
Last on Mar 18, 2025
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,881 carriers

Geographic context

How this crash sits in its setting.

Within TROY (TOWNSHIP OF), Ohio, 37 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
5
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 #:
OH0255049988
Date:
Mar 19, 2025
Time:
0725
State:
Ohio
City:
TROY (TOWNSHIP OF)
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
UNITED PARCEL SERVICE INC (21800)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
2 9 3 1FUJHTFW5PLUC0649 3410619 (IN) UNITED PARCEL SERVICE, 3 No

Crash event

Event sequence description.

1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT;3:18:COLLISION INVOLVING FIXED OBJECT;2:6:NONCOLLISION:EXPLOSION OR FIRE

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cmvottesl003xo3rbua6n3kmv Oct 21, 2026 KY Injury 0 1
cmvnd7c5m0021o3b5tlo8vbem Oct 20, 2026 NC Injury 0 3
cmvj4mhia002po3kf2gyvkuya Oct 15, 2026 OH Tow-Away 0 0
cmvettptu001xogss2nae0gcw Oct 14, 2026 IA Tow-Away 0 0
cmvettpt90017ogssat4b9tzd Oct 13, 2026 NJ Tow-Away 0 0
cmutcmzyv0047ku1lchqke1m7 Sep 28, 2026 MA Tow-Away 0 0
cmtwgmdz5000hpmiyo2frqnqj Sep 5, 2026 MI Tow-Away 0 0
cmtwgme2l004ppmiy5aj8lvhb Sep 3, 2026 KY Tow-Away 0 0
cmtwgme2a0043pmiyszslhsve Sep 3, 2026 NC Injury 0 1
cmtwgme08000zpmiys00h3101 Sep 3, 2026 NJ Tow-Away 0 0

Carrier booking & risk tools

Check booking and risk signals for USDOT 21800 — tools open pre-filled.

Book / don't book Insurance check Cancel desk Chameleon check Safety benchmark

Related records

Carrier
UNITED PARCEL SERVICE INC
USDOT 21800 · 28,027 crashes · 33,227 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 1FUJHTFW5PLUC0649
Decode this VIN for make, model, year, and recall data.
State
Crashes in Ohio
Statewide crash records.
City
Crashes in TROY (TOWNSHIP OF), OH
All crashes on file for this city.
Station
IR 80
Weigh / inspection station matching this crash location.
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.