TruckCodex
Hubs

Crash Record CA6302500741

FMCSA crash record in UNINCORPORATED on May 21, 2025.

Injury Federal Recordable

What happened

On May 21, 2025, FMCSA recorded an injury crash with one person hurt in UNINCORPORATED, California. The vehicle was operated by HUB GROUP DEDICATED LLC (USDOT 801828). Recorded conditions: 1 / 1 / 1 pavement. Reported by HUB GROUP DEDICATED LLC, FMCSA reference CA6302500741.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
2
Carrier
HUB GROUP DEDICATED LLC
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
206
8 fatal · 73 injury
Crashes per 100 power units (24 mo)
5.0
126 crashes · 2,505 units
Days since prior carrier crash
3
Last on May 18, 2025
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,838 carriers

Geographic context

How this crash sits in its setting.

Within UNINCORPORATED, California, 7,416 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 #:
CA6302500741
Date:
May 21, 2025
Time:
1800
State:
California
City:
UNINCORPORATED
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
HUB GROUP DEDICATED LLC (801828)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 3AKJHPDVXSSVW7147 2841689 (IN) HUB GROUP DEDICATED LLC 3 No

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cms8hio18000tpeo568gv9v4q Jul 26, 2026 VA Tow-Away 0 0
cmny3ygz200yok38vhzunnizs Mar 31, 2026 TN Injury 0 2
cr_5127311 Mar 31, 2026 TN Injury 0 2
cr_5125363 Mar 17, 2026 TX Injury 0 1
cr_5124849 Mar 12, 2026 TX Tow-Away 0 0
cr_5124780 Mar 9, 2026 WA Tow-Away 0 0
cr_5122231 Mar 3, 2026 TX Tow-Away 0 0
cr_5120153 Mar 3, 2026 GA Injury 0 2
cr_5124417 Feb 20, 2026 IN Injury 0 1
cr_5117658 Feb 20, 2026 PA Injury 0 1

Related records

Carrier
HUB GROUP DEDICATED LLC
USDOT 801828 · 1,137 crashes · 4,586 inspections
Vehicle
VIN: 3AKJHPDVXSSVW7147
Decode this VIN for make, model, year, and recall data.
State
Crashes in California
Statewide crash records.
Agency
HUB GROUP DEDICATED LLC
Crashes reported by this law-enforcement agency.
City
Crashes in UNINCORPORATED, 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.