TruckCodex
Hubs

Crash Record WV202314660A

FMCSA crash record in NITRO on Jun 29, 2023.

Injury Federal Recordable

What happened

On June 29, 2023, FMCSA recorded an injury crash with one person hurt in NITRO, West Virginia. The vehicle was operated by TRI-CITY EXTRUSION INC (USDOT 399245). Recorded conditions: 1 / 1 / 1 pavement. Reported by TRI-CITY EXTRUSION INC, FMCSA reference WV202314660A.

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
1
Vehicles
2
Carrier
TRI-CITY EXTRUSION INC
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
1
1 injury · 0 tow-away
Crashes per 100 power units (24 mo)
0.0
0 crashes · 9 units
Days since prior carrier crash
1,292
Last on Dec 15, 2019
Vs fleet-size peers
above the median
Cohort median 0.0 · 312,651 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 #:
WV202314660A
Date:
Jun 29, 2023
Time:
0830
State:
West Virginia
City:
NITRO
Fatalities:
0
Injuries:
1
Tow-Away:
No
HazMat:
No
Vehicles:
2
Carrier (USDOT):
TRI-CITY EXTRUSION INC (399245)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 3AKJGLDR8HSJF7448 2562842 (IN) TRI-CITY EXTRUSION INC 3 No

Crash event

Event sequence description.

1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT

Other crashes by this carrier

9 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_3902601 Dec 15, 2019 NC Tow-Away 0 0
cr_3671177 Sep 17, 2018 FL Injury 0 1
cr_3423887 Jul 7, 2017 TN Tow-Away 0 0
cr_3375313 Mar 26, 2017 TN Injury 0 2
cr_3204392 Apr 28, 2016 TN Tow-Away 0 0
cr_2730267 Aug 2, 2013 TN Injury 0 3
cr_749429 May 21, 2001 KY Tow-Away 0 0
cr_654119 Mar 13, 1996 KY Tow-Away 0 0
cr_815139 Oct 25, 1995 NC Tow-Away 0 0

Related records

Vehicle
2017 FREIGHTLINER Cascadia
NHTSA recalls and complaints for this make/model/year.
Recall
23V073000
ELECTRONIC STABILITY CONTROL (ESC)
Recall
22V817000
FORWARD COLLISION AVOIDANCE: ADAPTIVE CRUISE CONTROL
Recall
20V567000
EXTERIOR LIGHTING:BRAKE LIGHTS
Carrier
TRI-CITY EXTRUSION INC
USDOT 399245 · 10 crashes · 10 inspections
Vehicle
VIN: 3AKJGLDR8HSJF7448
Decode this VIN for make, model, year, and recall data.
State
Crashes in West Virginia
Statewide crash records.
Agency
TRI-CITY EXTRUSION INC
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.