Crash Record FL2517350002

FMCSA crash record in OCALA on Aug 28, 2022.

Tow-Away Federal Recordable

What happened

On August 28, 2022, FMCSA recorded a tow-away crash with no reported injuries in OCALA, Florida. The vehicle was operated by ENO INC (USDOT 1056669). Recorded conditions: 1 / 1 / 1 pavement. Reported by ENO INC, FMCSA reference FL2517350002.

Carrier pattern note

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

Geographic note

This crash is part of an active corridor: 82 crashes occurred in the same city in the past 24 months.

Fatalities

Injuries

Vehicles

Carrier

ENO INC

Vehicle Type

Truck

Severity

Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

4 injury · 7 tow-away

Crashes per 100 power units (24 mo)

0.0

0 crashes · 28 units

Days since prior carrier crash

Last on Jul 7, 2022

Vs fleet-size peers

above the median

Cohort median 0.0 · 313,835 carriers

Geographic context

How this crash sits in its setting.

Within OCALA, Florida, 82 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

UNKNOWN · 4 reports
CENTRAL FLORIDA TRANSPORT LLC · 3 reports
CITY OF OCALA · 3 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 #:: FL2517350002
Date:: Aug 28, 2022
Time:: 1256
State:: Florida
City:: OCALA
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: ENO INC (1056669)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	9	3	1M1AW02Y4GM054359	P1094455 (IL)	ENO INC	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_4763854	Jun 10, 2024	TN	Injury	2
cr_4748621	May 16, 2024	AL	Injury	1
cr_4724618	Mar 15, 2024	IL	Tow-Away	0
cr_4495510	Jan 17, 2023	FL	Tow-Away	0
cr_4424661	Sep 13, 2022	FL	Tow-Away	0
cr_4425015	Sep 12, 2022	FL	Tow-Away	0
cr_4417530	Sep 1, 2022	FL	Tow-Away	0
cr_4390217	Jul 7, 2022	FL	Injury	1
cr_4367881	May 27, 2022	FL	Tow-Away	0
cr_4306080	Feb 10, 2022	FL	Injury	1

Related records

Vehicle

2016 MACK CXU (Pinnacle)

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

Carrier

ENO INC

USDOT 1056669 · 42 crashes · 67 inspections

Vehicle

VIN: 1M1AW02Y4GM054359

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

State

Crashes in Florida

Statewide crash records.

Agency

ENO INC

Crashes reported by this law-enforcement agency.

City

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