Skip to main content
TruckCodex
Hubs

Crash Record MO0000100409

FMCSA crash record in NON-CITY OR UNINCORPORATE on Dec 13, 2022.

Injury Federal Recordable

What happened

On December 13, 2022, FMCSA recorded an injury crash with one person hurt in NON-CITY OR UNINCORPORATE, Missouri. The vehicle was operated by CARDS HOLDINGS INC (USDOT 3164317). Recorded conditions: 2 / 9 / 1 pavement. FMCSA reference MO0000100409.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
2
Carrier
CARDS HOLDINGS INC
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
21
5 injury · 21 tow-away
Crashes per 100 power units (24 mo)
3.6
16 crashes · 443 units
Days since prior carrier crash
25
Last on Nov 18, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 27,034 carriers

Geographic context

How this crash sits in its setting.

Within NON-CITY OR UNINCORPORATE, Missouri, 3,687 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
9
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 #:
MO0000100409
Date:
Dec 13, 2022
Time:
0615
State:
Missouri
City:
NON-CITY OR UNINCORPORATE
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
CARDS HOLDINGS INC (3164317)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
2 6 9 2NP2HJ7X7KM626086 C219672 (AR) CARDS 3 No

Crash event

Event sequence description.

1:98:OTHER;2:20:COLLISION INVOLVING OTHER MOVABLE OBJECT

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cms2qwgjv0023pey1f875158n Jul 22, 2026 AR Injury 0 1
cmqvwanss002dp8iukzo0fa4f Jun 22, 2026 OK Injury 0 1
cmny3yg2s00f4k38v8q89vhr0 Apr 6, 2026 AR Injury 0 3
cr_5078875 Dec 18, 2025 AR Tow-Away 0 0
cr_5041141 Oct 2, 2025 AR Tow-Away 0 0
cr_5038531 Sep 9, 2025 MO Tow-Away 0 0
cr_4988488 Jul 22, 2025 AR Tow-Away 0 0
cr_5021059 Jun 27, 2025 OK Tow-Away 0 0
cr_4988609 Jun 18, 2025 AR Tow-Away 0 0
cr_4904089 Feb 28, 2025 AR Injury 0 2

Carrier booking & risk tools

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

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

Related records

Vehicle
2019 PETERBILT 337
NHTSA recalls and complaints for this make/model/year.
Recall
22V277000
STEERING:CRITICAL FASTENERS
Recall
21V391000
FUEL SYSTEM, DIESEL:FUEL INJECTION SYSTEM:FUEL RAIL
Recall
20V199000
ELECTRONIC STABILITY CONTROL (ESC)
Carrier
CARDS HOLDINGS INC
USDOT 3164317 · 63 crashes · 337 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 2NP2HJ7X7KM626086
Decode this VIN for make, model, year, and recall data.
State
Crashes in Missouri
Statewide crash records.
City
Crashes in NON-CITY OR UNINCORPORATE, MO
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.