Crash Record CA0009684009

FMCSA crash record in RANCHO CORDOVA on Feb 7, 2024.

Injury Federal Recordable

What happened

On February 7, 2024, FMCSA recorded an injury crash with one person hurt in RANCHO CORDOVA, California. The vehicle was operated by AT&T SERVICES INC (USDOT 333636). Recorded conditions: 1 / 1 / 2 pavement. Reported by AT&T SERVICES INC, FMCSA reference CA0009684009.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

AT&T SERVICES INC

Vehicle Type

Truck

Severity

Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

110

4 fatal · 39 injury

Crashes per 100 power units (24 mo)

0.3

56 crashes · 18,627 units

Days since prior carrier crash

Last on Jan 18, 2024

Vs fleet-size peers

above the median

Cohort median 0.0 · 3,837 carriers

Geographic context

How this crash sits in its setting.

Within RANCHO CORDOVA, California, 19 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

SACRAMENTO REGIONAL TRANSIT DISTRICT · 2 reports
D & L TRANSPORTATION LLC · 1 reports
ASPIRE COMMUNICATIONS LLC · 1 reports

Contributing factors

What the responding officer recorded.

Light: 1
Weather: 1
Road surface: 2

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 #:: CA0009684009
Date:: Feb 7, 2024
Time:: 1355
State:: California
City:: RANCHO CORDOVA
Fatalities:: 0
Injuries:: 1
Tow-Away:: Yes
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: AT&T SERVICES INC (333636)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	5	98	1FDUF4GY6HEE37031	24494G2 (CA)	AT&T SERVICES INC	2	No

Crash event

Event sequence description.

1:13:COLLISION INVOLVING MOTOR VEHICLE IN TRANSPORT

Other crashes by this carrier

10 additional crash record(s) on file.

Record	Date	State	Severity	Fatalities	Injuries
cr_5114937	Feb 20, 2026	LA	Tow-Away	0	0
cr_5117148	Feb 19, 2026	GA	Tow-Away	0	0
cr_5114134	Feb 19, 2026	OK	Injury	0	1
cr_5121674	Feb 17, 2026	CA	Tow-Away	0	0
cr_5110226	Feb 12, 2026	MO	Tow-Away	0	0
cr_5108914	Feb 9, 2026	OH	Fatal	1	0
cr_5114795	Jan 25, 2026	MI	Tow-Away	0	0
cr_5097683	Jan 14, 2026	MI	Tow-Away	0	0
cr_5099741	Jan 14, 2026	MI	Tow-Away	0	0
cr_5098810	Jan 7, 2026	CA	Tow-Away	0	0

Related records

Vehicle

2017 FORD F-450

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

EXTERIOR LIGHTING:BRAKE LIGHTS

USDOT 333636 · 628 crashes · 1,257 inspections

Vehicle

VIN: 1FDUF4GY6HEE37031

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

State

Crashes in California

Statewide crash records.

Agency

AT&T SERVICES INC

Crashes reported by this law-enforcement agency.

City

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