Fatal crash rate in Floyd County, Indiana
Fatal crashes recorded by NHTSA in Floyd County, Indiana, 2020 to 2024, divided by the people who live there. Fatal crashes only: not injuries, not all crashes, not traffic in general.
Floyd County, Indiana2024 · fatal crashes recorded by NHTSA
6.1fatal crashes per 100,000 residents in 2024
In 2024, NHTSA recorded 5 fatal crashes in Floyd County, Indiana, where 81,799 people lived. That is 6.1 fatal crashes for every 100,000 residents, and 6 people died in those crashes. Over 2020 to 2024 the average was 8.4.
The road is a scale of fatal crashes per 100,000 residents in 2024, 0 to 40. The yellow post is Floyd County; the white posts are Indiana and the United States.
- Per 100,000
- 5 fatal crashes ÷ 81,799 residents × 100,000 = 6.1
- Five-year
- 34 crashes (2020 to 2024) ÷ 404,157 resident-years × 100,000 = 8.4
- Same year
- Indiana: 785 ÷ 6,934,754 = 11.3 · United States: 36,297 ÷ 340,003,797 = 10.7
Every year, 2020 to 2024
| Year | Fatal crashes | Deaths | Population | Per 100,000 |
|---|---|---|---|---|
| 2020 | 5 | 7 | 80,519 | 6.2 |
| 2021 | 6 | 6 | 80,490 | 7.5 |
| 2022 | 11 | 11 | 80,552 | 13.7 |
| 2023 | 7 | 7 | 80,797 | 8.7 |
| 2024 | 5 | 6 | 81,799 | 6.1 |
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 34 fatal crashes NHTSA coded to Floyd County, Indiana over five years, from the fields FARS records. Nothing is estimated or inferred.
| Road type | Crashes | Share |
|---|---|---|
| Interstate | 7 | 21% |
| Other freeway or expressway | 0 | 0% |
| Other principal arterial | 1 | 3% |
| Minor arterial | 12 | 35% |
| Major collector | 9 | 26% |
| Minor collector | 0 | 0% |
| Local road | 5 | 15% |
| Unknown or not reported | 0 | 0% |
| Rural | 15 | 44% |
| Urban | 19 | 56% |
| Time of day | Crashes | Share |
|---|---|---|
| Midnight to 5:59 am | 7 | 21% |
| 6 am to 11:59 am | 12 | 35% |
| Noon to 5:59 pm | 9 | 26% |
| 6 pm to 11:59 pm | 6 | 18% |
| Hour unknown | 0 | 0% |
| Light | Crashes | Share |
|---|---|---|
| Daylight | 16 | 47% |
| Dark, not lighted (or lighting unknown) | 13 | 38% |
| Dark, lighted | 1 | 3% |
| Dawn or dusk | 4 | 12% |
| Unknown or not reported | 0 | 0% |
| Weather | Crashes | Share |
|---|---|---|
| Clear | 24 | 71% |
| Cloudy | 8 | 24% |
| Rain | 1 | 3% |
| Snow, sleet or freezing rain | 1 | 3% |
| 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 | 4 | 12% |
| A bicyclist or other cyclist | 1 | 3% |
| A speeding-related vehicle | 8 | 24% |
| A driver police reported as drinking | 4 | 12% |
| Most-named roads | Crashes |
|---|---|
| I-64 | 4 |
| I-265 | 2 |
| STATE ST | 2 |
| SR-64 | 2 |
| SR-62 | 2 |
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.