Skip to main content
TruckCodex
Hubs

Crash Record MN0094102829

FMCSA crash record in Minnesota on Jun 23, 1994.

Injury

What happened

On June 23, 1994, FMCSA recorded an injury crash with 2 people hurt in Minnesota. The vehicle was operated by TAMARACK MATERIALS INC (USDOT 403686). FMCSA reference MN0094102829.

Fatalities
0
Injuries
2
Vehicles
—
Carrier
TAMARACK MATERIALS INC
Vehicle Type
—
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
1
1 injury · 1 tow-away
Crashes per 100 power units (24 mo)
1.9
4 crashes · 209 units
Prior carrier crash
—
No earlier crash on file
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,879 carriers

Geographic context

How this crash sits in its setting.

Within Minnesota, 4,622 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

Crash details

Key facts from the FMCSA crash record.

Report #:
MN0094102829
Date:
Jun 23, 1994
Time:
0815
State:
Minnesota
Fatalities:
0
Injuries:
2
Tow-Away:
Yes
HazMat:
No

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5078236 Dec 18, 2025 MI Tow-Away 0 0
cr_5001594 Aug 20, 2025 MN Injury 0 1
cr_5000893 Jun 26, 2025 MI Tow-Away 0 0
cr_4917646 Mar 5, 2025 WI Tow-Away 0 0
cr_4814856 Jul 18, 2024 ND Tow-Away 0 0
cr_4675081 Dec 28, 2023 WI Tow-Away 0 0
cr_4475503 Dec 13, 2022 ND Injury 0 1
cr_4089645 Dec 22, 2020 MN Injury 0 1
cr_3999992 Jul 2, 2020 MN Tow-Away 0 0
cr_3893727 Dec 9, 2019 MN Tow-Away 0 0

Related records

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.