Fatal crash rate · South Dakota
Fatal crash rate in Hyde County, South Dakota
Fatal crashes recorded by NHTSA in Hyde County, South Dakota, 2020 to 2024, divided by the people who live there. Fatal crashes only: not injuries, not all crashes, not traffic in general.
Hyde County, South Dakota2024 · fatal crashes recorded by NHTSA
82.7fatal crashes per 100,000 residents in 2024
In 2024, NHTSA recorded 1 fatal crash in Hyde County, South Dakota, where 1,209 people lived. That is 82.7 fatal crashes for every 100,000 residents, and 1 person died in those crashes. Over 2020 to 2024 the average was 81.4.
The road is a scale of fatal crashes per 100,000 residents in 2024, 0 to 40. The yellow post is Hyde County; the white posts are South Dakota and the United States.
- Per 100,000
- 1 fatal crashes ÷ 1,209 residents × 100,000 = 82.7
- Five-year
- 2 crashes (2020 to 2024) ÷ 2,457 resident-years × 100,000 = 81.4
- Same year
- South Dakota: 134 ÷ 927,110 = 14.5 · United States: 36,297 ÷ 340,003,797 = 10.7
Every year, 2020 to 2024
| Year | Fatal crashes | Deaths | Population | Per 100,000 |
|---|---|---|---|---|
| 2020 | 1 | 1 | 1,248 | 80.1 |
| 2021 | 0 | 0 | 1,228 | 0.0 |
| 2022 | 0 | 0 | 1,190 | 0.0 |
| 2023 | 0 | 0 | 1,183 | 0.0 |
| 2024 | 1 | 1 | 1,209 | 82.7 |
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 2 fatal crashes NHTSA coded to Hyde County, South Dakota over five years, from the fields FARS records. Nothing is estimated or inferred.
| Road type | Crashes | Share |
|---|---|---|
| Interstate | 0 | 0% |
| Other freeway or expressway | 0 | 0% |
| Other principal arterial | 1 | 50% |
| Minor arterial | 0 | 0% |
| Major collector | 0 | 0% |
| Minor collector | 0 | 0% |
| Local road | 1 | 50% |
| Unknown or not reported | 0 | 0% |
| Rural | 2 | 100% |
| Urban | 0 | 0% |
| Time of day | Crashes | Share |
|---|---|---|
| Midnight to 5:59 am | 0 | 0% |
| 6 am to 11:59 am | 1 | 50% |
| Noon to 5:59 pm | 0 | 0% |
| 6 pm to 11:59 pm | 1 | 50% |
| Hour unknown | 0 | 0% |
| Light | Crashes | Share |
|---|---|---|
| Daylight | 1 | 50% |
| Dark, not lighted (or lighting unknown) | 1 | 50% |
| Dark, lighted | 0 | 0% |
| Dawn or dusk | 0 | 0% |
| Unknown or not reported | 0 | 0% |
| Weather | Crashes | Share |
|---|---|---|
| Clear | 1 | 50% |
| Cloudy | 1 | 50% |
| Rain | 0 | 0% |
| Snow, sleet or freezing rain | 0 | 0% |
| Fog, smog or smoke | 0 | 0% |
| Severe wind, blowing sand or other | 0 | 0% |
| Unknown or not reported | 0 | 0% |
| Involving | Crashes | Share |
|---|---|---|
| A pedestrian | 1 | 50% |
| A bicyclist or other cyclist | 0 | 0% |
| A speeding-related vehicle | 0 | 0% |
| A driver police reported as drinking | 0 | 0% |
| Most-named roads | Crashes |
|---|---|
| US-14 | 1 |
| 337TH AVE | 1 |
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 theFATALSfield. Counties are the FARSSTATEandCOUNTYcodes 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.