TruckCodex
Hubs

Crash Record WV202313431A

FMCSA crash record in NITRO on Jun 20, 2023.

Tow-Away Federal Recordable

What happened

On June 20, 2023, FMCSA recorded a tow-away crash with no reported injuries in NITRO, West Virginia. The vehicle was operated by NEW BERN TRANSPORT CORPORATION (USDOT 692947). Recorded conditions: 1 / 1 / 1 pavement. Reported by NEW BERN TRANSPORT CORPORATION, FMCSA reference WV202313431A.

Carrier pattern note

This is the carrier's 417 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
0
Injuries
0
Vehicles
2
Carrier
NEW BERN TRANSPORT CORPORATION
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
417
6 fatal · 129 injury
Crashes per 100 power units (24 mo)
2.3
227 crashes · 9,786 units
Days since prior carrier crash
1
Last on Jun 19, 2023
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:

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 #:
WV202313431A
Date:
Jun 20, 2023
Time:
1650
State:
West Virginia
City:
NITRO
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
NEW BERN TRANSPORT CORPORATION (692947)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 1FUBCYCY4FHGS0064 B239357 (WV) NEW BERN TRANSPORT CORPORATION 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
cmsmuqyhr002ppexommay67rf Aug 5, 2026 PA Tow-Away 0 0
cmsipo3qm0003pef3pyevgg77 Aug 3, 2026 WV Tow-Away 0 0
cmrfwlwhp000pmlhrei7gbwzl Jul 6, 2026 KY Tow-Away 0 0
cmqkg7828009pp8fy5plcxw1w Jun 11, 2026 AR Tow-Away 0 0
cmq1vuzz4000fpbjq4urksg4h Jun 1, 2026 TN Injury 0 1
cr_5126517 Mar 19, 2026 LA Tow-Away 0 0
cr_5120076 Mar 5, 2026 AR Tow-Away 0 0
cr_5116321 Feb 27, 2026 TX Injury 0 2
cr_5117071 Feb 26, 2026 TX Tow-Away 0 0
cr_5109614 Feb 20, 2026 TN Injury 0 1

Related records

Vehicle
2015 FREIGHTLINER M2
NHTSA recalls and complaints for this make/model/year.
Recall
19V370000
SERVICE BRAKES, AIR:SUPPLY:RESERVOIR/TANK
Recall
19V146000
FUEL SYSTEM, OTHER
Recall
18V094000
EQUIPMENT
Carrier
NEW BERN TRANSPORT CORPORATION
USDOT 692947 · 4,157 crashes · 6,404 inspections
Vehicle
VIN: 1FUBCYCY4FHGS0064
Decode this VIN for make, model, year, and recall data.
State
Crashes in West Virginia
Statewide crash records.
Agency
NEW BERN TRANSPORT CORPORATION
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.