TruckCodex
Hubs

Crash Record CA8402200064

FMCSA crash record in RIVERSIDE on Jan 6, 2022.

Injury Federal Recordable

What happened

On January 6, 2022, FMCSA recorded an injury crash with 2 people hurt in RIVERSIDE, California. The vehicle was operated by ROYAL EXPRESS INC (USDOT 838117). Recorded conditions: 1 / 1 / 1 pavement. Reported by ROYAL EXPRESS INC, FMCSA reference CA8402200064.

Carrier pattern note

This is the carrier's 19 crashes in the past 24 months — above the typical pattern (median 0) for fleets of 51–500 power units.

Geographic note

This crash is part of an active corridor: 240 crashes occurred in the same city in the past 24 months.

Fatalities
0
Injuries
2
Vehicles
3
Carrier
ROYAL EXPRESS INC
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
19
10 injury · 18 tow-away
Crashes per 100 power units (24 mo)
12.1
17 crashes · 140 units
Days since prior carrier crash
15
Last on Dec 22, 2021
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,680 carriers

Geographic context

How this crash sits in its setting.

Within RIVERSIDE, California, 240 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 #:
CA8402200064
Date:
Jan 6, 2022
Time:
1120
State:
California
City:
RIVERSIDE
Fatalities:
0
Injuries:
2
Tow-Away:
Yes
HazMat:
No
Vehicles:
3
Carrier (USDOT):
ROYAL EXPRESS INC (838117)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 3HSDZAPR2LN041900 R431273 (TX) ROYAL EXPRESS 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_5120759 Mar 4, 2026 TX Injury 0 1
cr_5112416 Feb 22, 2026 OH Injury 0 2
cr_5084435 Dec 18, 2025 TX Injury 0 1
cr_5067903 Nov 2, 2025 IN Injury 0 2
cr_5046472 Oct 18, 2025 TX Tow-Away 0 0
cr_5024648 Aug 5, 2025 ID Tow-Away 0 0
cr_5012048 Jul 5, 2025 TX Injury 0 1
cr_5010831 Jun 19, 2025 TX Injury 0 1
cr_5011258 Jun 10, 2025 TX Tow-Away 0 0
cr_5010214 Jun 7, 2025 TX Tow-Away 0 0

Related records

Vehicle
2020 INTERNATIONAL LT625
NHTSA recalls and complaints for this make/model/year.
Carrier
ROYAL EXPRESS INC
USDOT 838117 · 208 crashes · 1,420 inspections
Vehicle
VIN: 3HSDZAPR2LN041900
Decode this VIN for make, model, year, and recall data.
State
Crashes in California
Statewide crash records.
Agency
ROYAL EXPRESS INC
Crashes reported by this law-enforcement agency.
City
Crashes in RIVERSIDE, 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.