Skip to main content
TruckCodex
Hubs

Crash Record MD22A0934686

FMCSA crash record in Maryland on Jul 23, 2022.

Injury Federal Recordable

What happened

On July 23, 2022, FMCSA recorded an injury crash with one person hurt in Maryland. The vehicle was operated by MDV SPARTANNASH LLC (USDOT 2552754). Recorded conditions: 2 / 1 pavement. Reported by MDV SPARTANNASH LLC, FMCSA reference MD22A0934686.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
2
Carrier
MDV SPARTANNASH LLC
USDOT 2552754
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
27
2 fatal · 8 injury
Crashes per 100 power units (24 mo)
4.0
11 crashes · 278 units
Days since prior carrier crash
50
Last on Jun 3, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 27,205 carriers

Geographic context

How this crash sits in its setting.

Within Maryland, 3,763 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
2
Weather
—
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 #:
MD22A0934686
Date:
Jul 23, 2022
Time:
2115
State:
Maryland
Fatalities:
0
Injuries:
1
Tow-Away:
No
HazMat:
No
Vehicles:
2
Carrier (USDOT):
MDV SPARTANNASH LLC (2552754)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 3HSDZAPR8NN364321 404158 (NE) MDV SPARTANNASH LLC 3 No

Crash event

Event sequence description.

2:98:OTHER;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
cr_5057303 Oct 28, 2025 NC Tow-Away 0 0
cr_5048264 Oct 24, 2025 VA Tow-Away 0 0
cr_5050543 Oct 16, 2025 GA Injury 0 1
cr_5101045 Jul 24, 2025 FL Injury 0 2
cr_4997811 Jun 24, 2025 KS Injury 0 1
cr_5052438 Jun 3, 2025 CO Tow-Away 0 0
cr_4906987 Mar 3, 2025 AL Tow-Away 0 0
cr_4917387 Feb 25, 2025 FL Tow-Away 0 0
cr_4895102 Feb 5, 2025 AR Injury 0 1
cr_4871102 Dec 4, 2024 IN Tow-Away 0 0

Carrier booking & risk tools

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

Book / don't book Insurance check Cancel desk Chameleon check Safety benchmark

Related records

Vehicle
2022 INTERNATIONAL LT625
NHTSA recalls and complaints for this make/model/year.
Carrier
MDV SPARTANNASH LLC
USDOT 2552754 · 107 crashes · 677 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 3HSDZAPR8NN364321
Decode this VIN for make, model, year, and recall data.
State
Crashes in Maryland
Statewide crash records.
Agency
MDV SPARTANNASH LLC
Crashes reported by this law-enforcement agency.
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.