TruckCodex
Hubs

Crash Record CA0009361156

FMCSA crash record in SAN FRANCISCO on Oct 22, 2021.

Injury Federal Recordable

What happened

On October 22, 2021, FMCSA recorded an injury crash with one person hurt in SAN FRANCISCO, California. The vehicle was operated by CINTAS CORPORATION NO 3 (USDOT 850618). Recorded conditions: 1 / 2 pavement. Reported by CINTAS CORPORATION NO 3, FMCSA reference CA0009361156.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
3
Carrier
CINTAS CORPORATION NO 3
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
22
1 fatal · 8 injury
Crashes per 100 power units (24 mo)
0.6
8 crashes · 1,307 units
Days since prior carrier crash
53
Last on Aug 30, 2021
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,833 carriers

Geographic context

How this crash sits in its setting.

Within SAN FRANCISCO, California, 175 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
—
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 #:
CA0009361156
Date:
Oct 22, 2021
Time:
0857
State:
California
City:
SAN FRANCISCO
Fatalities:
0
Injuries:
1
Tow-Away:
No
HazMat:
No
Vehicles:
3
Carrier (USDOT):
CINTAS CORPORATION NO 3 (850618)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 5 3 1F65F5KY1J0A22386 90438S2 (CA) CINTAS CORPORATION NO 3 2 No

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5126248 Mar 18, 2026 AZ Injury 0 1
cr_5067847 Oct 28, 2025 KS Tow-Away 0 0
cr_4950322 Apr 29, 2025 AZ Tow-Away 0 0
cr_4895087 Feb 18, 2025 ME Injury 0 1
cr_4874840 Dec 4, 2024 CA Injury 0 2
cr_4880933 Nov 14, 2024 CA Tow-Away 0 0
cr_4844564 Nov 4, 2024 PA Tow-Away 0 0
cr_4838372 Nov 1, 2024 CA Tow-Away 0 0
cr_4812156 Aug 26, 2024 MI Tow-Away 0 0
cr_4801823 Aug 2, 2024 MI Tow-Away 0 0

Related records

Carrier
CINTAS CORPORATION NO 3
USDOT 850618 · 108 crashes · 746 inspections
Vehicle
VIN: 1F65F5KY1J0A22386
Decode this VIN for make, model, year, and recall data.
State
Crashes in California
Statewide crash records.
Agency
CINTAS CORPORATION NO 3
Crashes reported by this law-enforcement agency.
City
Crashes in SAN FRANCISCO, 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.