Skip to main content
TruckCodex
Hubs

Crash Record KY0073244498

FMCSA crash record in LEXINGTON on Oct 14, 2025.

Tow-Away Federal Recordable

What happened

On October 14, 2025, FMCSA recorded a tow-away crash with no reported injuries in LEXINGTON, Kentucky. The vehicle was operated by MURROW'S TRANSFER INC (USDOT 90840). Recorded conditions: 1 / 1 / 1 pavement. Reported by MURROW'S TRANSFER INC, FMCSA reference KY0073244498.

Carrier pattern note

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

Geographic note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
USDOT 90840
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
20
1 fatal · 9 injury
Crashes per 100 power units (24 mo)
7.1
10 crashes · 140 units
Days since prior carrier crash
14
Last on Sep 30, 2025
Vs fleet-size peers
above the median
Cohort median 0.0 · 27,367 carriers

Geographic context

How this crash sits in its setting.

Within LEXINGTON, Kentucky, 306 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 #:
KY0073244498
Date:
Oct 14, 2025
Time:
1041
State:
Kentucky
City:
LEXINGTON
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 7 3 1FUJGLD5XFLGE3896 NL5534 (NC) MURROW'S TRANSFER 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
cmrzwwgqk000bpe21ex1jqv18 Jul 20, 2026 NC Tow-Away 0 0
cr_5125769 Mar 25, 2026 KY Tow-Away 0 0
cr_5118470 Mar 10, 2026 SC Tow-Away 0 0
cr_5058262 Sep 30, 2025 NC Tow-Away 0 0
cr_5091501 Jul 28, 2025 NC Tow-Away 0 0
cr_4934568 Apr 21, 2025 NC Tow-Away 0 0
cr_4896952 Feb 11, 2025 VA Injury 0 1
cr_4843291 Nov 15, 2024 NC Injury 0 1
cr_4842859 Nov 7, 2024 AL Tow-Away 0 0
cr_4826347 Oct 17, 2024 TN Injury 0 1

Carrier booking & risk tools

Check booking and risk signals for USDOT 90840 — 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.