TruckCodex
Hubs

Crash Record MO0000101459

FMCSA crash record in NON-CITY OR UNINCORPORATE on Feb 8, 2023.

Fatal Federal Recordable

What happened

On February 8, 2023, FMCSA recorded a fatal crash that resulted in one death in NON-CITY OR UNINCORPORATE, Missouri. The vehicle was operated by WAL-MART TRANSPORTATION LLC (USDOT 63585). Recorded conditions: 2 / 1 / 1 pavement. FMCSA reference MO0000101459.

Carrier pattern note

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

Fatalities
1
Injuries
1
Vehicles
2
Carrier
WAL-MART TRANSPORTATION LLC
Vehicle Type
Truck
Severity
Fatal

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
643
22 fatal · 214 injury
Crashes per 100 power units (24 mo)
4.8
654 crashes · 13,618 units
Days since prior carrier crash
1
Last on Feb 7, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,838 carriers

Geographic context

How this crash sits in its setting.

Within NON-CITY OR UNINCORPORATE, Missouri, 3,920 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 #:
MO0000101459
Date:
Feb 8, 2023
Time:
0613
State:
Missouri
City:
NON-CITY OR UNINCORPORATE
Fatalities:
1
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
WAL-MART TRANSPORTATION LLC (63585)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
2 9 3 3AKJGLDR4JSJM2603 3GZ115 (OK) WAL-MART TRANSPORTATION LLC 3 No

Crash event

Event sequence description.

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

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cmtazy7k7001zpmlnfdy6wbve Aug 20, 2026 WY Tow-Away 0 0
cmt5ony0b0029pmdmsmon347d Aug 18, 2026 NC Tow-Away 0 0
cmsw88sf000g1pev3wpohhu6a Aug 7, 2026 NV Injury 0 1
cms76vguw006xpehvig4qhkpd Jul 22, 2026 VA Tow-Away 0 0
cmqvwanp7000hp8iu11a8oiey Jun 23, 2026 TN Tow-Away 0 0
cmq1vv02h002rpbjqs3iuxscv May 31, 2026 NV Tow-Away 0 0
cmq0fazbl0015pmw8uiwlkv6l May 29, 2026 VA Injury 0 1
cmphifney005lpjl9mahhhzfu May 17, 2026 AL Tow-Away 0 0
cmoz9e2dw001tnufyuvgq9vwj May 6, 2026 VA Tow-Away 0 0
cmoweinyh001fnud5zmtc4btz May 4, 2026 NC Tow-Away 0 0

Related records

Carrier
WAL-MART TRANSPORTATION LLC
USDOT 63585 · 6,681 crashes · 28,198 inspections
Vehicle
VIN: 3AKJGLDR4JSJM2603
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.