CrashRate

Fatal crash rate · Oregon

Fatal crash rate in Gilliam County, Oregon

Fatal crashes recorded by NHTSA in Gilliam County, Oregon, 2020 to 2024, divided by the people who live there. Fatal crashes only: not injuries, not all crashes, not traffic in general.

Gilliam County, Oregon2024 · fatal crashes recorded by NHTSA

50.4fatal crashes per 100,000 residents in 2024

In 2024, NHTSA recorded 1 fatal crash in Gilliam County, Oregon, where 1,984 people lived. That is 50.4 fatal crashes for every 100,000 residents, and 1 person died in those crashes. Over 2020 to 2024 the average was 74.6.

The road is a scale of fatal crashes per 100,000 residents in 2024, 0 to 40. The yellow post is Gilliam County; the white posts are Oregon and the United States.

Small population. Gilliam County has 1,984 residents, so one crash moves the rate by 50.4 points and a single bad year can double it. Read the five-year average and the count, not the one-year rate alone.
Per 100,000
1 fatal crashes ÷ 1,984 residents × 100,000 = 50.4
Five-year
6 crashes (2020 to 2024) ÷ 8,043 resident-years × 100,000 = 74.6
Same year
Oregon: 491 ÷ 4,265,324 = 11.5 · United States: 36,297 ÷ 340,003,797 = 10.7

Every year, 2020 to 2024

YearFatal crashesDeathsPopulationPer 100,000
2020222,01499.3
2021002,0100.0
2022222,01299.4
2023112,03349.2
2024111,98450.4

2024 is NHTSA’s Annual Report File and will be revised when the final file replaces it. Populations are July 1 estimates, Census Vintage 2025.

What the record says about those crashes, 2020 to 2024

Every figure is a count of the 6 fatal crashes NHTSA coded to Gilliam County, Oregon over five years, from the fields FARS records. Nothing is estimated or inferred.

Road typeCrashesShare
Interstate233%
Other freeway or expressway00%
Other principal arterial00%
Minor arterial350%
Major collector00%
Minor collector00%
Local road117%
Unknown or not reported00%
Rural6100%
Urban00%
Time of dayCrashesShare
Midnight to 5:59 am00%
6 am to 11:59 am117%
Noon to 5:59 pm233%
6 pm to 11:59 pm350%
Hour unknown00%
LightCrashesShare
Daylight350%
Dark, not lighted (or lighting unknown)350%
Dark, lighted00%
Dawn or dusk00%
Unknown or not reported00%
WeatherCrashesShare
Clear233%
Cloudy350%
Rain117%
Snow, sleet or freezing rain00%
Fog, smog or smoke00%
Severe wind, blowing sand or other00%
Unknown or not reported00%
InvolvingCrashesShare
A pedestrian00%
A bicyclist or other cyclist00%
A speeding-related vehicle117%
A driver police reported as drinking233%
Most-named roadsCrashes
SR-19 ODOT 53
I-842
CR-SNIPTION CANYON LN1

Road type is FARS FUNC_SYS; speeding is any vehicle coded SPEEDREL 2 to 5; drinking is any driver coded DRINKING = 1 (police-reported, not a blood-alcohol test). Road names are the trafficway strings as the police coded them, counted as written, so the same road can appear under two spellings.

How this is counted

  • Fatal crashes are rows in NHTSA’s Fatality Analysis Reporting System (FARS) file FARS2024NationalCSV.zip, accident.csv, one row per crash on a public road in which someone died within 30 days. Deaths are the FATALS field. Counties are the FARS STATE and COUNTY codes joined to Census FIPS codes.
  • Population is the Census Bureau’s July 1 estimate for the same year, county totals, Vintage 2025. Rate per 100,000 = crashes ÷ population × 100,000.
  • The five-year average is total crashes over the years with both inputs ÷ total population over those years × 100,000, the rolling form in 23 CFR 490.207.
  • What it cannot say. FARS has no injury-only or property-damage crashes, no congestion, and nothing about any one driver, trip or road’s risk. A crash is counted where it happened, not where the people lived. Rates are not ranked here; comparing two places means comparing both sets of inputs.

Informational only, not professional advice. Last reviewed: October 2026. Data snapshot built 2026-10-28.