Crash Record MI0002617639

FMCSA crash record in DELHI TWP on Jul 1, 2022.

Injury Federal Recordable

What happened

On July 1, 2022, FMCSA recorded an injury crash with one person hurt in DELHI TWP, Michigan. The vehicle was operated by VV LOGISTICS SOLUTIONS INC (USDOT 2416643). Recorded conditions: 1 / 1 / 1 pavement. Reported by VV LOGISTICS SOLUTIONS INC, FMCSA reference MI0002617639.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

VV LOGISTICS SOLUTIONS INC

Vehicle Type

Truck

Severity

Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

8 injury · 16 tow-away

Crashes per 100 power units (24 mo)

13.6

15 crashes · 110 units

Days since prior carrier crash

Last on May 6, 2022

Vs fleet-size peers

above the median

Cohort median 0.0 · 26,885 carriers

Geographic context

How this crash sits in its setting.

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

Agencies most active in this area:

J BETS TRUCKING · 1 reports
JOHAL BROTHERS INC · 1 reports
RAKMARK INC · 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 #:: MI0002617639
Date:: Jul 1, 2022
Time:: 1813
State:: Michigan
City:: DELHI TWP
Fatalities:: 0
Injuries:: 1
Tow-Away:: Yes
HazMat:: No
Vehicles:: 1
Carrier (USDOT):: VV LOGISTICS SOLUTIONS INC (2416643)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	9	3	1FUJGLD59GLGY5997	2776662 (IL)	VV LOGISTICS SOLUTIONS INC	3	No

Crash event

Event sequence description.

3:17:COLLISION INVOLVING ANIMAL;1:6:NONCOLLISION:EXPLOSION OR FIRE;2:18:COLLISION INVOLVING FIXED OBJECT

Other crashes by this carrier

10 additional crash record(s) on file.

Record	Date	State	Severity	Injuries
cr_5081350	Dec 26, 2025	MI	Injury	2
cr_5121858	Dec 3, 2025	PA	Injury	1
cr_5038377	Sep 24, 2025	IL	Injury	1
cr_5022070	Aug 15, 2025	MO	Injury	2
cr_5019004	Aug 7, 2025	NY	Injury	1
cr_4996642	Jul 31, 2025	IL	Injury	1
cr_4995620	Jul 11, 2025	IL	Injury	1
cr_5007282	Jul 9, 2025	PA	Tow-Away	0
cr_4988179	Jul 4, 2025	AL	Injury	2
cr_4921658	Mar 29, 2025	TX	Tow-Away	0

Related records

Vehicle

2016 FREIGHTLINER Cascadia

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

SERVICE BRAKES, AIR:SUPPLY:RESERVOIR/TANK

Recall

19V093000

STEERING:LINKAGES:TIE ROD ASSEMBLY

Carrier

VV LOGISTICS SOLUTIONS INC

USDOT 2416643 · 73 crashes · 705 inspections

Vehicle

VIN: 1FUJGLD59GLGY5997

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

State

Crashes in Michigan

Statewide crash records.

Agency

VV LOGISTICS SOLUTIONS INC

Crashes reported by this law-enforcement agency.

City

Crashes in DELHI 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.