TruckCodex
Hubs

Crash Record CA2202200406

FMCSA crash record in ROSEVILLE on Mar 26, 2022.

Tow-Away Federal Recordable

What happened

On March 26, 2022, FMCSA recorded a tow-away crash with no reported injuries in ROSEVILLE, California. The vehicle was operated by FLYERS TRANSPORTATION LLC (USDOT 635460). Recorded conditions: 2 / 1 / 1 pavement. Reported by FLYERS TRANSPORTATION LLC, FMCSA reference CA2202200406.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
FLYERS TRANSPORTATION LLC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
5
1 fatal · 2 injury
Crashes per 100 power units (24 mo)
2.9
3 crashes · 105 units
Days since prior carrier crash
106
Last on Dec 10, 2021
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,773 carriers

Geographic context

How this crash sits in its setting.

Within ROSEVILLE, California, 45 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
2
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 #:
CA2202200406
Date:
Mar 26, 2022
Time:
2335
State:
California
City:
ROSEVILLE
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
FLYERS TRANSPORTATION LLC (635460)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 4 1XKYDK9X8LJ416187 XP60598 (CA) FLYERS TRANSPORTATION 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
cr_5116385 Feb 7, 2026 CA Tow-Away 0 0
cr_5081193 Dec 22, 2025 AZ Tow-Away 0 0
cr_4877478 Dec 10, 2024 CA Tow-Away 0 0
cr_4795192 Aug 4, 2024 CA Tow-Away 0 0
cr_4760658 May 26, 2024 CA Tow-Away 0 0
cr_4698016 Jan 16, 2024 CA Tow-Away 0 0
cr_4694744 Jan 2, 2024 CA Tow-Away 0 0
cr_4754943 Dec 4, 2023 CA Injury 0 4
cr_4620450 Aug 24, 2023 CA Tow-Away 0 0
cr_4581076 Jun 4, 2023 CA Injury 0 2

Related records

Carrier
FLYERS TRANSPORTATION LLC
USDOT 635460 · 34 crashes · 215 inspections
Vehicle
VIN: 1XKYDK9X8LJ416187
Decode this VIN for make, model, year, and recall data.
State
Crashes in California
Statewide crash records.
Agency
FLYERS TRANSPORTATION LLC
Crashes reported by this law-enforcement agency.
City
Crashes in ROSEVILLE, 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.