Fatal RoadsSearch

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

US Route 258 fatal crashes in North Carolina

FARS records 64 fatal crashes with 69 deaths on US Route 258 in North Carolina from 2015 to 2024.

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

By fatal crashes from 2015 to 2024, US Route 258 was number 30 of the 77 routes of North Carolina with a page.

Fatal crashes on US Route 258 rose by 3.2% between the ten years 2005 to 2014 (62) and the ten years 2015 to 2024 (64).

In North Carolina they rose by 9.4% between the same years.

From 2015 to 2024, a speeding-related driver was recorded in 26.6% of fatal crashes on US Route 258 and 31.8% in North Carolina.

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 258 in North Carolina 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 258 in North Carolina: fatal crashes and deaths by year, 2000 to 2024
YearFatal crashesDeaths
202455
202388
202244
2021810
202088
201944
2018910
201756
201655
201589
201469
201378
201233
201144
201057
200956
2008810
200756
20061010
2005913
200433
200345
200289
200178
200044

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 258: fatal crashes on the route in each county, 2015 to 2024, in name order
CountyOn the routeOn all roads of the county
Edgecombe County4104
Greene County335
Halifax County1 or 2137
Hertford County1 or 254
Jones County1 or 225
Lenoir County10118
Northampton County566
Onslow County29219
Pitt County7241
Surry County1 or 2133

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 258 in North Carolina: counts by recorded factor, 2015 to 2024
FactorCountCounted amongShareShare on all roads of North Carolina
A driver recorded as drinkingof 64 fatal crashes1364 fatal crashes25.3%
A speeding-related driverof 64 fatal crashes1764 fatal crashes31.8%
Pedestriansof 69 deaths769 deaths14.9%
Motorcyclistsof 69 deaths1169 deaths13.5%

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 258 in North Carolina: fatal crashes by time of day, 2015 to 2024
Time of dayFatal crashesShareShare on all roads of North Carolina
Midnight to 6 a.m.1218.8%17.4%
6 a.m. to noon1117.2%20.2%
Noon to 6 p.m.2234.4%29.5%
6 p.m. to midnight1929.7%32.9%

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

Mile ranges

Table 5.US Route 258 in North Carolina: fatal crashes by range of five miles, 2015 to 2024
MilepointFatal crashes
Mile 0 to 519
Mile 5 to 108
Mile 10 to 156
Mile 15 to 206
Mile 20 to 251 or 2
Mile 25 to 301 or 2

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

Official channels

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

Cite this page

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

FARS records 62 fatal crashes on US Route 258 in North Carolina from 2005 to 2014. It records 64 from 2015 to 2024.

What part of the fatal crashes in North Carolina was on US Route 258?

64 of the 14,061 fatal crashes in North Carolina from 2015 to 2024 were on US Route 258. That is 0.5 percent.

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

FARS records a driver as drinking in 13 of 64 fatal crashes from 2015 to 2024. It records a speeding-related driver in 17 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 258 in North Carolina only. The route in a different state has its own page.