TruckCodex
Hubs

Crash Record OK2307000321

FMCSA crash record in ARDMORE on Jun 18, 2023.

Tow-Away Federal Recordable

What happened

On June 18, 2023, FMCSA recorded a tow-away crash with no reported injuries in ARDMORE, Oklahoma. The vehicle was operated by SAM AUTO TRANS LLC (USDOT 2520572). Recorded conditions: 2 / 2 / 3 pavement. Reported by SAM AUTO TRANS LLC, FMCSA reference OK2307000321.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
1
Carrier
SAM AUTO TRANS LLC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
10
1 fatal · 2 injury
Crashes per 100 power units (24 mo)
10.5
8 crashes · 76 units
Days since prior carrier crash
5
Last on Jun 13, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,773 carriers

Geographic context

How this crash sits in its setting.

Within ARDMORE, Oklahoma, 40 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
2
Road surface
3

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 #:
OK2307000321
Date:
Jun 18, 2023
Time:
2244
State:
Oklahoma
City:
ARDMORE
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
1
Carrier (USDOT):
SAM AUTO TRANS LLC (2520572)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 1XKYDP9X5HJ139048 AH32591 (PA) SAM AUTO TRANS LLC 3 No

Crash event

Event sequence description.

1:6:NONCOLLISION:EXPLOSION OR FIRE;2:17:COLLISION INVOLVING ANIMAL

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5104500 Feb 4, 2026 TN Injury 0 2
cr_5081945 Dec 20, 2025 MO Tow-Away 0 0
cr_5079700 Dec 12, 2025 CO Tow-Away 0 0
cr_5005207 Jul 16, 2025 OH Injury 0 4
cr_4944307 May 16, 2025 KY Tow-Away 0 0
cr_4896319 Feb 19, 2025 OK Tow-Away 0 0
cr_4894370 Feb 18, 2025 AR Tow-Away 0 0
cr_4887106 Jan 22, 2025 TX Injury 0 1
cr_4772920 Jul 1, 2024 MA Tow-Away 0 0
cr_4723165 Mar 1, 2024 OK Tow-Away 0 0

Related records

Vehicle
2017 KENWORTH T680
NHTSA recalls and complaints for this make/model/year.
Recall
24V145000
SERVICE BRAKES, AIR:SUPPLY:RESERVOIR/TANK
Recall
21V00N000
ELECTRICAL SYSTEM:WIRING
Recall
20V593000
SERVICE BRAKES, AIR:ANTILOCK
Carrier
SAM AUTO TRANS LLC
USDOT 2520572 · 25 crashes · 303 inspections
Vehicle
VIN: 1XKYDP9X5HJ139048
Decode this VIN for make, model, year, and recall data.
State
Crashes in Oklahoma
Statewide crash records.
Agency
SAM AUTO TRANS LLC
Crashes reported by this law-enforcement agency.
City
Crashes in ARDMORE, 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.