Skip to main content
TruckCodex
Hubs

Crash Record CA8402304425

FMCSA crash record in RIVERSIDE on Aug 28, 2023.

Injury Federal Recordable

What happened

On August 28, 2023, FMCSA recorded an injury crash with one person hurt in RIVERSIDE, California. The vehicle was operated by UNFI TRANSPORT LLC (USDOT 179097). Recorded conditions: 3 / 1 / 1 pavement. Reported by UNFI TRANSPORT LLC, FMCSA reference CA8402304425.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
2
Carrier
UNFI TRANSPORT LLC
USDOT 179097
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
136
47 injury · 125 tow-away
Crashes per 100 power units (24 mo)
3.9
87 crashes · 2,222 units
Days since prior carrier crash
6
Last on Aug 22, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,881 carriers

Geographic context

How this crash sits in its setting.

Within RIVERSIDE, California, 209 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
3
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 #:
CA8402304425
Date:
Aug 28, 2023
Time:
2339
State:
California
City:
RIVERSIDE
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
UNFI TRANSPORT LLC (179097)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 3HCDZAPR8LL179626 1020043 (IN) UNFI TRANSPORT LLC 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
cmvettpw50065ogssdw6hvj5t Oct 11, 2026 VA Tow-Away 0 0
cmsw88scu00dlpev3k5hrreb7 Aug 7, 2026 NC Injury 0 1
cmsw88so500rdpev3ntoi4vfq Aug 5, 2026 MN Tow-Away 0 0
cms76vgqe001xpehvlyrww4ms Jul 23, 2026 NJ Tow-Away 0 0
cr_5124564 Mar 11, 2026 PA Injury 0 1
cr_5096171 Jan 30, 2026 TN Tow-Away 0 0
cr_5118543 Jan 30, 2026 PA Tow-Away 0 0
cr_5102704 Jan 24, 2026 CA Tow-Away 0 0
cr_5096924 Jan 20, 2026 NJ Tow-Away 0 0
cr_5096532 Jan 20, 2026 AZ Tow-Away 0 0

Carrier booking & risk tools

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

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

Related records

Carrier
UNFI TRANSPORT LLC
USDOT 179097 · 675 crashes · 3,273 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 3HCDZAPR8LL179626
Decode this VIN for make, model, year, and recall data.
State
Crashes in California
Statewide crash records.
Agency
UNFI TRANSPORT LLC
Crashes reported by this law-enforcement agency.
City
Crashes in RIVERSIDE, CA
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.