Skip to main content
TruckCodex
Hubs

Crash Record MN0260690081

FMCSA crash record in BLAINE on Mar 10, 2026.

Tow-Away Federal Recordable

What happened

On March 10, 2026, FMCSA recorded a tow-away crash with no reported injuries in BLAINE, Minnesota. The vehicle was operated by ROEHL TRANSPORT INC (USDOT 74481). Recorded conditions: 1 / 1 / 1 pavement. Reported by ROEHL TRANSPORT INC, FMCSA reference MN0260690081.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
ROEHL TRANSPORT INC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
144
2 fatal · 31 injury
Crashes per 100 power units (24 mo)
5.2
111 crashes · 2,128 units
Days since prior carrier crash
5
Last on Mar 5, 2026
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,850 carriers

Geographic context

How this crash sits in its setting.

Within BLAINE, Minnesota, 33 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 #:
MN0260690081
Date:
Mar 10, 2026
Time:
1642
State:
Minnesota
City:
BLAINE
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
ROEHL TRANSPORT INC (74481)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 3AKJHHDR8PSNT6897 3628007 (IN) ROEHL TRANSPORT 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
cmu507ce9004rpmtophg4teks Sep 9, 2026 PA Tow-Away 0 0
cmt5ony1a0049pmdmwwf9py7u Aug 17, 2026 MN Injury 0 1
cmsw88sbl00bnpev3e51z1dv5 Aug 8, 2026 PA Injury 0 4
cmrx2ea5k002rpequzzxcydoe Jul 15, 2026 WV Injury 0 1
cmr318ztr005pp8aywbqv2xkm Jun 25, 2026 NC Injury 0 1
cmq0fazf6006hpmw891l3tixh May 27, 2026 OH Injury 0 1
cmpj9ikyt0001o5mmdjv8zuhi May 20, 2026 TN Injury 0 1
cmogoa8g8003hnvt8fn9w79oj Apr 21, 2026 MN Injury 0 1
cr_5116064 Mar 5, 2026 OH Tow-Away 0 0
cr_5124604 Feb 25, 2026 IN Tow-Away 0 0

Related records

Carrier
ROEHL TRANSPORT INC
USDOT 74481 · 2,426 crashes · 3,735 inspections
Vehicle
VIN: 3AKJHHDR8PSNT6897
Decode this VIN for make, model, year, and recall data.
State
Crashes in Minnesota
Statewide crash records.
Agency
ROEHL TRANSPORT INC
Crashes reported by this law-enforcement agency.
City
Crashes in BLAINE, 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.