Skip to main content
TruckCodex
Hubs

Crash Record KY0073001550

FMCSA crash record in LOUISVILLE on Jan 27, 2024.

Tow-Away Federal Recordable

What happened

On January 27, 2024, FMCSA recorded a tow-away crash with no reported injuries in LOUISVILLE, Kentucky. The vehicle was operated by FEDEX FREIGHT INC (USDOT 239039). Recorded conditions: 2 / 1 / 1 pavement. Reported by FEDEX FREIGHT, FMCSA reference KY0073001550.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
FEDEX FREIGHT INC
USDOT 239039
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
794
30 fatal · 254 injury
Crashes per 100 power units (24 mo)
2.7
469 crashes · 17,633 units
Days since prior carrier crash
1
Last on Jan 26, 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 LOUISVILLE, Kentucky, 697 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 #:
KY0073001550
Date:
Jan 27, 2024
Time:
0310
State:
Kentucky
City:
LOUISVILLE
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
FEDEX FREIGHT INC (239039)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 10 3 1XPBA48X7PD877682 3509578 (KY) FEDEX FREIGHT 3 Yes

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
cmu507cc5000ppmto8ikxr4ca Sep 9, 2026 KY Injury 0 2
cmtgtnbz9001zpmmoal2fv4et Aug 26, 2026 PA Tow-Away 0 0
cmsw88sju00l1pev3ndvovb0h Aug 6, 2026 KY Tow-Away 0 0
cmqvwanqb000rp8iu8r2r96dl Jun 22, 2026 AZ Injury 0 2
cmq0fazcw003jpmw8b2frpcvi May 27, 2026 KY Tow-Away 0 0
cmpqehz12000vqiysev1c23b2 May 23, 2026 NC Tow-Away 0 0
cmp0olg5i000nnuqwp1a692zk May 6, 2026 TN Tow-Away 0 0
cmogoa8io006jnvt8c1z52yl8 Apr 21, 2026 TN Tow-Away 0 0
cmo6itlu400oqo1aujr86f1rh Apr 9, 2026 VA Tow-Away 0 0
cmny3yfoo002ik38vzcv0psxm Apr 7, 2026 NC Injury 0 4

Carrier booking & risk tools

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

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

Related records

Vehicle
2023 PETERBILT 579
NHTSA recalls and complaints for this make/model/year.
Recall
25V181000
ELECTRICAL SYSTEM
Recall
24V915000
ELECTRICAL SYSTEM
Recall
24V190000
POWER TRAIN:AUTOMATIC TRANSMISSION:LEVER AND LINKAGE:COLUMN SHIFT
Carrier
FEDEX FREIGHT INC
USDOT 239039 · 9,458 crashes · 10,325 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 1XPBA48X7PD877682
Decode this VIN for make, model, year, and recall data.
State
Crashes in Kentucky
Statewide crash records.
Agency
FEDEX FREIGHT
Crashes reported by this law-enforcement agency.
City
Crashes in LOUISVILLE, KY
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.