Skip to main content
TruckCodex
Hubs

Crash Record OH0245029260

FMCSA crash record in SANDUSKY (TOWNSHIP OF) on Feb 19, 2024.

Injury Federal Recordable

What happened

On February 19, 2024, FMCSA recorded an injury crash with one person hurt in SANDUSKY (TOWNSHIP OF), Ohio. The vehicle was operated by WAL-MART TRANSPORTATION LLC (USDOT 63585). Recorded conditions: 1 / 1 / 1 pavement. FMCSA reference OH0245029260.

Carrier pattern note

This is the carrier's 701 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
WAL-MART TRANSPORTATION LLC
USDOT 63585
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
701
22 fatal · 244 injury
Crashes per 100 power units (24 mo)
4.4
603 crashes · 13,618 units
Days since prior carrier crash
2
Last on Feb 17, 2024
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,881 carriers

Geographic context

How this crash sits in its setting.

Within SANDUSKY (TOWNSHIP OF), Ohio, 20 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 #:
OH0245029260
Date:
Feb 19, 2024
Time:
1609
State:
Ohio
City:
SANDUSKY (TOWNSHIP OF)
Fatalities:
0
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 3AKJHHDR4RSUT4340 3JH016 (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
cmvotteso0045o3rbzeludjgf Oct 21, 2026 AZ Injury 0 1
cmvettpy800a3ogssow5kjmsk Oct 12, 2026 KY Tow-Away 0 0
cmvettr47011fogss9y01xwbg Oct 7, 2026 AR Tow-Away 0 0
cmvettr0700utogsskbqdbyd3 Oct 7, 2026 NC Tow-Away 0 0
cmv0pusxp000jogxwrzkmilzw Oct 5, 2026 VA Tow-Away 0 0
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

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,688 crashes · 29,319 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 3AKJHHDR4RSUT4340
Decode this VIN for make, model, year, and recall data.
State
Crashes in Ohio
Statewide crash records.
City
Crashes in SANDUSKY (TOWNSHIP OF), OH
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.