Crash Record MN0220420182

FMCSA crash record in OSCAR on Feb 11, 2022.

Tow-Away Federal Recordable

What happened

On February 11, 2022, FMCSA recorded a tow-away crash with no reported injuries in OSCAR, Minnesota. The vehicle was operated by VALLEY EXPRESS INC (USDOT 189247). Recorded conditions: 5 / 6 / 6 pavement. Reported by VALLEY EXPRESS INC, FMCSA reference MN0220420182.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

VALLEY EXPRESS INC

Vehicle Type

Truck

Severity

Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

3 injury · 12 tow-away

Crashes per 100 power units (24 mo)

5.5

19 crashes · 345 units

Days since prior carrier crash

Last on Dec 19, 2021

Vs fleet-size peers

above the median

Cohort median 0.0 · 27,020 carriers

Geographic context

How this crash sits in its setting.

Within OSCAR, Minnesota, 5 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: 5
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 #:: MN0220420182
Date:: Feb 11, 2022
Time:: 0736
State:: Minnesota
City:: OSCAR
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 5
Carrier (USDOT):: VALLEY EXPRESS INC (189247)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	9	3	3AKJGLD51ESBC1290	37914P (ND)	VALLEY EXPRESS INC	3	No

Crash event

Event sequence description.

1:6:NONCOLLISION:EXPLOSION OR FIRE;2:20:COLLISION INVOLVING OTHER MOVABLE OBJECT

Other crashes by this carrier

10 additional crash record(s) on file.

Record	Date	State	Severity	Injuries
cmqbvah7l0001qumaq169oa1o	Jun 9, 2026	MN	Tow-Away	0
cr_5116784	Feb 4, 2026	ND	Injury	2
cr_5126644	Jan 21, 2026	SD	Tow-Away	0
cr_5069512	Nov 15, 2025	MO	Tow-Away	0
cr_5032824	Sep 16, 2025	TX	Tow-Away	0
cr_5021346	Aug 29, 2025	IA	Tow-Away	0
cr_5002420	Jul 29, 2025	NC	Tow-Away	0
cr_5034367	Jul 14, 2025	ND	Injury	2
cr_4956492	Jun 12, 2025	MN	Injury	1
cr_4953987	Jun 9, 2025	MN	Tow-Away	0

Related records

Vehicle

2014 FREIGHTLINER Cascadia

NHTSA recalls and complaints for this make/model/year.

SERVICE BRAKES, AIR:SUPPLY:RESERVOIR/TANK

Recall

19V093000

STEERING:LINKAGES:TIE ROD ASSEMBLY

Carrier

VALLEY EXPRESS INC

USDOT 189247 · 208 crashes · 912 inspections

Safety

Carrier inspections

Roadside inspection history for this USDOT.

Vehicle

VIN: 3AKJGLD51ESBC1290

Decode this VIN for make, model, year, and recall data.

State

Crashes in Minnesota

Statewide crash records.

Agency

VALLEY EXPRESS INC

Crashes reported by this law-enforcement agency.

City

Crashes in OSCAR, 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.