Skip to main content
TruckCodex
Hubs

Crash Record CA0009829515

FMCSA crash record in SAN DIEGO on Jun 23, 2025.

Injury Federal Recordable

What happened

On June 23, 2025, FMCSA recorded an injury crash with one person hurt in SAN DIEGO, California. The vehicle was operated by US FOODS INC (USDOT 358597). Recorded conditions: 1 / 1 / 1 pavement. Reported by US FOODS INC, FMCSA reference CA0009829515.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
2
Carrier
US FOODS INC
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
231
3 fatal · 80 injury
Crashes per 100 power units (24 mo)
3.4
168 crashes · 4,941 units
Days since prior carrier crash
17
Last on Jun 6, 2025
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,864 carriers

Geographic context

How this crash sits in its setting.

Within SAN DIEGO, California, 289 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
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 #:
CA0009829515
Date:
Jun 23, 2025
Time:
1300
State:
California
City:
SAN DIEGO
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
US FOODS INC (358597)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 6 3 1FUJGBDV3FLBW4282 9F08531 (CA) US FOODS INC 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
cr_5127762 Mar 27, 2026 NJ Injury 0 1
cr_5120537 Mar 16, 2026 MN Injury 0 2
cr_5121927 Mar 11, 2026 SC Tow-Away 0 0
cr_5117822 Mar 9, 2026 MT Tow-Away 0 0
cr_5120874 Mar 4, 2026 AL Tow-Away 0 0
cr_5111774 Feb 25, 2026 PA Tow-Away 0 0
cr_5117141 Feb 19, 2026 GA Tow-Away 0 0
cr_5106448 Feb 13, 2026 SC Injury 0 2
cr_5106371 Feb 13, 2026 SC Injury 0 1
cr_5125383 Feb 13, 2026 WA Tow-Away 0 0

Related records

Vehicle
2015 FREIGHTLINER Cascadia
NHTSA recalls and complaints for this make/model/year.
Recall
20V214000
EXTERIOR LIGHTING
Recall
19V370000
SERVICE BRAKES, AIR:SUPPLY:RESERVOIR/TANK
Recall
19V093000
STEERING:LINKAGES:TIE ROD ASSEMBLY
Carrier
US FOODS INC
USDOT 358597 · 2,230 crashes · 4,779 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 1FUJGBDV3FLBW4282
Decode this VIN for make, model, year, and recall data.
State
Crashes in California
Statewide crash records.
Agency
US FOODS INC
Crashes reported by this law-enforcement agency.
City
Crashes in SAN DIEGO, 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.