TruckCodex
Hubs

Crash Record WV202105567A

FMCSA crash record in MORGANTOWN on Mar 16, 2021.

Injury Federal Recordable

What happened

On March 16, 2021, FMCSA recorded an injury crash with one person hurt in MORGANTOWN, West Virginia. The vehicle was operated by COCA-COLA CONSOLIDATED INC (USDOT 16208). Recorded conditions: 3 / 1 / 1 pavement. Reported by COCA-COLA CONSOLIDATED INC, FMCSA reference WV202105567A.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
2
Carrier
COCA-COLA CONSOLIDATED INC
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
12
5 injury · 12 tow-away
Crashes per 100 power units (24 mo)
0.0
0 crashes · 52 units
Days since prior carrier crash
117
Last on Nov 19, 2020
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,632 carriers

Geographic context

How this crash sits in its setting.

Within MORGANTOWN, West Virginia, 73 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
3
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 #:
WV202105567A
Date:
Mar 16, 2021
Time:
0621
State:
West Virginia
City:
MORGANTOWN
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
COCA-COLA CONSOLIDATED INC (16208)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 5 3 1HTSCAAN5WH566054 LA7602 (NC) COCA-COLA CONSOLIDATED INC 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_4770159 Jun 17, 2024 IN Tow-Away 0 0
cr_4723862 Mar 27, 2024 AR Injury 0 1
cr_4721357 Mar 18, 2024 SC Injury 0 3
cr_4618709 Aug 12, 2023 OH Tow-Away 0 0
cr_4607085 Aug 7, 2023 SC Injury 0 7
cr_4571882 May 26, 2023 TX Tow-Away 0 0
cr_4527681 Mar 8, 2023 SC Tow-Away 0 0
cr_4385043 Jun 15, 2022 MD Tow-Away 0 0
cr_4370302 Jun 8, 2022 VA Injury 0 1
cr_4309036 Jan 26, 2022 NC Injury 0 3

Related records

Vehicle
1998 INTERNATIONAL 4700
NHTSA recalls and complaints for this make/model/year.
Recall
03V137000
SERVICE BRAKES, AIR
Recall
03V083000
SEATS
Recall
02V135002
SERVICE BRAKES, AIR:SUPPLY:CHECK VALVE
Carrier
COCA-COLA CONSOLIDATED INC
USDOT 16208 · 380 crashes · 0 inspections
Vehicle
VIN: 1HTSCAAN5WH566054
Decode this VIN for make, model, year, and recall data.
State
Crashes in West Virginia
Statewide crash records.
Agency
COCA-COLA CONSOLIDATED INC
Crashes reported by this law-enforcement agency.
City
Crashes in MORGANTOWN, 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.