Skip to main content
TruckCodex
Hubs

Crash Record MN0210340095

FMCSA crash record in DULUTH on Feb 3, 2021.

Tow-Away Federal Recordable

What happened

On February 3, 2021, FMCSA recorded a tow-away crash with no reported injuries in DULUTH, Minnesota. The vehicle was operated by KIVI BROS TRUCKING INC (USDOT 593718). Recorded conditions: 1 / 1 / 1 pavement. Reported by KIVI BROS TRUCKING INC, FMCSA reference MN0210340095.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
3
Carrier
KIVI BROS TRUCKING INC
USDOT 593718
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
26
1 fatal · 14 injury
Crashes per 100 power units (24 mo)
4.7
13 crashes · 278 units
Days since prior carrier crash
42
Last on Dec 23, 2020
Vs fleet-size peers
above the median
Cohort median 0.0 · 27,059 carriers

Geographic context

How this crash sits in its setting.

Within DULUTH, Minnesota, 42 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 #:
MN0210340095
Date:
Feb 3, 2021
Time:
1424
State:
Minnesota
City:
DULUTH
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
3
Carrier (USDOT):
KIVI BROS TRUCKING INC (593718)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 7 5 1XPCDP9X7JD460064 PAR3921 (MN) KIVI BROS TRUCKING 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
cmuz83jqo004hogz6i0up2wxa Oct 1, 2026 MN Injury 0 1
cmt5ony080025pmdmuusazv3k Aug 18, 2026 KY Injury 0 1
cr_5105117 Jan 19, 2026 TX Tow-Away 0 0
cr_5017353 Aug 19, 2025 WI Tow-Away 0 0
cr_5013770 Aug 4, 2025 VA Injury 0 1
cr_4995159 Jun 25, 2025 IL Tow-Away 0 0
cr_4931098 Apr 11, 2025 AL Tow-Away 0 0
cr_4878186 Jan 18, 2025 WI Injury 0 1
cr_4862452 Dec 16, 2024 TN Tow-Away 0 0
cr_4882207 Dec 14, 2024 MD Tow-Away 0 0

Carrier booking & risk tools

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

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

Related records

Carrier
KIVI BROS TRUCKING INC
USDOT 593718 · 125 crashes · 959 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 1XPCDP9X7JD460064
Decode this VIN for make, model, year, and recall data.
State
Crashes in Minnesota
Statewide crash records.
Agency
KIVI BROS TRUCKING INC
Crashes reported by this law-enforcement agency.
City
Crashes in DULUTH, MN
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.