Skip to main content
TruckCodex
Hubs

Crash Record CA5752101355

FMCSA crash record in BURBANK on May 11, 2021.

Tow-Away Federal Recordable

What happened

On May 11, 2021, FMCSA recorded a tow-away crash with no reported injuries in BURBANK, California. The vehicle was operated by TONY LEZCANO LLC (USDOT 3353226). Recorded conditions: 1 / 1 / 1 pavement. FMCSA reference CA5752101355.

Carrier pattern note

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

Geographic note

This crash is part of an active corridor: 29 crashes occurred in the same city in the past 24 months.

Fatalities
0
Injuries
0
Vehicles
2
Carrier
TONY LEZCANO LLC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
6
4 injury · 6 tow-away
Crashes per 100 power units (24 mo)
0.0
0 crashes · 6 units
Days since prior carrier crash
15
Last on Apr 26, 2021
Vs fleet-size peers
above the median
Cohort median 0.0 · 314,282 carriers

Geographic context

How this crash sits in its setting.

Within BURBANK, California, 29 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 #:
CA5752101355
Date:
May 11, 2021
Time:
1550
State:
California
City:
BURBANK
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
TONY LEZCANO LLC (3353226)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
2 5 98 3ALACWDT1EDFN9291 K116649 (TX) TONY LEZCANO LLC 2 No

Crash event

Event sequence description.

1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT

Other crashes by this carrier

9 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4233544 Sep 28, 2021 TX Tow-Away 0 0
cr_4213642 Aug 31, 2021 KY Injury 0 2
cr_4603819 Jun 29, 2021 NE Tow-Away 0 0
cr_4603213 Jun 29, 2021 NE Tow-Away 0 0
cr_4150050 Apr 26, 2021 TX Injury 0 3
cr_4088292 Dec 11, 2020 NJ Injury 0 1
cr_4022773 Aug 20, 2020 OH Tow-Away 0 0
cr_4096791 Jul 6, 2020 IL Injury 0 1
cr_3978183 May 23, 2020 AR Injury 0 1

Related records

Carrier
TONY LEZCANO LLC
USDOT 3353226 · 10 crashes · 2 inspections
Vehicle
VIN: 3ALACWDT1EDFN9291
Decode this VIN for make, model, year, and recall data.
State
Crashes in California
Statewide crash records.
City
Crashes in BURBANK, 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.