Skip to main content
TruckCodex
Hubs

Crash Record FL2668337604

FMCSA crash record in VENICE on Nov 1, 2024.

Injury Federal Recordable

What happened

On November 1, 2024, FMCSA recorded an injury crash with one person hurt in VENICE, Florida. The vehicle was operated by RUSH TRUCK LEASING INC (USDOT 333690). Recorded conditions: 2 / 1 / 1 pavement. Reported by RUSH TRUCK LEASING INC, FMCSA reference FL2668337604.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
2
Carrier
RUSH TRUCK LEASING INC
USDOT 333690
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
53
1 fatal · 18 injury
Crashes per 100 power units (24 mo)
0.6
45 crashes · 7,074 units
Days since prior carrier crash
9
Last on Oct 23, 2024
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,864 carriers

Geographic context

How this crash sits in its setting.

Within VENICE, Florida, 11 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
2
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 #:
FL2668337604
Date:
Nov 1, 2024
Time:
0651
State:
Florida
City:
VENICE
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
RUSH TRUCK LEASING INC (333690)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 5 1XPCDP9X2LD732281 NFRX12 (FL) RUSH TRUCK LEASING 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 Fatalities Injuries
cr_5122536 Mar 18, 2026 DC Tow-Away 0 0
cr_5119955 Mar 12, 2026 WY Injury 0 1
cr_5115292 Feb 23, 2026 TX Tow-Away 0 0
cr_5117019 Feb 20, 2026 NV Tow-Away 0 0
cr_5088027 Dec 29, 2025 TX Injury 0 1
cr_5090757 Dec 9, 2025 FL Injury 0 1
cr_5073138 Dec 2, 2025 WV Tow-Away 0 0
cr_5069852 Nov 29, 2025 NC Tow-Away 0 0
cr_5076216 Nov 26, 2025 OH Tow-Away 0 0
cr_5067681 Nov 13, 2025 IL Tow-Away 0 0

Carrier booking & risk tools

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

Book / don't book Insurance check Cancel desk Chameleon check Safety benchmark

Related records

Carrier
RUSH TRUCK LEASING INC
USDOT 333690 · 348 crashes · 401 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 1XPCDP9X2LD732281
Decode this VIN for make, model, year, and recall data.
State
Crashes in Florida
Statewide crash records.
Agency
RUSH TRUCK LEASING INC
Crashes reported by this law-enforcement agency.
City
Crashes in VENICE, 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.