Skip to main content
TruckCodex
Hubs

Crash Record CA6752111019

FMCSA crash record in ANAHEIM on Jul 13, 2021.

Tow-Away Federal Recordable

What happened

On July 13, 2021, FMCSA recorded a tow-away crash with no reported injuries in ANAHEIM, California. The vehicle was operated by HUB GROUP DEDICATED LLC (USDOT 801828). Recorded conditions: 3 / 1 / 1 pavement. Reported by HUB GROUP DEDICATED LLC, FMCSA reference CA6752111019.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
HUB GROUP DEDICATED LLC
USDOT 801828
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
199
3 fatal · 60 injury
Crashes per 100 power units (24 mo)
4.8
119 crashes · 2,505 units
Days since prior carrier crash
1
Last on Jul 12, 2021
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,866 carriers

Geographic context

How this crash sits in its setting.

Within ANAHEIM, California, 176 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 #:
CA6752111019
Date:
Jul 13, 2021
Time:
0055
State:
California
City:
ANAHEIM
Fatalities:
0
Injuries:
0
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 98 3AKJHTDV0KSKG8917 2786298 (IN) HUB GROUP DEDICATED 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
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

Carrier booking & risk tools

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

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

Related records

Carrier
HUB GROUP DEDICATED LLC
USDOT 801828 · 1,137 crashes · 4,728 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 3AKJHTDV0KSKG8917
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 ANAHEIM, 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.