What Durham Residents Can Verify Before 911 Drone Flights

Durham residents can read published police drone rules and see the council’s vote on surveillance safeguards. The new 911 program’s dispatch rules, executed contract and operating controls remain unverified in the records reviewed.

Editorial illustration of a drone above a docking station.
Editorial illustration of a drone above a docking station.

Durham residents can read the police department’s published drone rules and see the City Council’s June vote on surveillance safeguards. Before Durham starts sending docked drones to 911 calls, residents still need a program-specific account of which calls qualify, who can see the footage, and how the city will check compliance. Police General Order 3008 and June 15 council record.

Durham police told WRAL in early November that planning was in its early stages and that the department could give no launch timetable. WRAL reported two acquired drones that were still out of use. In the records reviewed through November 4, the executed contract and procedures for the new 911 program remained unverified. WRAL’s November 2 report and the agenda contract copy.

What Durham has put in writing

General Order 3008, dated January 2, 2025, directs deployment requests to the pilot in command, who decides whether the mission can fly legally and safely. Pilots must document flights and denials. The order directs investigators to obtain a warrant before flights when there are reasonable grounds to expect evidence of criminal wrongdoing or an intrusion on reasonable expectations of privacy. It sets a minimum of 30 calendar days for collected media that is not attached to an incident report. It also permits some sharing of live footage during a mission. The order says the pilot in command must be positioned to see the aircraft during flights, a provision Durham should explain in the context of remote dispatch. General Order 3008, pages 5–9.

The council’s June 15 agenda records a 7–0 vote to adopt a surveillance resolution. Both posted versions call for auditable access to drone footage, limits on third-party use of city data to improve AI models, and publication of departmental policies and retention links. The revised copy shows tracked changes. The records reviewed did not include a clean adopted copy that resolves the wording changes. Council vote and original and revised resolution attachments.

The council had already authorized the city manager to execute an Axon agreement of up to $16.1 million on June 1. The authorization covers a broader police technology bundle that includes cameras, Tasers and drones. The agenda copy has blank signature fields, so it leaves the final terms and any amendments open. June 1 authorization and agenda contract, pages 5 and 54–56.

What faster response would mean

WRAL’s November 3 follow-up points to randomized trials in Philadelphia and Montgomery County, Maryland. The preprint reports that in Montgomery County, the researchers estimated that median first arrival across eligible calls was 0.72 minutes sooner on days randomly assigned to drone operations than on days assigned to patrol only. Philadelphia measured a different result: calls assigned to drone response closed 14.5 minutes sooner on average. Its estimate for travel from dispatch to arrival was inconclusive, and many arrival timestamps were missing. These results give Durham measures to track locally, including when a call arrives, when the first responder reaches the scene and when the call closes. WRAL’s follow-up and the two-trial preprint.

Before launch, Durham should publish the rules for dispatch from docks and explain which parts of the general order carry over. The city can also explain who can view and export video, how long each class of footage stays in storage, and who reviews access logs. Once flights start, aggregate reports could show what triggered launches, how often drones arrived first, and how often ground responders still had to go. Those records would let residents evaluate response and oversight without releasing incident footage.

Respond to this post

See something missing, disputed, or worth following? Send a private response to the editor. Nothing will appear publicly without permission.

Permissions

Your email remains private. CAPTCHA verification is required before WordPress accepts the response.