Skip to main content
TruckCodex
Hubs

Crash Record MN0253300274

FMCSA crash record in MIDWAY on Nov 26, 2025.

Injury Federal Recordable

What happened

On November 26, 2025, FMCSA recorded an injury crash with one person hurt in MIDWAY, Minnesota. The vehicle was operated by LOHSE TRANSFER INC (USDOT 294301). Recorded conditions: 1 / 6 / 6 pavement. Reported by LOHSE TRANSFER INC, FMCSA reference MN0253300274.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
1
Carrier
USDOT 294301
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
4
2 injury · 4 tow-away
Crashes per 100 power units (24 mo)
8.2
5 crashes · 61 units
Days since prior carrier crash
176
Last on Jun 3, 2025
Vs fleet-size peers
above the median
Cohort median 0.0 · 27,189 carriers

Geographic context

How this crash sits in its setting.

Within MIDWAY, Minnesota, 7 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
6
Road surface
6

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 #:
MN0253300274
Date:
Nov 26, 2025
Time:
1332
State:
Minnesota
City:
MIDWAY
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
1
Carrier (USDOT):
LOHSE TRANSFER INC (294301)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 4V4NC9GH27N454510 YCD0651 (MN) LOHSE TRANSFER INC 3 No

Crash event

Event sequence description.

1:15:COLLISION INVOLVING TRAIN

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5092236 Jan 21, 2026 IA Tow-Away 0 0
cr_5076141 Dec 18, 2025 MN Injury 0 1
cr_4950728 Jun 3, 2025 MN Tow-Away 0 0
cr_4916514 Mar 27, 2025 MN Injury 0 1
cr_4706385 Feb 15, 2024 MN Tow-Away 0 0
cr_4554352 May 9, 2023 MN Tow-Away 0 0
cr_4343435 Apr 22, 2022 MN Tow-Away 0 0
cr_4304979 Jan 28, 2022 MN Tow-Away 0 0
cr_4287274 Dec 29, 2021 MN Tow-Away 0 0
cr_4274053 Dec 15, 2021 MN Fatal 1 4

Carrier booking & risk tools

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

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.