TruckCodex
Hubs

Crash Record OH0255003849

FMCSA crash record in LYME (TOWNSHIP OF) on Jan 2, 2025.

Fatal Federal Recordable

What happened

On January 2, 2025, FMCSA recorded a fatal crash that resulted in one death in LYME (TOWNSHIP OF), Ohio. The vehicle was operated by EXEL INC (USDOT 482746). Recorded conditions: 2 / 1 / 1 pavement. FMCSA reference OH0255003849.

Carrier pattern note

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

Fatalities
1
Injuries
0
Vehicles
2
Carrier
EXEL INC
Vehicle Type
Truck
Severity
Fatal

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
66
2 fatal · 20 injury
Crashes per 100 power units (24 mo)
5.9
46 crashes · 776 units
Days since prior carrier crash
7
Last on Dec 26, 2024
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,828 carriers

Geographic context

How this crash sits in its setting.

Within LYME (TOWNSHIP OF), Ohio, 6 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
2
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 #:
OH0255003849
Date:
Jan 2, 2025
Time:
0338
State:
Ohio
City:
LYME (TOWNSHIP OF)
Fatalities:
1
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
EXEL INC (482746)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
2 9 3 3AKJHLFG7LSLP4236 2891148 (IN) DHL SUPPLY CHAIN USA 3 No

Crash event

Event sequence description.

1:20:COLLISION INVOLVING OTHER MOVABLE 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
cmr318zre0019p8ayyje3v8cc Jun 25, 2026 OH Injury 0 1
cr_5127980 Mar 20, 2026 TX Tow-Away 0 0
cr_5102545 Feb 6, 2026 OH Injury 0 1
cr_5100210 Feb 4, 2026 TN Tow-Away 0 0
cr_5091647 Jan 21, 2026 KY Tow-Away 0 0
cr_5051533 Oct 23, 2025 SC Injury 0 1
cr_5060669 Oct 16, 2025 CA Injury 0 1
cr_5048972 Oct 13, 2025 PA Tow-Away 0 0
cr_5047679 Oct 10, 2025 GA Tow-Away 0 0
cr_5050779 Oct 9, 2025 PA Injury 0 1

Related records

Carrier
EXEL INC
USDOT 482746 · 848 crashes · 1,472 inspections
Vehicle
VIN: 3AKJHLFG7LSLP4236
Decode this VIN for make, model, year, and recall data.
State
Crashes in Ohio
Statewide crash records.
City
Crashes in LYME (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.