US Route 12 fatal crashes in Washington
FARS records 83 fatal crashes with 93 deaths on US Route 12 in Washington from 2015 to 2024.
In 2024 it records 9 fatal crashes with 9 deaths on the route.
By fatal crashes from 2015 to 2024, US Route 12 was number 7 of the 29 routes of Washington with a page.
Fatal crashes on US Route 12 fell by 7.8% between the ten years 2005 to 2014 (90) and the ten years 2015 to 2024 (83).
In Washington they rose by 23.3% between the same years.
From 2015 to 2024, a speeding-related driver was recorded in 15.7% of fatal crashes on US Route 12 and 31.1% in Washington.
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 | 9 | 9 |
| 2023 | 10 | 11 |
| 2022 | 9 | 9 |
| 2021 | 9 | 10 |
| 2020 | 6 | 6 |
| 2019 | 13 | 14 |
| 2018 | 4 | 6 |
| 2017 | 10 | 13 |
| 2016 | 7 | 8 |
| 2015 | 6 | 7 |
| 2014 | 5 | 6 |
| 2013 | 5 | 5 |
| 2012 | 8 | 9 |
| 2011 | 5 | 8 |
| 2010 | 7 | 8 |
| 2009 | 13 | 16 |
| 2008 | 13 | 15 |
| 2007 | 18 | 20 |
| 2006 | 4 | 4 |
| 2005 | 12 | 17 |
| 2004 | 11 | 15 |
| 2003 | 11 | 12 |
| 2002 | 10 | 12 |
| 2001 | 8 | 10 |
| 2000 | 7 | 8 |
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 |
|---|---|---|
| Asotin County | 1 or 2 | 13 |
| Columbia County | 1 or 2 | 4 |
| Franklin County | 1 or 2 | 73 |
| Garfield County | 6 | 8 |
| Grays Harbor County | 13 | 86 |
| Lewis County | 17 | 105 |
| Spokane County | 1 or 2 | 417 |
| Thurston County | 10 | 207 |
| Walla Walla County | 15 | 48 |
| Yakima County | 17 | 356 |
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 Washington |
|---|---|---|---|---|
| A driver recorded as drinkingof 83 fatal crashes | 22 | 83 fatal crashes | 31.1% | |
| A speeding-related driverof 83 fatal crashes | 13 | 83 fatal crashes | 31.1% | |
| Pedestriansof 93 deaths | 5 | 93 deaths | 18.4% | |
| Motorcyclistsof 93 deaths | 17 | 93 deaths | 15.7% |
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 Washington |
|---|---|---|---|
| Midnight to 6 a.m. | 14 | 16.9% | 19.9% |
| 6 a.m. to noon | 13 | 15.7% | 17.7% |
| Noon to 6 p.m. | 33 | 39.8% | 29.9% |
| 6 p.m. to midnight | 23 | 27.7% | 32.5% |
Note: the table has the fatal crashes with a known hour.
Mile ranges
| Milepoint | Fatal crashes |
|---|---|
| Mile 10 to 15 | 3 |
| Mile 35 to 40 | 3 |
| Mile 40 to 45 | 7 |
| Mile 140 to 145 | 3 |
| Mile 195 to 200 | 5 |
| Mile 340 to 345 | 4 |
Note: the table has the six ranges of five miles with the largest counts, in the order of the milepoint. 96.4 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 Washington 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.
- Washington Traffic Safety CommissionThe highway safety office of Washington.
These links go to the sites of the agencies. They were checked on .
Cite this page
Fatal Roads. US Route 12 fatal crashes in Washington. https://fatalroads.com/route/wa/us-12/. 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 12 in the ten years before 2015?
FARS records 90 fatal crashes on US Route 12 in Washington from 2005 to 2014. It records 83 from 2015 to 2024.
What part of the fatal crashes in Washington was on US Route 12?
83 of the 5,793 fatal crashes in Washington from 2015 to 2024 were on US Route 12. That is 1.4 percent.
How many fatal crashes on US Route 12 had a driver recorded as drinking?
FARS records a driver as drinking in 22 of 83 fatal crashes from 2015 to 2024. It records a speeding-related driver in 13 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 12 in Washington only. The route in a different state has its own page.