TruckCodex
Hubs

Crash Record CA3352200478

FMCSA crash record in UNINCORPORATED on Mar 8, 2022.

Tow-Away Federal Recordable Bus

What happened

On March 8, 2022, FMCSA recorded a tow-away crash with no reported injuries in UNINCORPORATED, California. The vehicle was operated by SAN MATEO COUNTY TRANSIT DISTRICT (USDOT 2671515). Recorded conditions: 1 / 1 / 1 pavement. Reported by SAN MATEO COUNTY TRANSIT DISTRICT, FMCSA reference CA3352200478.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
3
Carrier
SAN MATEO COUNTY TRANSIT DISTRICT
Vehicle Type
Bus
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
17
1 fatal · 7 injury
Crashes per 100 power units (24 mo)
3.8
11 crashes · 292 units
Days since prior carrier crash
1
Last on Mar 7, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,695 carriers

Geographic context

How this crash sits in its setting.

Within UNINCORPORATED, California, 7,378 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 #:
CA3352200478
Date:
Mar 8, 2022
Time:
1220
State:
California
City:
UNINCORPORATED
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
3
Carrier (USDOT):
SAN MATEO COUNTY TRANSIT DISTRICT (2671515)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 4 2 15GGD3012D1183133 1382628 (CA) SAN MATEO COUNTY TRANSIT DISTRICT 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_5065800 Nov 9, 2025 CA Injury 0 1
cr_5065808 Oct 26, 2025 CA Injury 0 1
cr_5050411 Sep 24, 2025 CA Injury 0 3
cr_5058639 May 24, 2025 CA Injury 0 1
cr_4947520 May 13, 2025 CA Injury 0 7
cr_4989180 Apr 18, 2025 CA Tow-Away 0 0
cr_4923513 Mar 17, 2025 CA Tow-Away 0 0
cr_4899220 Jan 22, 2025 CA Injury 0 1
cr_4888998 Jan 17, 2025 CA Tow-Away 0 0
cr_4874212 Nov 26, 2024 CA Tow-Away 0 0

Related records

Vehicle
2013 GILLIG Low Floor Bus
NHTSA recalls and complaints for this make/model/year.
Carrier
SAN MATEO COUNTY TRANSIT DISTRICT
USDOT 2671515 · 78 crashes · 104 inspections
Vehicle
VIN: 15GGD3012D1183133
Decode this VIN for make, model, year, and recall data.
State
Crashes in California
Statewide crash records.
Agency
SAN MATEO COUNTY TRANSIT DISTRICT
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.