SFResponse.org How San Francisco responds

SFPD drone flights

in

Where and why the Police Department flies drones, from its published flight log.

Loading…

SFPD drone flights in Tenderloin (Police District J)

Flights since May 16, 2024; the latest in the city's log is from Aug 31, 2026 · source updated Sep 25, 2026.

SFPD flew 385 operational drone flights to calls in Tenderloin (Police District J) in the twelve months to Aug 2026, 6% of the 6,464 citywide. That is 12.1 per 1,000 residents, 1.8× the citywide rate, rank 2 of 10 police districts. Several flights can serve one call: these served 237 dispatch events.

Where drones were sent: the intersections with the most operational flights. Each dot is the intersection of a call in Tenderloin (Police District J) drones were sent to, sized by operational flights, Sep 2025 to Aug 2026.
IntersectionFlights
Eddy St & Mason St40
Taylor St & Turk St30
Eddy St & Leavenworth St29
Eddy St & Jones St28
Golden Gate Ave & Jones St23
Hyde St & Turk St20
Leavenworth St & Turk St17
Eddy St & Taylor St14
Golden Gate Ave & Leavenworth St12
Ofarrell St & Powell St12
Ellis St & Powell St10
Ada Ct & Ofarrell St9
What the flights were for. Tenderloin (Police District J), Sep 2025 to Aug 2026: 385 flights to calls here. Gray figures are citywide. Drone sent is the share of all police calls of that type in Tenderloin (Police District J) that had a flight, shown where there were at least 20 calls.
ReasonFlightsShareCitywide
Criminal Investigation37096%83%
Major or Critical Incidents92%2%
Fire / Mutual Aid62%2%
Call types that got a drone.
Call typeFlightsShareCitywideCallsDrone sent
PERSON W/GUN4016%12%17315% (17%)
SUSPICIOUS PERSON3614%11%7,8140% (0%)
MISC3213%10%5613% (3%)
SUSPICIOUS VEHICLE2711%13%1,3901% (2%)
WANTED VEHICLE / SUB239%15%2057% (10%)
STRONGARM ROBBERY198%5%8316% (14%)
SHOTS FIRED177%—5711% (7%)
SHOOTING166%—2030% (23%)
AGG ASSAULT / ADW146%—1524% (5%)
FIGHT NO WEAPON114%4%2,4180% (0%)
ASSAULT / BATTERY94%5%8651% (1%)
PERSON W/KNIFE94%—2062% (6%)
The calls that got a drone. Calls in Tenderloin (Police District J) that got a drone, with the citywide figure beside it.
ShareCalls
Priority A calls63% (citywide 63%)Priority A 149, B 36, C 52
Officer-initiated36% (citywide 32%)Officer on view 86, resident call 150
How calls with a drone ended. Resident calls in Tenderloin (Police District J) that got a drone, by the month of the call. SFPD plans a SoMa pilot this fall in which officers watching drone footage decide whether an officer is needed on site (Mission Local). Percentages appear for months with at least 20 calls.
MonthCalls with a droneNo officer on sceneCancelledPriority lowered
Aug 202617000
Jul 202618000
Jun 202610000
May 20268001
Apr 202610000
Mar 20269000
Feb 20269000
Jan 202611000
Dec 20259000
Nov 202518000
Oct 202513000
Sep 20259000
All months since Oct 20241710 (0%)0 (0%)2 (1%)
Police districts ranked by flights per resident. Operational flights per 1,000 residents, Sep 2025 to Aug 2026. Citywide counts the flights to calls with a known location, divided by the whole city's residents.
#Police districtPer 1,000 residents× citywideFlightsDispatch events
Citywide6.71.0×5,530
1Southern (Police District B)21.43.2×1,314858
2Tenderloin (Police District J)12.11.8×385237
3Mission (Police District D)11.71.8×919585
4Central (Police District A)9.11.4×574335
5Bayview (Police District C)8.11.2×544325
6Northern (Police District E)7.21.1×700437
7Richmond (Police District G)3.80.6×311159
8Park (Police District F)3.20.5×196121
9Ingleside (Police District H)2.20.3×300168
10Taraval (Police District I)1.80.3×271166

Method

Source: SFPD Drone Flight Logs (giw5-ttjs on DataSF), one row per flight since May 16, 2024. Flights logged as training or testing are not counted as operational. The log has recorded them only since September 2025. Each flight is placed at the location of its call in the police dispatch data, matched by CAD number, the same way the police page places calls. The log's own location is the general area of the operation and can be a launch site, so it is not used. 85% of operational flights match a dispatch record with a location. The rest count citywide only. A month appears once the city's log covers its last day. The 12-week and 4-week periods end at the latest flight in the log. Until September 2025 the reason for a flight was free text. Since then it is one of a few set categories. Where the log gives an incident report number instead of a CAD number, as it often did before October 2025, the flight is linked through that report's CAD number. For each call type, the share with a drone counts police calls of that original type, minus duplicates but including cancelled calls, that had a flight on the day of the call or the next day. About one linked flight in ten comes later, as a follow-up investigation, and is not counted in that share or in the month-by-month table. Rates divide by the 2020–2024 American Community Survey population. Drones are sent to serious, active incidents, so these calls are not typical police calls. Nothing here is compared with response times.

Every figure here is also in https://sfresponse.org/data/drones.json.

Operational flights per month

Citywide

Where drones were sent

Most flights

What the flights were for

Stated reason

Call type of the linked dispatch

The calls that got a drone

How calls with a drone ended

Neighborhoods ranked by flights per resident