Crash Record KY0072914150

FMCSA crash record in CRESTWOOD on Jun 22, 2023.

Tow-Away Federal Recordable

What happened

On June 22, 2023, FMCSA recorded a tow-away crash with no reported injuries in CRESTWOOD, Kentucky. The vehicle was operated by STONEY CREEK LOGISTICS INC (USDOT 1774073). Recorded conditions: 1 / 1 / 1 pavement. FMCSA reference KY0072914150.

Geographic note

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

Fatalities
0
Injuries
0
Vehicles
3
Carrier
STONEY CREEK LOGISTICS INC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
3
0 injury · 3 tow-away
Crashes per 100 power units (24 mo)
0.0
0 crashes · 17 units
Days since prior carrier crash
138
Last on Feb 4, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 312,693 carriers

Geographic context

How this crash sits in its setting.

Within CRESTWOOD, Kentucky, 38 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 #:
KY0072914150
Date:
Jun 22, 2023
Time:
1814
State:
Kentucky
City:
CRESTWOOD
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
3

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
2 7 13 3AKJGLD58GSHA7438 RC01669 (MI) STONEY CREEK LOGISTICS 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_4508557 Feb 4, 2023 MI Tow-Away 0 0
cr_4459153 Nov 17, 2022 KY Tow-Away 0 0
cr_4160765 May 26, 2021 MI Tow-Away 0 0
cr_4144378 Apr 25, 2021 KY Tow-Away 0 0
cr_4118300 Jan 24, 2021 MI Tow-Away 0 0
cr_4006163 Jul 16, 2020 OH Injury 0 1
cr_3791058 May 2, 2019 MI Tow-Away 0 0
cr_3675199 Oct 11, 2018 NC Tow-Away 0 0
cr_3616954 Jun 29, 2018 KY Tow-Away 0 0
cr_3482395 Oct 29, 2017 TN Tow-Away 0 0

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.