Skip to main content
TruckCodex
Hubs

Crash Record TN0400073724

FMCSA crash record in NASHVILLE on Apr 7, 2024.

Tow-Away Federal Recordable

What happened

On April 7, 2024, FMCSA recorded a tow-away crash with no reported injuries in NASHVILLE, Tennessee. The vehicle was operated by WAL-MART TRANSPORTATION LLC (USDOT 63585). Recorded conditions: 1 / 1 / 1 pavement. Reported by WAL-MART TRANSPORTATION LLC, FMCSA reference TN0400073724.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
WAL-MART TRANSPORTATION LLC
USDOT 63585
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
740
21 fatal · 263 injury
Crashes per 100 power units (24 mo)
4.6
622 crashes · 13,618 units
Days since prior carrier crash
3
Last on Apr 4, 2024
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,864 carriers

Geographic context

How this crash sits in its setting.

Within NASHVILLE, Tennessee, 860 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 #:
TN0400073724
Date:
Apr 7, 2024
Time:
0631
State:
Tennessee
City:
NASHVILLE
Fatalities:
0
Injuries:
0
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
1 6 98 3AKJHHDR7RSUT3621 3HA700 (OK) WAL-MART TRANSPORTATION LLC 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
cmup2ni5l008dl4z8039jpdcg Sep 21, 2026 NC Tow-Away 0 0
cmtwgme24003tpmiytwyg2014 Sep 4, 2026 MI Tow-Away 0 0
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

Carrier booking & risk tools

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

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

Related records

Carrier
WAL-MART TRANSPORTATION LLC
USDOT 63585 · 6,683 crashes · 28,860 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 3AKJHHDR7RSUT3621
Decode this VIN for make, model, year, and recall data.
State
Crashes in Tennessee
Statewide crash records.
Agency
WAL-MART TRANSPORTATION LLC
Crashes reported by this law-enforcement agency.
City
Crashes in NASHVILLE, TN
All crashes on file for this city.
Station
I-24
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.