Home / States / North Carolina / Kill Devil Hills Police Department
Kill Devil Hills Police Department
City agency in Dare, North Carolina, United States. Reports crime data to the FBI, and has done since 2019.
- ORI
- NC0280100
- Type
- City
- County
- Dare
- State
- North Carolina (NC)
- FBI reporting
- Reporting since 2019-01-01
- Location
- 35.6063, -75.7675
Workforce
As reported to the FBI for 2025, covering a population of 7,763.
| Year | Officers | Civilians | Population served | Per 1,000 |
|---|---|---|---|---|
| 2025 | 27 | 6 | 7,763 | 4.25 |
| 2024 | 27 | 8 | 7,817 | 4.48 |
| 2023 | 27 | 6 | 7,865 | 4.20 |
| 2022 | 28 | 6 | 7,911 | 4.30 |
| 2021 | 27 | 6 | 7,488 | 4.41 |
| 2020 | 29 | 6 | 7,407 | 4.73 |
| 2019 | 28 | 6 | 7,268 | 4.68 |
| 2018 | 28 | 6 | 7,179 | 4.74 |
| 2017 | 28 | 6 | 7,194 | 4.73 |
| 2016 | 29 | 6 | 7,132 | 4.91 |
| 2015 | 28 | 6 | 6,991 | 4.86 |
| 2014 | 29 | 6 | 6,976 | 5.02 |
Officer and civilian counts are full-time employees as filed by the agency in its annual return. A dash means the agency did not report that figure for that year — it does not mean zero.
Crime and clearances
Offences and clearances filed by Kill Devil Hills Police Department in its monthly returns to the FBI, added up by calendar year, 2019–2026. Violent crime and property crime are the FBI’s two categories. These are the counts as filed: Police Census does not turn them into a rate.
| Year | Months filed | Offences | Cleared | Cleared as % of offences |
|---|---|---|---|---|
| 2026 | Not yet in the FBI’s file | |||
| 2025 | 11 of 12 | 16 | 8 | 50.0% |
| 2024 | 12 | 17 | 9 | 52.9% |
| 2023 | 12 | 31 | 15 | 48.4% |
| 2022 | 12 | 18 | 10 | 55.6% |
| 2021 | 12 | 23 | 9 | 39.1% |
| 2020 | 12 | 17 | 14 | 82.4% |
| 2019 | 12 | 19 | 6 | 31.6% |
| Year | Months filed | Offences | Cleared | Cleared as % of offences |
|---|---|---|---|---|
| 2026 | Not yet in the FBI’s file | |||
| 2025 | 11 of 12 | 146 | 35 | 24.0% |
| 2024 | 12 | 117 | 24 | 20.5% |
| 2023 | 12 | 158 | 35 | 22.2% |
| 2022 | 12 | 216 | 29 | 13.4% |
| 2021 | 12 | 201 | 37 | 18.4% |
| 2020 | 12 | 216 | 35 | 16.2% |
| 2019 | 12 | 282 | 58 | 20.6% |
Reading the table. “Not reported” means the agency filed nothing for that year; it does not mean zero. A 0 is a figure the agency filed. For 2026 the FBI is still collecting: that year is not complete in the file we read, so where this agency has no 2026 figures the table says “Not yet in the FBI’s file” rather than “Not reported”. We can see that the agency is absent from the file so far; we cannot tell whether it has not filed or has not yet been published, and we do not guess. A year marked “7 of 12” adds up only the months the agency filed, so it is not a full-year total. A dash in the last column means the percentage cannot be worked out: it needs both figures, and at least one offence.
“Cleared” is the FBI file’s clearance count for the year. Clearances in a year can relate to offences from earlier years, so the percentage is not the share of that year’s offences that were solved, and it can exceed 100%. Figures are not adjusted: a year far below the agency’s neighbouring years, or a 0 beside many offences, may reflect what was submitted rather than what happened. The file does not say which, and Police Census does not guess.
Source: FBI Crime Data Explorer, summarized data for agency record NC0280100.
Arrests
Arrests made by Kill Devil Hills Police Department, all offences combined, as filed with the FBI and added up by calendar year, 2019–2026.
| Year | Months filed | Arrests |
|---|---|---|
| 2026 | Not yet in the FBI’s file | |
| 2025 | 11 of 12 | 167 |
| 2024 | 12 | 195 |
| 2023 | 12 | 235 |
| 2022 | 12 | 260 |
| 2021 | 12 | 379 |
| 2020 | 12 | 301 |
| 2019 | 12 | 279 |
“Not reported” means the agency filed nothing for that year; it does not mean zero. A year marked “7 of 12” adds up only the months filed. For 2026 the FBI is still collecting, so an absent agency reads “Not yet in the FBI’s file”: absent from the file so far, which is not the same claim as having filed nothing. Source: FBI Crime Data Explorer, arrest data for agency record NC0280100.
Bias-motivated incidents in the FBI’s file
1 incident appears in the FBI’s hate crime file for Kill Devil Hills Police Department for 2025, as at 14 August 2026. The table lists every year from 1991 to 2025 for which the file has at least one.
| Year | Incidents appearing in the file |
|---|---|
| 2025 | 1 |
| 2024 | 2 |
| 2011 | 1 |
| 1995 | 1 |
| Bias motivation | Incidents |
|---|---|
| Anti-Jewish | 3 |
| Anti-Black or African American | 1 |
| Anti-Hispanic or Latino | 1 |
Absence from this file is not a zero. The file lists incidents that were reported to the FBI. An agency can be missing from it because it recorded none, because it did not report, or because it does not take part in the FBI’s hate crime program, and nothing Police Census holds can tell these apart. In any one year the file lists incidents for only a minority of the agencies the FBI counts as reporting.
The figures are counts of incidents as they appear in the file, as at 14 August 2026; Police Census does not turn them into a rate and does not compare them with other agencies. Offence and bias wording is the FBI’s own, unaltered. Source: FBI Crime Data Explorer, additional datasets, hate crime bulk file, agency record NC0280100.
Assaults on officers
Officers of Kill Devil Hills Police Department assaulted in the line of duty, by the weapon reported, between 1995 and 2024. These are the FBI’s own weapon categories.
| Weapon reported | Officers assaulted |
|---|---|
| Firearm | 1 |
| Knife or other cutting instrument | 1 |
| Hands, fists or feet | 87 |
| Other weapon | 5 |
| Year | Firearm | Knife | Hands, fists, feet | Other |
|---|---|---|---|---|
| 1995 | 0 | 1 | 2 | 0 |
| 1996 | 0 | 0 | 1 | 0 |
| 1997 | 0 | 0 | 2 | 1 |
| 1998 | 0 | 0 | 4 | 0 |
| 1999 | 0 | 0 | 3 | 1 |
| 2000 | 0 | 0 | 4 | 0 |
| 2001 | 0 | 0 | 2 | 0 |
| 2002 | 0 | 0 | 2 | 0 |
| 2003 | 0 | 0 | 5 | 0 |
| 2004 | 0 | 0 | 7 | 0 |
| 2005 | 0 | 0 | 6 | 0 |
| 2006 | 0 | 0 | 6 | 0 |
| 2007 | 0 | 0 | 7 | 0 |
| 2008 | 0 | 0 | 4 | 1 |
| 2009 | 0 | 0 | 4 | 0 |
| 2010 | 0 | 0 | 2 | 0 |
| 2011 | 0 | 0 | 6 | 0 |
| 2012 | 1 | 0 | 2 | 1 |
| 2013 | 0 | 0 | 3 | 0 |
| 2014 | 0 | 0 | 5 | 0 |
| 2015 | 0 | 0 | 1 | 0 |
| 2016 | 0 | 0 | 2 | 0 |
| 2017 | 0 | 0 | 2 | 0 |
| 2019 | 0 | 0 | 1 | 0 |
| 2020 | 0 | 0 | 1 | 0 |
| 2021 | 0 | 0 | 1 | 0 |
| 2022 | 0 | 0 | 1 | 0 |
| 2023 | 0 | 0 | 1 | 0 |
| 2024 | 0 | 0 | 0 | 1 |
Why there is no single total here. The FBI publishes two breakdowns of the same assaults — by weapon, and by how the officer was deployed — and nationally they do not agree: the assignment columns sum to 1,869,337 and the weapon columns to 1,744,852, and the two match on only 84% of rows. Police Census publishes the weapon breakdown as the FBI states it rather than picking one basis and calling it ‘the total’. The file’s ‘cleared’ column is not shown either: it sums higher than the assaults themselves, so it is not a subset of what is above and we have not established what it counts.
This comes from the FBI’s Law Enforcement Officers Killed and Assaulted programme. Despite the name, the file carries no officers-killed data at all — those columns are empty for every agency and every year, so this page reports assaults only and says nothing about officers killed.
LEOKA identifies agencies by name, not by the ORI used elsewhere on this site. A row was attached only where exactly one agency in that state reduces to the same base name; 78.7% of rows matched nationwide. An agency with nothing here may have reported no assaults, or may be one of the names that did not match — Police Census does not guess which.
Also policing Dare
Jurisdictions overlap. These agencies are also recorded against the same county, so a single address may be covered by more than one of them.
Source
Agency identity, type, jurisdiction, coordinates and reporting status are as published by the FBI Crime Data Explorer, agency record NC0280100. Police Census reproduces these values without adjustment. Where the FBI publishes nothing, this page says so rather than estimating.
Believe something on this page is wrong? Tell us at corrections@policecensus.com — every correction is published on Corrections.