Crash Record WV202503624A

FMCSA crash record in BECKLEY on Feb 10, 2025.

Injury Federal Recordable

What happened

On February 10, 2025, FMCSA recorded an injury crash with 2 people hurt in BECKLEY, West Virginia. The vehicle was operated by EXEL INC (USDOT 482746). Recorded conditions: 2 / 1 / 1 pavement. FMCSA reference WV202503624A.

Carrier pattern note

This is the carrier's 70 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: 38 crashes occurred in the same city in the past 24 months.

Fatalities

Injuries

Vehicles

Carrier

EXEL INC

Vehicle Type

Truck

Severity

Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

2 fatal · 24 injury

Crashes per 100 power units (24 mo)

5.9

46 crashes · 776 units

Days since prior carrier crash

Last on Feb 7, 2025

Vs fleet-size peers

above the median

Cohort median 0.0 · 3,835 carriers

Geographic context

How this crash sits in its setting.

Within BECKLEY, West Virginia, 38 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

FEDEX EXPRESS FEDEX · 2 reports
CALHOUN LOGGING COMPANY · 1 reports
BAGGETT TRANSPORTATION COMPANY · 1 reports

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 #:: WV202503624A
Date:: Feb 10, 2025
Time:: 2325
State:: West Virginia
City:: BECKLEY
Fatalities:: 0
Injuries:: 2
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	12	3AKJHLDR6RDUR1887	25498PZ (VA)	DHL SUPPLY CHAIN USA	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	Injuries
cmr318zre0019p8ayyje3v8cc	Jun 25, 2026	OH	Injury	1
cr_5127980	Mar 20, 2026	TX	Tow-Away	0
cr_5102545	Feb 6, 2026	OH	Injury	1
cr_5100210	Feb 4, 2026	TN	Tow-Away	0
cr_5091647	Jan 21, 2026	KY	Tow-Away	0
cr_5051533	Oct 23, 2025	SC	Injury	1
cr_5060669	Oct 16, 2025	CA	Injury	1
cr_5048972	Oct 13, 2025	PA	Tow-Away	0
cr_5047679	Oct 10, 2025	GA	Tow-Away	0
cr_5050779	Oct 9, 2025	PA	Injury	1

Related records

Vehicle

2024 FREIGHTLINER Cascadia

NHTSA recalls and complaints for this make/model/year.

ELECTRONIC STABILITY CONTROL (ESC)

Carrier

EXEL INC

USDOT 482746 · 848 crashes · 1,475 inspections

Vehicle

VIN: 3AKJHLDR6RDUR1887

Decode this VIN for make, model, year, and recall data.

State

Crashes in West Virginia

Statewide crash records.

City

Crashes in BECKLEY, WV

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.