Skip to main content
TruckCodex
Hubs

Crash Record CA8402200249

FMCSA crash record in RIVERSIDE on Jan 19, 2022.

Tow-Away Federal Recordable

What happened

On January 19, 2022, FMCSA recorded a tow-away crash with no reported injuries in RIVERSIDE, California. The vehicle was operated by LINCOLN TRANSPORTATION SERVICES INC (USDOT 1120526). Recorded conditions: 3 / 1 / 1 pavement. Reported by LINCOLN TRANSPORTATION SERVICES INC, FMCSA reference CA8402200249.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
LINCOLN TRANSPORTATION SERVICES INC
USDOT 1120526
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
14
3 injury · 14 tow-away
Crashes per 100 power units (24 mo)
3.4
5 crashes · 148 units
Days since prior carrier crash
7
Last on Jan 12, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 27,205 carriers

Geographic context

How this crash sits in its setting.

Within RIVERSIDE, California, 211 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 #:
CA8402200249
Date:
Jan 19, 2022
Time:
2140
State:
California
City:
RIVERSIDE
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
LINCOLN TRANSPORTATION SERVICES INC (1120526)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 1FUJGLDR8ELBE8596 9F85696 (CA) LINCOLN TRANSPORTATION SERVICES 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_5031962 Aug 23, 2025 CA Tow-Away 0 0
cr_4989418 Jul 29, 2025 AZ Tow-Away 0 0
cr_4934988 Apr 16, 2025 CA Tow-Away 0 0
cr_4909179 Feb 7, 2025 CA Injury 0 1
cr_4895031 Jan 16, 2025 CA Tow-Away 0 0
cr_4830305 Oct 4, 2024 CA Tow-Away 0 0
cr_4825531 Sep 27, 2024 CA Injury 0 2
cr_4743111 Apr 17, 2024 CA Injury 0 1
cr_4737792 Apr 3, 2024 CA Tow-Away 0 0
cr_4737757 Apr 2, 2024 CA Tow-Away 0 0

Carrier booking & risk tools

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

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

Related records

Carrier
LINCOLN TRANSPORTATION SERVICES INC
USDOT 1120526 · 125 crashes · 416 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 1FUJGLDR8ELBE8596
Decode this VIN for make, model, year, and recall data.
State
Crashes in California
Statewide crash records.
Agency
LINCOLN TRANSPORTATION SERVICES 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.