Skip to main content
TruckCodex
Hubs

Crash Record CA190016-471

FMCSA crash record in COMMERCE on Nov 18, 2025.

Injury Federal Recordable

What happened

On November 18, 2025, FMCSA recorded an injury crash with one person hurt in COMMERCE, California. The vehicle was operated by J B HUNT TRANSPORT INC (USDOT 80806). Recorded conditions: 5 / 1 / 1 pavement. Reported by J B HUNT TRANSPORT INC, FMCSA reference CA190016-471.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
2
Carrier
USDOT 80806
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
1,630
49 fatal · 544 injury
Crashes per 100 power units (24 mo)
4.2
1,052 crashes · 25,280 units
Days since prior carrier crash
1
Last on Nov 17, 2025
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,897 carriers

Geographic context

How this crash sits in its setting.

Within COMMERCE, California, 51 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
5
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 #:
CA190016-471
Date:
Nov 18, 2025
Time:
1730
State:
California
City:
COMMERCE
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
2

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 13 3AKJHLDV1RSVE9649 3577682 (IN) J B HUNT TRANSPORT INC 3 No

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cmwegqbqd001no3kjse4amw0b Nov 7, 2026 MN Injury 0 1
cmwd62p67004xo3wwovw7d3v4 Nov 5, 2026 AR Tow-Away 0 0
cmwd62p8d007xo3ww1oo7yz0f Nov 4, 2026 MN Tow-Away 0 0
cmw3er80h001fo3skbvyjas8k Oct 30, 2026 MI Tow-Away 0 0
cmvnd7c5c001ro3b5iu0mwz3o Oct 19, 2026 WA Tow-Away 0 0
cmvkkgib4000zo3pw9js2vp50 Oct 19, 2026 ME Tow-Away 0 0
cmvettpz200blogsswa3qxxi0 Oct 9, 2026 VA Tow-Away 0 0
cmvettq7200ppogss7k79a9nb Oct 8, 2026 OH Injury 0 1
cmvettr5f013togssav1wvbco Oct 6, 2026 CA Tow-Away 0 0
cmup2ni260035l4z8bfo4gqwe Sep 25, 2026 WV Tow-Away 0 0

Carrier booking & risk tools

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

Related records

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.