Crash Record FL2561703203

FMCSA crash record in LAKE ALFRED on Sep 5, 2023.

Injury Federal Recordable

What happened

On September 5, 2023, FMCSA recorded an injury crash with 2 people hurt in LAKE ALFRED, Florida. The vehicle was operated by AVENTURA TRANSPORTATION SERVICES INC (USDOT 2348407). Recorded conditions: 1 / 1 / 1 pavement. Reported by AVENTURA TRANSPORTATION SERVICES INC, FMCSA reference FL2561703203.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

AVENTURA TRANSPORTATION SERVICES INC

Vehicle Type

Truck

Severity

Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

2 injury · 4 tow-away

Crashes per 100 power units (24 mo)

0.0

0 crashes · 3 units

Days since prior carrier crash

Last on Aug 9, 2023

Vs fleet-size peers

above the median

Cohort median 0.0 · 3,554,606 carriers

Geographic context

How this crash sits in its setting.

Within LAKE ALFRED, Florida, 16 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

UNKNOWN · 2 reports
EG TRANS EXPRESS CORP · 1 reports
DISCOVERY ACADEMY OF LAKE ALFRED INC · 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 #:: FL2561703203
Date:: Sep 5, 2023
Time:: 1447
State:: Florida
City:: LAKE ALFRED
Fatalities:: 0
Injuries:: 2
Tow-Away:: Yes
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: AVENTURA TRANSPORTATION SERVICES INC (2348407)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	9	3	1XKYDP9X6LJ349487	FP4989 (IA)	AVENTURA TRANSPORTATION SERVICES INC	3	No

Crash event

Event sequence description.

1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT

Other crashes by this carrier

8 additional crash record(s) on file.

Record	Date	State	Severity	Fatalities	Injuries
cr_4604312	Aug 9, 2023	NC	Injury	0	1
cr_4550553	Apr 22, 2023	NY	Tow-Away	0	0
cr_4520078	Mar 5, 2023	RI	Tow-Away	0	0
cr_3746381	Feb 14, 2019	PA	Injury	0	1
cr_3602400	May 20, 2018	FL	Tow-Away	0	0
cr_3189054	Mar 4, 2016	DE	Injury	0	1
cr_2969269	Dec 20, 2014	NC	Tow-Away	0	0
cr_3195325	May 7, 2014	NJ	Fatal	1	0

Related records

Carrier

AVENTURA TRANSPORTATION SERVICES INC

USDOT 2348407 · 9 crashes · 16 inspections

Vehicle

VIN: 1XKYDP9X6LJ349487

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

State

Crashes in Florida

Statewide crash records.

Agency

AVENTURA TRANSPORTATION SERVICES INC

Crashes reported by this law-enforcement agency.

City

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