Skip to main content
TruckCodex
Hubs

Crash Record MN0241600032

FMCSA crash record in MINNEAPOLIS on Jun 8, 2024.

Tow-Away Federal Recordable

What happened

On June 8, 2024, FMCSA recorded a tow-away crash with no reported injuries in MINNEAPOLIS, Minnesota. The vehicle was operated by CENTRAL STATES TRUCKING LLC (USDOT 185732). Recorded conditions: 1 / 2 / 2 pavement. Reported by CENTRAL STATES TRUCKING CO, FMCSA reference MN0241600032.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
1
Carrier
CENTRAL STATES TRUCKING LLC
USDOT 185732
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
52
3 fatal · 16 injury
Crashes per 100 power units (24 mo)
3.8
34 crashes · 900 units
Days since prior carrier crash
10
Last on May 29, 2024
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,867 carriers

Geographic context

How this crash sits in its setting.

Within MINNEAPOLIS, Minnesota, 244 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
2
Road surface
2

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 #:
MN0241600032
Date:
Jun 8, 2024
Time:
0726
State:
Minnesota
City:
MINNEAPOLIS
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
1
Carrier (USDOT):
CENTRAL STATES TRUCKING LLC (185732)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 1FUJA6CK67LX09678 PWZ9716 (OH) CENTRAL STATES TRUCKING CO 3 No

Crash event

Event sequence description.

1:17:COLLISION INVOLVING ANIMAL

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cmvettq5000lzogssyuesfedc Oct 8, 2026 VA Injury 0 1
cr_5125823 Mar 27, 2026 MN Tow-Away 0 0
cr_5123213 Mar 16, 2026 AL Tow-Away 0 0
cr_5092759 Jan 2, 2026 MS Tow-Away 0 0
cr_5078751 Dec 19, 2025 TN Tow-Away 0 0
cr_5081384 Dec 1, 2025 MO Injury 0 1
cr_5071334 Oct 30, 2025 SC Tow-Away 0 0
cr_5055059 Oct 21, 2025 GA Injury 0 1
cr_5042113 Oct 6, 2025 TX Injury 0 1
cr_5042189 Sep 30, 2025 PA Injury 0 2

Carrier booking & risk tools

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

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

Related records

Carrier
CENTRAL STATES TRUCKING LLC
USDOT 185732 · 474 crashes · 1,546 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Insurance
Insurance-lapse watch · HIGH
BMC-91 filing instability signal for this carrier.
HIGH
Vehicle
VIN: 1FUJA6CK67LX09678
Decode this VIN for make, model, year, and recall data.
State
Crashes in Minnesota
Statewide crash records.
Agency
CENTRAL STATES TRUCKING CO
Crashes reported by this law-enforcement agency.
City
Crashes in MINNEAPOLIS, MN
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.