Crash Record MN0242180200

FMCSA crash record in ELK RIVER on Aug 5, 2024.

Tow-Away Federal Recordable

What happened

On August 5, 2024, FMCSA recorded a tow-away crash with no reported injuries in ELK RIVER, Minnesota. The vehicle was operated by GARDA CL GREAT LAKES INC (USDOT 163997). Recorded conditions: 1 / 2 / 2 pavement. Reported by GARDA CL GREAT LAKES INC, FMCSA reference MN0242180200.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

GARDA CL GREAT LAKES INC

USDOT 163997

Vehicle Type

Truck

Severity

Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

7 injury · 15 tow-away

Crashes per 100 power units (24 mo)

3.5

11 crashes · 310 units

Days since prior carrier crash

Last on May 2, 2024

Vs fleet-size peers

above the median

Cohort median 0.0 · 27,189 carriers

Geographic context

How this crash sits in its setting.

Within ELK RIVER, Minnesota, 28 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

VISION OF ELK RIVER INC · 3 reports
SYSCO MINNESOTA INC · 2 reports
SHAW TRUCKING INC · 2 reports

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 #:: MN0242180200
Date:: Aug 5, 2024
Time:: 1245
State:: Minnesota
City:: ELK RIVER
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 1
Carrier (USDOT):: GARDA CL GREAT LAKES INC (163997)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	5	3	1FTRS4XM5KKB13855	YBY0950 (MN)	GARDA CL GREAT LAKES INC	2	No

Crash event

Event sequence description.

1:18:COLLISION INVOLVING FIXED OBJECT

Other crashes by this carrier

10 additional crash record(s) on file.

Record	Date	State	Severity	Injuries
cr_5075288	Dec 4, 2025	IN	Tow-Away	0
cr_5077776	Dec 2, 2025	IN	Tow-Away	0
cr_5016696	Jul 24, 2025	MI	Tow-Away	0
cr_4997436	Jun 23, 2025	IN	Injury	1
cr_4944406	Apr 30, 2025	MI	Tow-Away	0
cr_4925475	Mar 20, 2025	WI	Tow-Away	0
cr_4897985	Feb 21, 2025	MN	Tow-Away	0
cr_4895492	Feb 1, 2025	MI	Injury	1
cr_4892205	Jan 13, 2025	WI	Tow-Away	0
cr_4879259	Dec 23, 2024	MI	Tow-Away	0

Carrier booking & risk tools

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

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

Related records

Vehicle

2019 FORD Transit

NHTSA recalls and complaints for this make/model/year.

Recall

25V876000

EQUIPMENT ADAPTIVE/MOBILITY

GARDA CL GREAT LAKES INC

USDOT 163997 · 177 crashes · 18 inspections

Safety

Carrier inspections

Roadside inspection history for this USDOT.

Vehicle

VIN: 1FTRS4XM5KKB13855

Decode this VIN for make, model, year, and recall data.

State

Crashes in Minnesota

Statewide crash records.

Agency

GARDA CL GREAT LAKES INC

Crashes reported by this law-enforcement agency.

City

Crashes in ELK RIVER, 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.