Crash Record WV202215104A

FMCSA crash record in NITRO on Jun 27, 2022.

Injury Federal Recordable

What happened

On June 27, 2022, FMCSA recorded an injury crash with one person hurt in NITRO, West Virginia. The vehicle was operated by FEDEX FREIGHT INC (USDOT 239039). Recorded conditions: 1 / 1 / 1 pavement. Reported by FEDEX FREIGHT, FMCSA reference WV202215104A.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

FEDEX FREIGHT INC

Vehicle Type

Truck

Severity

Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

899

29 fatal · 281 injury

Crashes per 100 power units (24 mo)

2.8

500 crashes · 17,633 units

Days since prior carrier crash

Last on Jun 24, 2022

Vs fleet-size peers

above the median

Cohort median 0.0 · 3,837 carriers

Geographic context

How this crash sits in its setting.

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

Agencies most active in this area:

AMBA TRANSPORTATION LLC · 1 reports
AMERICAN RAPID TRANSPORT LLC · 1 reports
10 ROADS EXPRESS · 1 reports

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 #:: WV202215104A
Date:: Jun 27, 2022
Time:: 0904
State:: West Virginia
City:: NITRO
Fatalities:: 0
Injuries:: 1
Tow-Away:: Yes
HazMat:: No
Vehicles:: 3
Carrier (USDOT):: FEDEX FREIGHT INC (239039)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	5	3	4VN19TG07N465976	1176627 (IN)	FEDEX FREIGHT	3	No

Other crashes by this carrier

10 additional crash record(s) on file.

Record	Date	State	Severity	Injuries
cmtgtnbz9001zpmmoal2fv4et	Aug 26, 2026	PA	Tow-Away	0
cmsw88sju00l1pev3ndvovb0h	Aug 6, 2026	KY	Tow-Away	0
cmqvwanqb000rp8iu8r2r96dl	Jun 22, 2026	AZ	Injury	2
cmq0fazcw003jpmw8b2frpcvi	May 27, 2026	KY	Tow-Away	0
cmpqehz12000vqiysev1c23b2	May 23, 2026	NC	Tow-Away	0
cmp0olg5i000nnuqwp1a692zk	May 6, 2026	TN	Tow-Away	0
cmogoa8io006jnvt8c1z52yl8	Apr 21, 2026	TN	Tow-Away	0
cmo6itlu400oqo1aujr86f1rh	Apr 9, 2026	VA	Tow-Away	0
cmny3yfoo002ik38vzcv0psxm	Apr 7, 2026	NC	Injury	4
cmny3yg7000i5k38vpr37idhu	Apr 3, 2026	AR	Tow-Away	0

Related records

Carrier

FEDEX FREIGHT INC

USDOT 239039 · 9,457 crashes · 10,104 inspections

State

Crashes in West Virginia

Statewide crash records.

Agency

FEDEX FREIGHT

Crashes reported by this law-enforcement agency.

City

Crashes in NITRO, 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.