US Route 33 fatal crashes in West Virginia
FARS records 57 fatal crashes with 61 deaths on US Route 33 in West Virginia 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 33 was number 9 of the 23 routes of West Virginia with a page.
Fatal crashes on US Route 33 fell by 17.4% between the ten years 2005 to 2014 (69) and the ten years 2015 to 2024 (57).
In West Virginia they fell by 22.2% between the same years.
From 2015 to 2024, a driver was recorded as drinking in 19.3% of fatal crashes on US Route 33 and 27.2% in West Virginia.
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 | 1 or 2 | 1 or 2 |
| 2023 | 6 | 6 |
| 2022 | 1 or 2 | 1 or 2 |
| 2021 | 5 | 5 |
| 2020 | 3 | 4 |
| 2019 | 9 | 11 |
| 2018 | 4 | 5 |
| 2017 | 7 | 7 |
| 2016 | 10 | 10 |
| 2015 | 9 | 9 |
| 2014 | 3 | 3 |
| 2013 | 7 | 7 |
| 2012 | 6 | 7 |
| 2011 | 7 | 7 |
| 2010 | 6 | 6 |
| 2009 | 4 | 6 |
| 2008 | 8 | 8 |
| 2007 | 12 | 12 |
| 2006 | 8 | 8 |
| 2005 | 8 | 8 |
| 2004 | 8 | 9 |
| 2003 | 5 | 5 |
| 2002 | 10 | 11 |
| 2001 | 9 | 9 |
| 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 |
|---|---|---|
| Barbour County | 1 or 2 | 28 |
| Gilmer County | 3 | 12 |
| Jackson County | 4 | 57 |
| Lewis County | 10 | 39 |
| Pendleton County | 7 | 18 |
| Randolph County | 12 | 45 |
| Roane County | 8 | 30 |
| Upshur County | 11 | 36 |
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 West Virginia |
|---|---|---|---|---|
| A driver recorded as drinkingof 57 fatal crashes | 11 | 57 fatal crashes | 27.2% | |
| A speeding-related driverof 57 fatal crashes | 11 | 57 fatal crashes | 26.7% | |
| Pedestriansof 61 deaths | 1 or 2 | 61 deaths | 8.7% | |
| Motorcyclistsof 61 deaths | 3 | 61 deaths | 12.4% |
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 West Virginia |
|---|---|---|---|
| Midnight to 6 a.m. | 7 | 12.3% | 15.4% |
| 6 a.m. to noon | 15 | 26.3% | 20.7% |
| Noon to 6 p.m. | 22 | 38.6% | 35.2% |
| 6 p.m. to midnight | 13 | 22.8% | 28.6% |
Note: the table has the fatal crashes with a known hour.
Mile ranges
| Milepoint | Fatal crashes |
|---|---|
| Mile 0 to 5 | 8 |
| Mile 5 to 10 | 16 |
| Mile 10 to 15 | 12 |
| Mile 15 to 20 | 8 |
| Mile 20 to 25 | 4 |
| Mile 30 to 35 | 3 |
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 West Virginia 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.
- Governors Highway Safety Association: State Highway Safety OfficesThe list of the highway safety offices of the states.
These links go to the sites of the agencies. They were checked on .
Cite this page
Fatal Roads. US Route 33 fatal crashes in West Virginia. https://fatalroads.com/route/wv/us-33/. 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 33 in the ten years before 2015?
FARS records 69 fatal crashes on US Route 33 in West Virginia from 2005 to 2014. It records 57 from 2015 to 2024.
What part of the fatal crashes in West Virginia was on US Route 33?
57 of the 2,517 fatal crashes in West Virginia from 2015 to 2024 were on US Route 33. That is 2.3 percent.
How many fatal crashes on US Route 33 had a driver recorded as drinking?
FARS records a driver as drinking in 11 of 57 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 33 in West Virginia only. The route in a different state has its own page.