Fatal RoadsSearch

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

US Route 51 fatal crashes in Tennessee

FARS records 137 fatal crashes with 142 deaths on US Route 51 in Tennessee from 2015 to 2024.

In 2024 it records 16 fatal crashes with 17 deaths on the route.

By fatal crashes from 2015 to 2024, US Route 51 was number 8 of the 84 routes of Tennessee with a page.

From 2015 to 2024, pedestrians were 28.9% of the deaths on US Route 51 and 13.0% in Tennessee.

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 51 in Tennessee 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

The counts of some years are not complete. In the years 2000 to 2011, FARS wrote the US routes of Tennessee with state route numbers, for example "US-SR 1". This site cannot assign these crashes to this route, so the counts of those years are too low. This site does not guess a US route from a state route number.

Table 1.US Route 51 in Tennessee: fatal crashes and deaths by year, 2000 to 2024
YearFatal crashesDeaths
20241617
20231212
20221919
20211819
20201416
201988
20181920
201788
20161010
20151313
201478
20131011
20121416
201100
201000
200900
200800
200700
200600
200500
200400
200300
200200
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 51: fatal crashes on the route in each county, 2015 to 2024, in name order
CountyOn the routeOn all roads of the county
Dyer County1070
Lauderdale County1554
Obion County945
Shelby County871,755
Tipton County1668

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 51 in Tennessee: counts by recorded factor, 2015 to 2024
FactorCountCounted amongShareShare on all roads of Tennessee
A driver recorded as drinkingof 137 fatal crashes22137 fatal crashes24.5%
A speeding-related driverof 137 fatal crashes11137 fatal crashes16.5%
Pedestriansof 142 deaths41142 deaths13.0%
Motorcyclistsof 142 deaths17142 deaths13.8%

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 51 in Tennessee: fatal crashes by time of day, 2015 to 2024
Time of dayFatal crashesShareShare on all roads of Tennessee
Midnight to 6 a.m.2820.6%17.1%
6 a.m. to noon2518.4%18.7%
Noon to 6 p.m.3727.2%31.8%
6 p.m. to midnight4633.8%32.4%

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

Mile ranges

Table 5.US Route 51 in Tennessee: fatal crashes by range of five miles, 2015 to 2024
MilepointFatal crashes
Mile 0 to 529
Mile 5 to 1024
Mile 10 to 1520
Mile 15 to 2030
Mile 20 to 2524
Mile 25 to 307

Note: the table has the six ranges of five miles with the largest counts, in the order of the milepoint. 100 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 Tennessee 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 Tennessee

Official channels

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

Cite this page

Fatal Roads. US Route 51 fatal crashes in Tennessee. https://fatalroads.com/route/tn/us-51/. 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 51 in the ten years before 2015?

FARS records 31 fatal crashes on US Route 51 in Tennessee from 2005 to 2014. It records 137 from 2015 to 2024. The figures of 2005 to 2011 are not complete. This site makes no comparison of the two periods.

What part of the fatal crashes in Tennessee was on US Route 51?

137 of the 10,680 fatal crashes in Tennessee from 2015 to 2024 were on US Route 51. That is 1.3 percent.

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

FARS records a driver as drinking in 22 of 137 fatal crashes from 2015 to 2024. It records a speeding-related driver in 11 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 51 in Tennessee only. The route in a different state has its own page.