Skip to main content
TruckCodex
Hubs

Crash Record OK0021025821

FMCSA crash record in GOLDSBY on Nov 5, 2021.

Injury Federal Recordable

What happened

On November 5, 2021, FMCSA recorded an injury crash with one person hurt in GOLDSBY, Oklahoma. The vehicle was operated by CORE-MARK MIDCONTINENT INC (USDOT 1532737). Recorded conditions: 2 / 1 / 1 pavement. FMCSA reference OK0021025821.

Carrier pattern note

This is the carrier's 40 crashes in the past 24 months — above the typical pattern (median 0) for fleets of 500+ power units.

Fatalities
0
Injuries
1
Vehicles
2
Carrier
CORE-MARK MIDCONTINENT INC
USDOT 1532737
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
40
13 injury · 39 tow-away
Crashes per 100 power units (24 mo)
0.0
0 crashes · 619 units
Days since prior carrier crash
9
Last on Oct 27, 2021
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,881 carriers

Geographic context

How this crash sits in its setting.

Within GOLDSBY, Oklahoma, 17 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
2
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 #:
OK0021025821
Date:
Nov 5, 2021
Time:
0414
State:
Oklahoma
City:
GOLDSBY
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
CORE-MARK MIDCONTINENT INC (1532737)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
2 10 3 3AKJHLDV9LSLU3720 2829986 (IN) CORE-MARK MIDCONTINENT 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_4570982 Apr 12, 2023 NE Injury 0 2
cr_4521505 Feb 22, 2023 NY Tow-Away 0 0
cr_4476589 Nov 2, 2022 NJ Injury 0 1
cr_4451487 Nov 1, 2022 OH Tow-Away 0 0
cr_4455200 Oct 25, 2022 MN Tow-Away 0 0
cr_4422210 Sep 9, 2022 TX Injury 0 1
cr_4412402 Sep 2, 2022 KY Tow-Away 0 0
cr_4418062 Aug 30, 2022 IN Injury 0 1
cr_4414777 Aug 25, 2022 FL Tow-Away 0 0
cr_4431748 Aug 23, 2022 VT Tow-Away 0 0

Carrier booking & risk tools

Check booking and risk signals for USDOT 1532737 — tools open pre-filled.

Book / don't book Insurance check Cancel desk Chameleon check Safety benchmark

Related records

Vehicle
2020 FREIGHTLINER Cascadia
NHTSA recalls and complaints for this make/model/year.
Recall
26V583000
SERVICE BRAKES, AIR:ANTILOCK
Recall
23V299000
ELECTRONIC STABILITY CONTROL (ESC)
Recall
23V208000
EXTERIOR LIGHTING
Carrier
CORE-MARK MIDCONTINENT INC
USDOT 1532737 · 260 crashes · 0 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 3AKJHLDV9LSLU3720
Decode this VIN for make, model, year, and recall data.
State
Crashes in Oklahoma
Statewide crash records.
City
Crashes in GOLDSBY, OK
All crashes on file for this city.
Station
I-35
Weigh / inspection station matching this crash location.
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.