TruckCodex
Hubs

Crash Record FL2601098104

FMCSA crash record in FORT LAUDERDALE on Apr 30, 2024.

Injury Federal Recordable Bus

What happened

On April 30, 2024, FMCSA recorded an injury crash with one person hurt in FORT LAUDERDALE, Florida. The vehicle was operated by KEOLIS TRANSIT SERVICES LLC (USDOT 2866231). Recorded conditions: 3 / 1 / 1 pavement. Reported by KEOLIS TRANSIT SERVICES LLC, FMCSA reference FL2601098104.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
2
Carrier
KEOLIS TRANSIT SERVICES LLC
Vehicle Type
Bus
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
17
6 injury · 16 tow-away
Crashes per 100 power units (24 mo)
1.9
37 crashes · 1,913 units
Days since prior carrier crash
5
Last on Apr 25, 2024
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,838 carriers

Geographic context

How this crash sits in its setting.

Within FORT LAUDERDALE, Florida, 113 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
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 #:
FL2601098104
Date:
Apr 30, 2024
Time:
0045
State:
Florida
City:
FORT LAUDERDALE
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
KEOLIS TRANSIT SERVICES LLC (2866231)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 4 2 1N9APAL99LC084046 PCGX29 (FL) KEOLIS TRANSIT SERVICES LLC 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_5088669 Jan 8, 2026 AZ Injury 0 1
cr_5095336 Dec 30, 2025 CA Injury 0 1
cr_5090689 Nov 25, 2025 CA Injury 0 1
cr_5122449 Nov 21, 2025 AZ Injury 0 1
cr_5065840 Nov 18, 2025 AZ Tow-Away 0 0
cr_5051022 Oct 17, 2025 AZ Injury 0 1
cr_5047516 Oct 12, 2025 AZ Tow-Away 0 0
cr_5033892 Aug 31, 2025 FL Tow-Away 0 0
cr_5030429 Aug 29, 2025 AZ Tow-Away 0 0
cr_4991681 Jul 30, 2025 DC Injury 0 1

Related records

Vehicle
2020 ELDORADO NATIONAL Axess
NHTSA recalls and complaints for this make/model/year.
Carrier
KEOLIS TRANSIT SERVICES LLC
USDOT 2866231 · 69 crashes · 370 inspections
Vehicle
VIN: 1N9APAL99LC084046
Decode this VIN for make, model, year, and recall data.
State
Crashes in Florida
Statewide crash records.
Agency
KEOLIS TRANSIT SERVICES LLC
Crashes reported by this law-enforcement agency.
City
Crashes in FORT LAUDERDALE, FL
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.