TruckCodex
Hubs

Crash Record CA0009486799

FMCSA crash record in TRACY on Sep 9, 2022.

Injury Federal Recordable

What happened

On September 9, 2022, FMCSA recorded an injury crash with one person hurt in TRACY, California. The vehicle was operated by AMAZON LOGISTICS INC (USDOT 2881058). Recorded conditions: 1 / 1 / 1 pavement. Reported by AMAZON LOGISTICS INC, FMCSA reference CA0009486799.

Carrier pattern note

This is the carrier's 232 crashes in the past 24 months — above the typical pattern (median 0) for fleets of 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
0
Injuries
1
Vehicles
2
Carrier
AMAZON LOGISTICS INC
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
232
4 fatal · 85 injury
Crashes per 100 power units (24 mo)
2.0
299 crashes · 15,259 units
Days since prior carrier crash
3
Last on Sep 6, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,837 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:

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 #:
CA0009486799
Date:
Sep 9, 2022
Time:
1048
State:
California
City:
TRACY
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
AMAZON LOGISTICS INC (2881058)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 5 3 1F65F5KN9M0A05006 43A80J (AZ) AMAZON LOGISTICS INC 2 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
cmtch5ocs000jpmuct6sxdmus Aug 21, 2026 KY Tow-Away 0 0
cmt5onxxh0007pmdmttd4x8og Aug 19, 2026 NC Injury 0 1
cmt5ony13003vpmdm3p75texs Aug 16, 2026 MI Tow-Away 0 0
cmrpwdsk9002ppe2cna6g7vqy Jul 12, 2026 WA Tow-Away 0 0
cmrk8iqyn002lpelc4b28jnto Jul 7, 2026 VA Injury 0 1
cmqxb77cv0073p8f0d64rtg4i Jun 22, 2026 NC Tow-Away 0 0
cmqugos7i0009p8o5awf0sgk0 Jun 20, 2026 NJ Injury 0 1
cmq0fazfm0075pmw8rat3v97n May 27, 2026 OH Injury 0 2
cmoqocdt40007mztos5cit57g Apr 30, 2026 NC Tow-Away 0 0
cmouyr2vh006rnu1ky12bhu25 Apr 29, 2026 NJ Injury 0 1

Related records

Carrier
AMAZON LOGISTICS INC
USDOT 2881058 · 853 crashes · 6,409 inspections
Vehicle
VIN: 1F65F5KN9M0A05006
Decode this VIN for make, model, year, and recall data.
State
Crashes in California
Statewide crash records.
Agency
AMAZON LOGISTICS 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.