TruckCodex
Hubs

Crash Record CA194221-001

FMCSA crash record in LOS ANGELES on Jun 5, 2025.

Tow-Away Federal Recordable

What happened

On June 5, 2025, FMCSA recorded a tow-away crash with no reported injuries in LOS ANGELES, California. The vehicle was operated by CITY OF LOS ANGELES (USDOT 1099065). Recorded conditions: 1 / 8 / 1 pavement. Reported by CITY OF LOS ANGELES, FMCSA reference CA194221-001.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
CITY OF LOS ANGELES
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
90
28 injury · 81 tow-away
Crashes per 100 power units (24 mo)
2.3
64 crashes · 2,728 units
Days since prior carrier crash
13
Last on May 23, 2025
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,836 carriers

Geographic context

How this crash sits in its setting.

Within LOS ANGELES, California, 981 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
8
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 #:
CA194221-001
Date:
Jun 5, 2025
Time:
1145
State:
California
City:
LOS ANGELES
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
CITY OF LOS ANGELES (1099065)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 5 12 1FDRF3GN6LEE48092 1617634 (CA) CITY OF LOS ANGELES 2 No

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5121652 Feb 23, 2026 CA Tow-Away 0 0
cr_5117347 Feb 13, 2026 CA Tow-Away 0 0
cr_5115412 Feb 3, 2026 CA Tow-Away 0 0
cr_5115402 Feb 3, 2026 CA Tow-Away 0 0
cr_5097320 Jan 16, 2026 CA Tow-Away 0 0
cr_5090690 Dec 9, 2025 CA Tow-Away 0 0
cr_5079631 Dec 1, 2025 CA Tow-Away 0 0
cr_5079652 Dec 1, 2025 CA Injury 0 1
cr_5073753 Nov 18, 2025 CA Tow-Away 0 0
cr_5065802 Nov 6, 2025 CA Injury 0 3

Related records

Vehicle
2020 FORD F-350
NHTSA recalls and complaints for this make/model/year.
Recall
20V599000
POWER TRAIN:AXLE ASSEMBLY
Recall
19V633000
SEATS:FRONT ASSEMBLY:RECLINER
Carrier
CITY OF LOS ANGELES
USDOT 1099065 · 357 crashes · 72 inspections
Vehicle
VIN: 1FDRF3GN6LEE48092
Decode this VIN for make, model, year, and recall data.
State
Crashes in California
Statewide crash records.
Agency
CITY OF LOS ANGELES
Crashes reported by this law-enforcement agency.
City
Crashes in LOS ANGELES, 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.