Crash Record MO0000101750

FMCSA crash record in KANSAS CITY on Mar 10, 2023.

Injury Federal Recordable

What happened

On March 10, 2023, FMCSA recorded an injury crash with 2 people hurt in KANSAS CITY, Missouri. The vehicle was operated by HY-VEE INC (USDOT 117784). Recorded conditions: 2 / 1 / 1 pavement. Reported by HY-VEE INC, FMCSA reference MO0000101750.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

HY-VEE INC

Vehicle Type

Truck

Severity

Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

1 fatal · 7 injury

Crashes per 100 power units (24 mo)

3.5

13 crashes · 367 units

Days since prior carrier crash

Last on Mar 5, 2023

Vs fleet-size peers

above the median

Cohort median 0.0 · 26,863 carriers

Geographic context

How this crash sits in its setting.

Within KANSAS CITY, Missouri, 719 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

FEDERAL EXPRESS CORPORATION · 6 reports
FIRST STUDENT INC · 5 reports
CITY OF KANSAS CITY · 4 reports

Contributing factors

What the responding officer recorded.

Light: 2
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 #:: MO0000101750
Date:: Mar 10, 2023
Time:: 1956
State:: Missouri
City:: KANSAS CITY
Fatalities:: 0
Injuries:: 2
Tow-Away:: Yes
HazMat:: No
Vehicles:: 4
Carrier (USDOT):: HY-VEE INC (117784)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	9	3	4V4NC9EH0MN271573	FH7566 (IA)	HY-VEE INC	3	No

Crash event

Event sequence description.

1:98:OTHER:OTHER;2:98:OTHER:OTHER;3:20:COLLISION INVOLVING OTHER MOVABLE OBJECT

Other crashes by this carrier

10 additional crash record(s) on file.

Record	Date	State	Severity	Injuries
cr_5094070	Jan 18, 2026	MN	Tow-Away	0
cr_5081097	Dec 19, 2025	MO	Injury	1
cr_5067361	Nov 19, 2025	IA	Tow-Away	0
cr_5046117	Oct 20, 2025	IA	Tow-Away	0
cr_4994895	Jul 31, 2025	IA	Tow-Away	0
cr_4956743	Jun 2, 2025	SD	Tow-Away	0
cr_4919493	Jan 3, 2025	MN	Tow-Away	0
cr_4853863	Nov 21, 2024	MO	Tow-Away	0
cr_4844177	Nov 14, 2024	IA	Tow-Away	0
cr_4846231	Nov 2, 2024	IL	Tow-Away	0

Related records

Vehicle

2021 VOLVO TRUCK VNL

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

Carrier

HY-VEE INC

USDOT 117784 · 281 crashes · 439 inspections

Vehicle

VIN: 4V4NC9EH0MN271573

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

State

Crashes in Missouri

Statewide crash records.

Agency

HY-VEE INC

Crashes reported by this law-enforcement agency.

City

Crashes in KANSAS CITY, MO

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.