Skip to main content
TruckCodex
Hubs

Crash Record KY0071693564

FMCSA crash record in Kentucky on Nov 9, 2015.

Injury

What happened

On November 9, 2015, FMCSA recorded an injury crash with 2 people hurt in Kentucky. The vehicle was operated by WILSON HAULING INC (USDOT 508388). FMCSA reference KY0071693564.

Fatalities
0
Injuries
2
Vehicles
—
Carrier
USDOT 508388
Vehicle Type
—
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
2
2 injury · 2 tow-away
Crashes per 100 power units (24 mo)
6.7
1 crashes · 15 units
Days since prior carrier crash
151
Last on Jun 11, 2015
Vs fleet-size peers
above the median
Cohort median 0.0 · 315,143 carriers

Geographic context

How this crash sits in its setting.

Within Kentucky, 5,047 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

Crash details

Key facts from the FMCSA crash record.

Report #:
KY0071693564
Date:
Nov 9, 2015
Time:
0950
State:
Kentucky
Fatalities:
0
Injuries:
2
Tow-Away:
Yes
HazMat:
No
Carrier (USDOT):
WILSON HAULING INC (508388)

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5080011 Dec 21, 2025 OH Injury 0 1
cr_4641361 Oct 20, 2023 KY Tow-Away 0 0
cr_4529911 Mar 6, 2023 IN Tow-Away 0 0
cr_3904632 Dec 17, 2019 OH Tow-Away 0 0
cr_3873994 Oct 30, 2019 KY Tow-Away 0 0
cr_3820001 Jun 18, 2019 OH Injury 0 1
cr_3840877 Jun 3, 2019 OH Tow-Away 0 0
cr_3809775 Mar 11, 2019 OH Tow-Away 0 0
cr_3809716 Feb 8, 2019 OH Injury 0 1
cr_3135332 Dec 7, 2015 OH Tow-Away 0 0

Carrier booking & risk tools

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

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.