Skip to main content
TruckCodex
Hubs

Crash Record CA2652100473

FMCSA crash record in UNINCORPORATED on Feb 12, 2021.

Injury Federal Recordable

What happened

On February 12, 2021, FMCSA recorded an injury crash with one person hurt in UNINCORPORATED, California. The vehicle was operated by RYDER INTEGRATED LOGISTICS INC (USDOT 165420). Recorded conditions: 3 / 1 / 2 pavement. Reported by RYDER, FMCSA reference CA2652100473.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
2
Carrier
RYDER INTEGRATED LOGISTICS INC
USDOT 165420
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
456
15 fatal · 163 injury
Crashes per 100 power units (24 mo)
6.3
148 crashes · 2,367 units
Days since prior carrier crash
1
Last on Feb 11, 2021
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,877 carriers

Geographic context

How this crash sits in its setting.

Within UNINCORPORATED, California, 6,503 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
2

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 #:
CA2652100473
Date:
Feb 12, 2021
Time:
0223
State:
California
City:
UNINCORPORATED
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
RYDER INTEGRATED LOGISTICS INC (165420)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 3AKJGEFG4LSLL7725 2901339 (IN) RYDER 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
cmvettpyj00arogssghh2y9mc Oct 12, 2026 TN Injury 0 1
cmvettpyv00b7ogssd3mmxtkd Oct 10, 2026 KY Tow-Away 0 0
cmup2ni1v002fl4z82vbavpnr Sep 23, 2026 KY Tow-Away 0 0
cmqvwanqt000zp8iu7rbkbo24 Jun 22, 2026 TN Tow-Away 0 0
cmqesjovi0001p4usoezvxtzl Jun 10, 2026 TN Injury 0 1
cmphifne0003xpjl9ms1v679u May 18, 2026 TN Injury 0 1
cmny3ygor00r6k38vqzpei8qm Apr 3, 2026 KY Injury 0 1
cmny3yfxt00bjk38vb3mwj58r Apr 2, 2026 KY Tow-Away 0 0
cr_5126418 Mar 24, 2026 KY Injury 0 1
cr_5125953 Mar 24, 2026 PA Tow-Away 0 0

Carrier booking & risk tools

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

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

Related records

Carrier
RYDER INTEGRATED LOGISTICS INC
USDOT 165420 · 4,405 crashes · 4,969 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 3AKJGEFG4LSLL7725
Decode this VIN for make, model, year, and recall data.
State
Crashes in California
Statewide crash records.
Agency
RYDER
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.