TruckCodex
Hubs

Crash Record MI0002841470

FMCSA crash record in CASCADE TWP on Mar 18, 2023.

Tow-Away Federal Recordable

What happened

On March 18, 2023, FMCSA recorded a tow-away crash with no reported injuries in CASCADE TWP, Michigan. The vehicle was operated by JW HUNT OTC INC (USDOT 929376). Recorded conditions: 1 / 4 / 4 pavement. Reported by JW HUNT OTC INC, FMCSA reference MI0002841470.

Geographic note

This crash is part of an active corridor: 57 crashes occurred in the same city in the past 24 months.

Fatalities
0
Injuries
0
Vehicles
2
Carrier
JW HUNT OTC INC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
3
0 injury · 3 tow-away
Crashes per 100 power units (24 mo)
8.2
5 crashes · 61 units
Days since prior carrier crash
554
Last on Sep 10, 2021
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,858 carriers

Geographic context

How this crash sits in its setting.

Within CASCADE TWP, Michigan, 57 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
4
Road surface
4

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 #:
MI0002841470
Date:
Mar 18, 2023
Time:
1225
State:
Michigan
City:
CASCADE TWP
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
JW HUNT OTC INC (929376)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 4 2HSCNSCR25C001999 RB46727 (MI) JW HUNT OTC INC 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 Fatalities Injuries
cmroiq153002rpemcjtn6sxji Jul 10, 2026 MI Tow-Away 0 0
cr_5019484 Aug 10, 2025 IN Tow-Away 0 0
cr_4997234 Jul 9, 2025 IN Tow-Away 0 0
cr_4944434 May 16, 2025 MI Tow-Away 0 0
cr_4894709 Feb 6, 2025 OH Tow-Away 0 0
cr_4812129 Sep 8, 2024 MI Tow-Away 0 0
cr_4800190 Aug 13, 2024 OH Tow-Away 0 0
cr_4750430 May 3, 2024 OH Injury 0 2
cr_4748267 May 2, 2024 MI Tow-Away 0 0
cr_4542361 Mar 18, 2023 MI Tow-Away 0 0

Related records

Vehicle
2005 INTERNATIONAL 9400i
NHTSA recalls and complaints for this make/model/year.
Recall
23V353000
EXTERIOR LIGHTING:BACK UP LIGHTS
Recall
09V386000
ENGINE AND ENGINE COOLING
Recall
05V296000
ELECTRICAL SYSTEM:12V/24V/48V BATTERY:CABLES
Carrier
JW HUNT OTC INC
USDOT 929376 · 57 crashes · 17 inspections
Vehicle
VIN: 2HSCNSCR25C001999
Decode this VIN for make, model, year, and recall data.
State
Crashes in Michigan
Statewide crash records.
Agency
JW HUNT OTC INC
Crashes reported by this law-enforcement agency.
City
Crashes in CASCADE 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.