Skip to main content
TruckCodex
Hubs

Crash Record MN0241940173

FMCSA crash record in MONTICELLO on Jul 12, 2024.

Tow-Away Federal Recordable

What happened

On July 12, 2024, FMCSA recorded a tow-away crash with no reported injuries in MONTICELLO, Minnesota. The vehicle was operated by KNIFE RIVER CORPORATION-NORTH CENTRAL (USDOT 607349). Recorded conditions: 1 / 1 / 1 pavement. Reported by KNIFE RIVER CORPORATION-NORTH CENTRAL, FMCSA reference MN0241940173.

Carrier pattern note

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

Geographic note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
KNIFE RIVER CORPORATION-NORTH CENTRAL
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
8
3 injury · 8 tow-away
Crashes per 100 power units (24 mo)
0.8
5 crashes · 615 units
Days since prior carrier crash
38
Last on Jun 4, 2024
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,850 carriers

Geographic context

How this crash sits in its setting.

Within MONTICELLO, Minnesota, 67 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 #:
MN0241940173
Date:
Jul 12, 2024
Time:
1635
State:
Minnesota
City:
MONTICELLO
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
KNIFE RIVER CORPORATION-NORTH CENTRAL (607349)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 6 7 1HTXLAHT35J128120 YBR4181 (MN) KNIFE RIVER CORPORATION-NORTH CENTRAL 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
cmpaoq9bz000tnu1hcph8748p May 14, 2026 MN Tow-Away 0 0
cr_5123034 Mar 23, 2026 MN Injury 0 1
cr_5001623 Aug 7, 2025 MN Tow-Away 0 0
cr_4912377 Mar 22, 2025 MN Tow-Away 0 0
cr_4863006 Oct 31, 2024 MN Tow-Away 0 0
cr_4813857 Sep 25, 2024 MN Injury 0 1
cr_4763163 Jun 4, 2024 MN Injury 0 1
cr_4718505 Jan 29, 2024 ND Injury 0 1
cr_4646962 Nov 1, 2023 MN Tow-Away 0 0
cr_4577568 Jun 16, 2023 MN Injury 0 1

Related records

Carrier
KNIFE RIVER CORPORATION-NORTH CENTRAL
USDOT 607349 · 140 crashes · 116 inspections
Vehicle
VIN: 1HTXLAHT35J128120
Decode this VIN for make, model, year, and recall data.
State
Crashes in Minnesota
Statewide crash records.
Agency
KNIFE RIVER CORPORATION-NORTH CENTRAL
Crashes reported by this law-enforcement agency.
City
Crashes in MONTICELLO, 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.