Crash Record OK0022009750

FMCSA crash record in WELLSTON on May 18, 2022.

Tow-Away Federal Recordable

What happened

On May 18, 2022, FMCSA recorded a tow-away crash with no reported injuries in WELLSTON, Oklahoma. The vehicle was operated by CORE & MAIN LP (USDOT 3024102). Recorded conditions: 1 / 1 / 1 pavement. Reported by GEMFAB NEILLSUPPLY ALBANYPIPE LONGISLANDPIPESUPPLY GEMLOCK BRECCO LMSUPPLY USEROSION PROTECH CES CATALONE DEPI LCS EEC, FMCSA reference OK0022009750.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

CORE & MAIN LP

Vehicle Type

Truck

Severity

Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

4 injury · 16 tow-away

Crashes per 100 power units (24 mo)

1.3

24 crashes · 1,892 units

Days since prior carrier crash

Last on Apr 18, 2022

Vs fleet-size peers

above the median

Cohort median 0.0 · 3,864 carriers

Geographic context

How this crash sits in its setting.

Within WELLSTON, Oklahoma, 37 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 #:: OK0022009750
Date:: May 18, 2022
Time:: 0904
State:: Oklahoma
City:: WELLSTON
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: CORE & MAIN LP (3024102)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	9	5	3AKJGEBG3GSHC1327	2386386 (IN)	GEMFAB NEILLSUPPLY ALBANYPIPE LONGISLANDPIPESUPPLY GEMLOCK BRECCO LMSUPPLY USEROSION PROTECH CES CATALONE DEPI LCS EEC	3	No

Crash event

Event sequence description.

1:11:NONCOLLISION:UNKNOWN

Other crashes by this carrier

10 additional crash record(s) on file.

Record	Date	State	Severity	Fatalities	Injuries
cr_5124472	Mar 16, 2026	OK	Injury	0	1
cr_5104015	Feb 2, 2026	MA	Injury	0	1
cr_5105741	Jan 15, 2026	OR	Fatal	1	0
cr_5102977	Jan 7, 2026	MD	Tow-Away	0	0
cr_5057406	Nov 4, 2025	NC	Tow-Away	0	0
cr_5051413	Oct 23, 2025	SC	Tow-Away	0	0
cr_5021797	Aug 25, 2025	OH	Tow-Away	0	0
cr_5026363	Aug 21, 2025	MI	Tow-Away	0	0
cr_5002931	Aug 19, 2025	NC	Tow-Away	0	0
cr_5024473	Aug 5, 2025	CA	Tow-Away	0	0

Related records

Carrier

CORE & MAIN LP

USDOT 3024102 · 84 crashes · 1,631 inspections

Safety

Carrier inspections

Roadside inspection history for this USDOT.

Vehicle

VIN: 3AKJGEBG3GSHC1327

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

State

Crashes in Oklahoma

Statewide crash records.

Agency

GEMFAB NEILLSUPPLY ALBANYPIPE LONGISLANDPIPESUPPLY GEMLOCK BRECCO LMSUPPLY USEROSION PROTECH CES CATALONE DEPI LCS EEC

Crashes reported by this law-enforcement agency.

City

Crashes in WELLSTON, OK

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.