Fatal RoadsSearch

Edition: FARS 2024, annual fileNHTSA released it on Release dates

US Route 31 fatal crashes in Kentucky

FARS records 108 fatal crashes with 121 deaths on US Route 31 in Kentucky from 2015 to 2024.

In 2024 it records 1 or 2 fatal crashes with 1 or 2 deaths on the route.

By fatal crashes from 2015 to 2024, US Route 31 was number 10 of the 62 routes of Kentucky with a page.

Fatal crashes on US Route 31 rose by 369.6% between the ten years 2005 to 2014 (23) and the ten years 2015 to 2024 (108).

In Kentucky they fell by 2.6% between the same years.

From 2015 to 2024, pedestrians were 21.5% of the deaths on US Route 31 and 11.1% in Kentucky.

To qualify as a FARS case, the crash had to involve a motor vehicle traveling on a trafficway customarily open to the public and must have resulted in the death of a motorist or a non-motorist within 30 days of the crash.

The set of first files, known as the Annual Report File (ARF), is released following the crash year. The ARF is replaced about a year later with a final file, which contains additional cases or updates to cases that had become available after the ARF was released.

NHTSA's words. Source: NHTSA, Fatality Analysis Reporting System Analytical User's Manual, 1975-2024 (DOT HS 813 794, April 2026), copied on .

This page rests on the FARS 2024 annual file. NHTSA released it on . NHTSA can revise the counts in the final file. Release dates

Figure 1.Fatal crashes on US Route 31 in Kentucky by year, 2015 to 2024

Table 1 has the numbers. Go to the table

Since the last update: no figure of this route has a change on record.

Fatal crashes by year

Table 1.US Route 31 in Kentucky: fatal crashes and deaths by year, 2000 to 2024
YearFatal crashesDeaths
20241 or 21 or 2
20232425
20222225
20212526
20201215
20191821
201834
20171 or 23
20161 or 21 or 2
201500
201400
201333
201299
20111 or 21 or 2
20101 or 21 or 2
20091 or 21 or 2
200833
200733
20061 or 21 or 2
20051 or 21 or 2
200400
20031 or 21 or 2
200233
200100
200000

Note: the route is the trafficway that FARS records for the crash. The records of routes start in 2000. A count of 1 or 2 is written "1 or 2".

Counties on the route

Table 2.US Route 31: fatal crashes on the route in each county, 2015 to 2024, in name order
CountyOn the routeOn all roads of the county
Allen County349
Barren County689
Bullitt County1 or 2112
Edmonson County1 or 221
Hardin County14182
Hart County1 or 250
Jefferson County621,039
Larue County335
Meade County471
Nelson County5100
Simpson County1 or 242
Spencer County1 or 223
Warren County4161

Note: the table has the counties where FARS records a fatal crash on the route in these years.

Factors that NHTSA records

Table 3.US Route 31 in Kentucky: counts by recorded factor, 2015 to 2024
FactorCountCounted amongShareShare on all roads of Kentucky
A driver recorded as drinkingof 108 fatal crashes24108 fatal crashes25.3%
A speeding-related driverof 108 fatal crashes20108 fatal crashes16.2%
Pedestriansof 121 deaths26121 deaths11.1%
Motorcyclistsof 121 deaths15121 deaths13.1%

Note: FARS records a driver as drinking when police reported alcohol involvement or a test of the driver was positive for alcohol. It is not NHTSA's alcohol-impaired measure. One crash can be in two rows. NHTSA's definitions

Note that alcohol data is often missing. For that reason, this data element may under-count the actual number of drinking drivers.

NHTSA's words. Source: NHTSA, Fatality Analysis Reporting System Analytical User's Manual, 1975-2024 (DOT HS 813 794, April 2026), copied on .

Time of day

Table 4.US Route 31 in Kentucky: fatal crashes by time of day, 2015 to 2024
Time of dayFatal crashesShareShare on all roads of Kentucky
Midnight to 6 a.m.1816.7%15.7%
6 a.m. to noon2018.5%21.0%
Noon to 6 p.m.3128.7%34.1%
6 p.m. to midnight3936.1%29.2%

Note: the table has the fatal crashes with a known hour.

Mile ranges

Table 5.US Route 31 in Kentucky: fatal crashes by range of five miles, 2015 to 2024
MilepointFatal crashes
Mile 0 to 535
Mile 5 to 1022
Mile 10 to 1518
Mile 15 to 2013
Mile 20 to 259
Mile 25 to 305

Note: the table has the six ranges of five miles with the largest counts, in the order of the milepoint. 96.3 percent of the fatal crashes on the route have a milepoint in FARS. A state can start its milepoints again at a county line.

Routes in the same counties

These routes of Kentucky have a fatal crash on record in one or more of the same counties. The list is for navigation. The number is the fatal crashes on the route from 2015 to 2024.

All routes in Kentucky

Official channels

These links go to the sites of the agencies. They were checked on .

Cite this page

Fatal Roads. US Route 31 fatal crashes in Kentucky. https://fatalroads.com/route/ky/us-31/. Source: National Highway Traffic Safety Administration, Fatality Analysis Reporting System, FARS 2024 annual file. Data to .

The address of this page does not change.

Source of the figures

Counts: National Highway Traffic Safety Administration, Fatality Analysis Reporting System, national files of 2000 to 2024. A route page is built for a signed Interstate, US or state route with 20 or more fatal crashes in a state in ten years. Data to . The figures are totals. No page of this site is about one crash or one person.

How the figures are made. Data sources and licences. Corrections.

Questions

How many fatal crashes did FARS record on US Route 31 in the ten years before 2015?

FARS records 23 fatal crashes on US Route 31 in Kentucky from 2005 to 2014. It records 108 from 2015 to 2024.

What part of the fatal crashes in Kentucky was on US Route 31?

108 of the 7,075 fatal crashes in Kentucky from 2015 to 2024 were on US Route 31. That is 1.5 percent.

How many fatal crashes on US Route 31 had a driver recorded as drinking?

FARS records a driver as drinking in 24 of 108 fatal crashes from 2015 to 2024. It records a speeding-related driver in 20 of them.

Does this page count the same route number in a different state?

No. This page counts the fatal crashes that FARS records on US Route 31 in Kentucky only. The route in a different state has its own page.