State Route 62 fatal crashes in North Carolina
FARS records 22 fatal crashes with 23 deaths on State Route 62 in North Carolina from 2015 to 2024.
It records no fatal crash on the route in 2024.
By fatal crashes from 2015 to 2024, State Route 62 was number 70 of the 77 routes of North Carolina with a page.
Fatal crashes on State Route 62 fell by 21.4% between the ten years 2005 to 2014 (28) and the ten years 2015 to 2024 (22).
In North Carolina they rose by 9.4% between the same years.
From 2015 to 2024, a speeding-related driver was recorded in 36.4% of fatal crashes on State Route 62 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
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
| Year | Fatal crashes | Deaths |
|---|---|---|
| 2024 | 0 | 0 |
| 2023 | 1 or 2 | 1 or 2 |
| 2022 | 1 or 2 | 1 or 2 |
| 2021 | 7 | 7 |
| 2020 | 3 | 3 |
| 2019 | 4 | 4 |
| 2018 | 1 or 2 | 1 or 2 |
| 2017 | 1 or 2 | 1 or 2 |
| 2016 | 1 or 2 | 1 or 2 |
| 2015 | 1 or 2 | 1 or 2 |
| 2014 | 1 or 2 | 1 or 2 |
| 2013 | 4 | 4 |
| 2012 | 0 | 0 |
| 2011 | 6 | 6 |
| 2010 | 4 | 5 |
| 2009 | 1 or 2 | 1 or 2 |
| 2008 | 1 or 2 | 1 or 2 |
| 2007 | 4 | 6 |
| 2006 | 1 or 2 | 3 |
| 2005 | 3 | 4 |
| 2004 | 3 | 3 |
| 2003 | 1 or 2 | 1 or 2 |
| 2002 | 1 or 2 | 1 or 2 |
| 2001 | 4 | 4 |
| 2000 | 6 | 6 |
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
| County | On the route | On all roads of the county |
|---|---|---|
| Alamance County | 6 | 200 |
| Caswell County | 1 or 2 | 50 |
| Davidson County | 1 or 2 | 282 |
| Guilford County | 10 | 607 |
| Randolph County | 3 | 250 |
Note: the table has the counties where FARS records a fatal crash on the route in these years.
Factors that NHTSA records
| Factor | Count | Counted among | Share | Share on all roads of North Carolina |
|---|---|---|---|---|
| A driver recorded as drinkingof 22 fatal crashes | 5 | 22 fatal crashes | 25.3% | |
| A speeding-related driverof 22 fatal crashes | 8 | 22 fatal crashes | 31.8% | |
| Pedestriansof 23 deaths | 4 | 23 deaths | 14.9% | |
| Motorcyclistsof 23 deaths | 3 | 23 deaths | 13.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.
Time of day
| Time of day | Fatal crashes | Share | Share on all roads of North Carolina |
|---|---|---|---|
| Midnight to 6 a.m. | 3 | 13.6% | 17.4% |
| 6 a.m. to noon | 7 | 31.8% | 20.2% |
| Noon to 6 p.m. | 8 | 36.4% | 29.5% |
| 6 p.m. to midnight | 4 | 18.2% | 32.9% |
Note: the table has the fatal crashes with a known hour.
Mile ranges
| Milepoint | Fatal crashes |
|---|---|
| Mile 0 to 5 | 4 |
| Mile 5 to 10 | 5 |
| Mile 10 to 15 | 1 or 2 |
| Mile 15 to 20 | 3 |
| Mile 20 to 25 | 1 or 2 |
Note: the table has the six ranges of five miles with the largest counts, in the order of the milepoint. 72.7 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.
Official channels
- NHTSA Fatality and Injury Reporting System Tool (FIRST)NHTSA's query tool for FARS counts.
- NHTSA FARS EncyclopediaNHTSA's tables of FARS data.
- North Carolina Governor's Highway Safety ProgramThe highway safety office of North Carolina.
These links go to the sites of the agencies. They were checked on .
Cite this page
Fatal Roads. State Route 62 fatal crashes in North Carolina. https://fatalroads.com/route/nc/sr-62/. 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 State Route 62 in the ten years before 2015?
FARS records 28 fatal crashes on State Route 62 in North Carolina from 2005 to 2014. It records 22 from 2015 to 2024.
What part of the fatal crashes in North Carolina was on State Route 62?
22 of the 14,061 fatal crashes in North Carolina from 2015 to 2024 were on State Route 62. That is 0.2 percent.
How many fatal crashes on State Route 62 had a driver recorded as drinking?
FARS records a driver as drinking in 5 of 22 fatal crashes from 2015 to 2024. It records a speeding-related driver in 8 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 State Route 62 in North Carolina only. The route in a different state has its own page.