Crash Record MI0003522900

FMCSA crash record in SYLVAN TWP on Jun 16, 2025.

Injury Federal Recordable

What happened

On June 16, 2025, FMCSA recorded an injury crash with one person hurt in SYLVAN TWP, Michigan. The vehicle was operated by WARREN GIBSON LTD (USDOT 201808). Recorded conditions: 1 / 1 / 1 pavement. FMCSA reference MI0003522900.

Carrier pattern note

This is the carrier's 13 crashes in the past 24 months — above the typical pattern (median 0) for fleets of 51–500 power units.

Fatalities

Injuries

Vehicles

Carrier

WARREN GIBSON LTD

USDOT 201808

Vehicle Type

Truck

Severity

Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

5 injury · 12 tow-away

Crashes per 100 power units (24 mo)

4.6

10 crashes · 219 units

Days since prior carrier crash

Last on May 30, 2025

Vs fleet-size peers

above the median

Cohort median 0.0 · 27,189 carriers

Geographic context

How this crash sits in its setting.

Within SYLVAN TWP, Michigan, 8 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

ERIC M OSMAN · 1 reports
GAR'S PLUMBING LLC · 1 reports
JES GLOBAL TRUCKING LLC · 1 reports

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 #:: MI0003522900
Date:: Jun 16, 2025
Time:: 1804
State:: Michigan
City:: SYLVAN TWP
Fatalities:: 0
Injuries:: 1
Tow-Away:: Yes
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: WARREN GIBSON LTD (201808)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
2	9	3	3AKJHLDR9TSWJ4102	PB27084 (ON)	WARREN GIBSON LTD	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	Injuries
cr_5078116	Dec 10, 2025	OH	Injury	2
cr_5061012	Oct 23, 2025	MI	Tow-Away	0
cr_5040346	Sep 26, 2025	MI	Tow-Away	0
cr_5039424	Sep 23, 2025	OH	Injury	1
cr_5038348	Sep 23, 2025	IL	Tow-Away	0
cr_5035166	Sep 23, 2025	OH	Injury	1
cr_4953692	May 30, 2025	OH	Injury	1
cr_4930246	Apr 6, 2025	OH	Tow-Away	0
cr_4860461	Dec 5, 2024	OH	Tow-Away	0
cr_4828820	Oct 7, 2024	OH	Injury	1

Carrier booking & risk tools

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

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

Related records

Vehicle

2026 FREIGHTLINER Cascadia

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

USDOT 201808 · 197 crashes · 361 inspections

Safety

Carrier inspections

Roadside inspection history for this USDOT.

Vehicle

VIN: 3AKJHLDR9TSWJ4102

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

State

Crashes in Michigan

Statewide crash records.

City

Crashes in SYLVAN TWP, MI

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.