Skip to main content
TruckCodex
Hubs

Crash Record MI0002950330

FMCSA crash record in FARMINGTON HILLS on Jul 20, 2023.

Tow-Away Federal Recordable

What happened

On July 20, 2023, FMCSA recorded a tow-away crash with no reported injuries in FARMINGTON HILLS, Michigan. The vehicle was operated by MIDWEST FREIGHT SYSTEMS CORP (USDOT 2074894). Recorded conditions: 1 / 1 / 1 pavement. Reported by MIDWEST FREIGHT SYSTEMS CORP, FMCSA reference MI0002950330.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
1
Carrier
MIDWEST FREIGHT SYSTEMS CORP
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
31
1 fatal · 12 injury
Crashes per 100 power units (24 mo)
4.2
16 crashes · 382 units
Days since prior carrier crash
83
Last on Apr 28, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,885 carriers

Geographic context

How this crash sits in its setting.

Within FARMINGTON HILLS, Michigan, 71 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 #:
MI0002950330
Date:
Jul 20, 2023
Time:
0635
State:
Michigan
City:
FARMINGTON HILLS
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
1
Carrier (USDOT):
MIDWEST FREIGHT SYSTEMS CORP (2074894)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 4V4MC9EG1GN974848 RC14569 (MI) MIDWEST FREIGHT SYSTEMS CORP 3 No

Crash event

Event sequence description.

1:8:NONCOLLISION:CROSS MEDIAN/CENTERLINE;2:15:COLLISION INVOLVING TRAIN;3:6:NONCOLLISION:EXPLOSION OR FIRE

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5122072 Mar 11, 2026 MI Tow-Away 0 0
cr_5094939 Jan 11, 2026 MI Tow-Away 0 0
cr_5068789 Nov 25, 2025 MI Tow-Away 0 0
cr_5047844 Oct 23, 2025 MI Tow-Away 0 0
cr_5041992 Oct 7, 2025 MI Injury 0 1
cr_5037826 Sep 18, 2025 MI Tow-Away 0 0
cr_5026321 Sep 4, 2025 MI Injury 0 1
cr_5016366 Jun 27, 2025 WV Tow-Away 0 0
cr_5000582 Jun 21, 2025 MI Tow-Away 0 0
cr_4947883 May 21, 2025 MI Tow-Away 0 0

Related records

Vehicle
2016 VOLVO TRUCK VNM
NHTSA recalls and complaints for this make/model/year.
Carrier
MIDWEST FREIGHT SYSTEMS CORP
USDOT 2074894 · 207 crashes · 478 inspections
Vehicle
VIN: 4V4MC9EG1GN974848
Decode this VIN for make, model, year, and recall data.
State
Crashes in Michigan
Statewide crash records.
Agency
MIDWEST FREIGHT SYSTEMS CORP
Crashes reported by this law-enforcement agency.
City
Crashes in FARMINGTON HILLS, 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.