Crash Record CA0009615567

FMCSA crash record in LAKEWOOD on Jul 28, 2023.

Injury Federal Recordable Bus

What happened

On July 28, 2023, FMCSA recorded an injury crash with 2 people hurt in LAKEWOOD, California. The vehicle was operated by LONG BEACH PUBLIC TRANSPORTATION COMPANY (USDOT 2735822). Recorded conditions: 1 / 1 / 1 pavement. Reported by LONG BEACH PUBLIC TRANSPORTATION COMPANY, FMCSA reference CA0009615567.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

LONG BEACH PUBLIC TRANSPORTATION COMPANY

Vehicle Type

Bus

Severity

Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

10 injury · 21 tow-away

Crashes per 100 power units (24 mo)

3.8

11 crashes · 293 units

Days since prior carrier crash

Last on Jul 26, 2023

Vs fleet-size peers

above the median

Cohort median 0.0 · 26,695 carriers

Geographic context

How this crash sits in its setting.

Within LAKEWOOD, California, 6 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

LONG BEACH PUBLIC TRANSPORTATION COMPANY · 2 reports
ADONAI LOGISTICS LLC · 1 reports
EDCO DISPOSAL CORPORATION · 1 reports

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 #:: CA0009615567
Date:: Jul 28, 2023
Time:: 1142
State:: California
City:: LAKEWOOD
Fatalities:: 0
Injuries:: 2
Tow-Away:: No
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: LONG BEACH PUBLIC TRANSPORTATION COMPANY (2735822)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	4	2	5FYC8FB16HB051856	1535578 (CA)	LONG BEACH PUBLIC TRANSPORTATION COMPANY	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	Injuries
cr_5104837	Jan 14, 2026	CA	Tow-Away	0
cr_5065988	Nov 11, 2025	CA	Tow-Away	0
cr_5104838	Oct 2, 2025	CA	Injury	3
cr_5051067	Jul 12, 2025	CA	Injury	1
cr_5060597	Jun 17, 2025	CA	Injury	2
cr_4950904	May 11, 2025	CA	Tow-Away	0
cr_4944807	May 6, 2025	CA	Injury	2
cr_4930401	Mar 23, 2025	CA	Injury	1
cr_4886093	Dec 18, 2024	CA	Tow-Away	0
cr_4894008	Nov 6, 2024	CA	Injury	2

Related records

Vehicle

2017 NEW FLYER Xcelsior

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

LONG BEACH PUBLIC TRANSPORTATION COMPANY

USDOT 2735822 · 88 crashes · 119 inspections

Vehicle

VIN: 5FYC8FB16HB051856

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

State

Crashes in California

Statewide crash records.

Agency

LONG BEACH PUBLIC TRANSPORTATION COMPANY

Crashes reported by this law-enforcement agency.

City

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