Crash Record CA4812200323

FMCSA crash record in UNINCORPORATED on May 14, 2022.

Tow-Away Federal Recordable

What happened

On May 14, 2022, FMCSA recorded a tow-away crash with no reported injuries in UNINCORPORATED, California. The vehicle was operated by TS TRANSPORTING INC (USDOT 1825494). Recorded conditions: 1 / 1 / 1 pavement. Reported by TS TRANSPORTING INC, FMCSA reference CA4812200323.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

TS TRANSPORTING INC

Vehicle Type

Truck

Severity

Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

1 fatal · 2 injury

Crashes per 100 power units (24 mo)

3.7

6 crashes · 161 units

Days since prior carrier crash

Last on Mar 31, 2022

Vs fleet-size peers

above the median

Cohort median 0.0 · 27,000 carriers

Geographic context

How this crash sits in its setting.

Within UNINCORPORATED, California, 6,901 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

UNITED PARCEL SERVICE INC · 47 reports
FEDERAL EXPRESS CORPORATION · 47 reports
J B HUNT TRANSPORT INC · 38 reports

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 #:: CA4812200323
Date:: May 14, 2022
Time:: 1555
State:: California
City:: UNINCORPORATED
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: TS TRANSPORTING INC (1825494)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	9	3	1HSHWSNNXEH779232	9G10033 (CA)	TS TRANSPORTING 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_5121685	Mar 11, 2026	CA	Tow-Away	0	0
cr_5118976	Feb 18, 2026	CA	Tow-Away	0	0
cr_5046021	Sep 15, 2025	CA	Tow-Away	0	0
cr_4915352	Feb 24, 2025	CA	Tow-Away	0	0
cr_4907573	Feb 6, 2025	CA	Tow-Away	0	0
cr_4896693	Feb 1, 2025	CA	Injury	0	1
cr_4819288	Sep 9, 2024	CA	Tow-Away	0	0
cr_4803529	Jul 24, 2024	CA	Fatal	1	1
cr_4745377	Apr 12, 2024	CA	Tow-Away	0	0
cr_4732377	Mar 26, 2024	CA	Tow-Away	0	0

Related records

Vehicle

2014 INTERNATIONAL RA027

NHTSA recalls and complaints for this make/model/year.

Carrier

TS TRANSPORTING INC

USDOT 1825494 · 41 crashes · 377 inspections

Vehicle

VIN: 1HSHWSNNXEH779232

Decode this VIN for make, model, year, and recall data.

State

Crashes in California

Statewide crash records.

Agency

TS TRANSPORTING INC

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.