Skip to main content
TruckCodex
Hubs

Crash Record FL2561939903

FMCSA crash record in DAYTONA BEACH on Aug 17, 2023.

Injury Federal Recordable

What happened

On August 17, 2023, FMCSA recorded an injury crash with one person hurt in DAYTONA BEACH, Florida. The vehicle was operated by PENSKE TRUCK LEASING CO LP (USDOT 327574). Recorded conditions: 1 / 1 / 1 pavement. Reported by PENSKE TRUCK LEASING CO LP, FMCSA reference FL2561939903.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
2
Carrier
USDOT 327574
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
326
10 fatal · 134 injury
Crashes per 100 power units (24 mo)
0.9
327 crashes · 38,075 units
Days since prior carrier crash
1
Last on Aug 16, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,878 carriers

Geographic context

How this crash sits in its setting.

Within DAYTONA BEACH, Florida, 55 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 #:
FL2561939903
Date:
Aug 17, 2023
Time:
1727
State:
Florida
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
2

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 5 3 3ALACWFC7KDKB8852 BA16992 (CT) PENSKE TRUCK LEASING CO LP 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
cmvettpro000logssfnfqbcfr Oct 15, 2026 ME Tow-Away 0 0
cmvettpzf00c5ogssmb25urv9 Oct 10, 2026 VA Injury 0 1
cmvettpye00ahogsspwwridzm Oct 10, 2026 TN Injury 0 3
cmvettq2600gvogss5vvd3pqa Oct 9, 2026 LA Tow-Away 0 0
cmvettq4w00lpogssut9mr2k0 Oct 8, 2026 LA Injury 0 1
cmvettq3e00jhogsszhrqlk3d Oct 8, 2026 MA Tow-Away 0 0
cmuz83jsy008rogz6ihggtwmh Sep 30, 2026 NC Tow-Away 0 0
cmu6fpo4j0001pmvz6vkhz60x Sep 14, 2026 MA Tow-Away 0 0
cmtwgme2m004rpmiyfq15hbf7 Sep 3, 2026 MI Injury 0 1
cmtfchmex0003pmjnt0s8apq9 Aug 26, 2026 NJ Injury 0 1

Carrier booking & risk tools

Check booking and risk signals for USDOT 327574 — tools open pre-filled.

Related records

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.