TruckCodex
Hubs

Crash Record CT2300440339

FMCSA crash record in CHESHIRE on Nov 6, 2023.

Tow-Away Federal Recordable

What happened

On November 6, 2023, FMCSA recorded a tow-away crash with no reported injuries in CHESHIRE, Connecticut. The vehicle was operated by PENSKE LOGISTICS LLC (USDOT 268015). Recorded conditions: 1 / 1 / 1 pavement. FMCSA reference CT2300440339.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
PENSKE LOGISTICS LLC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
469
18 fatal · 143 injury
Crashes per 100 power units (24 mo)
5.7
355 crashes · 6,237 units
Days since prior carrier crash
1
Last on Nov 5, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,848 carriers

Geographic context

How this crash sits in its setting.

Within CHESHIRE, Connecticut, 34 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 #:
CT2300440339
Date:
Nov 6, 2023
Time:
1302
State:
Connecticut
City:
CHESHIRE
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
PENSKE LOGISTICS LLC (268015)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
2 9 98 3AKBHKDV4KSLG2510 2810190 (IN) PENSKE LOGISTICS 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
cmsw88s1x001vpev3pclexq94 Aug 10, 2026 NC Tow-Away 0 0
cmp0olg760029nuqwoh65ea37 May 5, 2026 KY Tow-Away 0 0
cmny3yfo10020k38vupf79475 Apr 7, 2026 KY Injury 0 1
cr_5126769 Mar 28, 2026 NC Tow-Away 0 0
cr_5123021 Mar 18, 2026 MN Tow-Away 0 0
cr_5124761 Mar 17, 2026 KY Tow-Away 0 0
cr_5122029 Mar 16, 2026 MN Tow-Away 0 0
cr_5121906 Mar 16, 2026 PA Injury 0 1
cr_5126774 Mar 16, 2026 OH Tow-Away 0 0
cr_5123967 Mar 12, 2026 WY Tow-Away 0 0

Related records

Carrier
PENSKE LOGISTICS LLC
USDOT 268015 · 3,080 crashes · 9,828 inspections
Vehicle
VIN: 3AKBHKDV4KSLG2510
Decode this VIN for make, model, year, and recall data.
State
Crashes in Connecticut
Statewide crash records.
City
Crashes in CHESHIRE, CT
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.