Crash Record CA0009602771

FMCSA crash record in LONG BEACH on Jun 10, 2023.

Tow-Away Federal Recordable

What happened

On June 10, 2023, FMCSA recorded a tow-away crash with no reported injuries in LONG BEACH, California. The vehicle was operated by CITY OF LONG BEACH (USDOT 219043). Recorded conditions: 3 / 1 / 1 pavement. Reported by CITY OF LONG BEACH, FMCSA reference CA0009602771.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

CITY OF LONG BEACH

Vehicle Type

Truck

Severity

Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

2 injury · 7 tow-away

Crashes per 100 power units (24 mo)

0.7

3 crashes · 403 units

Days since prior carrier crash

105

Last on Feb 25, 2023

Vs fleet-size peers

above the median

Cohort median 0.0 · 26,687 carriers

Geographic context

How this crash sits in its setting.

Within LONG BEACH, California, 207 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

LONG BEACH PUBLIC TRANSPORTATION COMPANY · 7 reports
MISSION SCHOOL TRANSPORTATION INC · 3 reports
RYDER TRUCK RENTAL INC · 3 reports

Contributing factors

What the responding officer recorded.

Light: 3
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 #:: CA0009602771
Date:: Jun 10, 2023
Time:: 0235
State:: California
City:: LONG BEACH
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 1
Carrier (USDOT):: CITY OF LONG BEACH (219043)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	5	98	1FDUF5GY3GEB69978	1430931 (CA)	CITY OF LONG BEACH	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
cr_4868202	Dec 13, 2024	CA	Tow-Away	0	0
cr_4859986	Nov 16, 2024	CA	Injury	0	2
cr_4843655	Sep 24, 2024	CA	Fatal	1	0
cr_4835905	Aug 2, 2024	CA	Tow-Away	0	0
cr_4769886	Jun 17, 2024	CA	Tow-Away	0	0
cr_4788736	Jun 4, 2024	CA	Injury	0	1
cr_4755532	Mar 4, 2024	CA	Tow-Away	0	0
cr_4691688	Jan 3, 2024	CA	Tow-Away	0	0
cr_4652001	Oct 29, 2023	CA	Fatal	1	1
cr_4784185	Oct 10, 2023	CA	Tow-Away	0	0

Related records

Vehicle

2016 FORD F-550

NHTSA recalls and complaints for this make/model/year.

LATCHES/LOCKS/LINKAGES:DOORS:LATCH

Carrier

CITY OF LONG BEACH

USDOT 219043 · 21 crashes · 0 inspections

Vehicle

VIN: 1FDUF5GY3GEB69978

Decode this VIN for make, model, year, and recall data.

State

Crashes in California

Statewide crash records.

Agency

CITY OF LONG BEACH

Crashes reported by this law-enforcement agency.

City

Crashes in LONG BEACH, 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.