Crash Record CA3906006040

FMCSA crash record in TRACY on Nov 21, 2023.

Tow-Away Federal Recordable

What happened

On November 21, 2023, FMCSA recorded a tow-away crash with no reported injuries in TRACY, California. The vehicle was operated by JORDAN HOLDINGS INC (USDOT 1351000). Recorded conditions: 1 / 1 / 1 pavement. Reported by JORDAN HOLDINGS INC, FMCSA reference CA3906006040.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

JORDAN HOLDINGS 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 · 28 injury

Crashes per 100 power units (24 mo)

4.3

9 crashes · 209 units

Days since prior carrier crash

Last on Nov 15, 2023

Vs fleet-size peers

above the median

Cohort median 0.0 · 26,684 carriers

Geographic context

How this crash sits in its setting.

Within TRACY, California, 33 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

CALIFORNIA DEPARTMENT OF TRANSPORTATION · 2 reports
TRACY DELTA SOLID WASTE MGMT INC · 2 reports
ASBURY ENVIRONMENTAL SERVICES · 1 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 #:: CA3906006040
Date:: Nov 21, 2023
Time:: 0806
State:: California
City:: TRACY
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: JORDAN HOLDINGS INC (1351000)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	9	3	1XPBD49X8PD804150	P1168823 (CA)	JORDAN HOLDINGS 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	Injuries
cr_5068117	Nov 28, 2025	LA	Tow-Away	0
cr_4915551	Mar 15, 2025	KY	Injury	3
cr_4862296	Dec 7, 2024	CT	Injury	1
cr_4855583	Nov 22, 2024	IL	Injury	1
cr_4845136	Nov 8, 2024	OH	Tow-Away	0
cr_4832173	Oct 12, 2024	NC	Tow-Away	0
cr_4846744	Oct 8, 2024	GA	Tow-Away	0
cr_4826465	Sep 8, 2024	CO	Tow-Away	0
cr_4812118	Sep 6, 2024	MI	Tow-Away	0
cr_4799239	Aug 25, 2024	NC	Injury	1

Related records

Carrier

JORDAN HOLDINGS INC

USDOT 1351000 · 157 crashes · 568 inspections

Vehicle

VIN: 1XPBD49X8PD804150

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

State

Crashes in California

Statewide crash records.

Agency

JORDAN HOLDINGS INC

Crashes reported by this law-enforcement agency.

City

Crashes in TRACY, 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.