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 Bayview (Police District C)

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

SFPD flew 544 operational drone flights to calls in Bayview (Police District C) in the twelve months to Aug 2026, 8% of the 6,464 citywide. That is 8.1 per 1,000 residents, 1.2× the citywide rate, rank 5 of 10 police districts. Several flights can serve one call: these served 325 dispatch events.

Where drones were sent: the intersections with the most operational flights. Each dot is the intersection of a call in Bayview (Police District C) drones were sent to, sized by operational flights, Sep 2025 to Aug 2026.
IntersectionFlights
Colby St & Sweeny St21
Evans Ave & Selby St20
25th St & Dakota St & Texas St16
Ingalls St & Quesada Ave16
Mariposa St & Pennsylvania Ave15
Boutwell St & Industrial St & Loomis St13
3rd St & Davidson Ave12
Bay Shore Blvd & Marengo St9
Cesar Chavez St & Mississippi St9
Lane St & Mckinnon Ave9
3rd St & China Basin St8
Maddux Ave & Topeka Ave8
What the flights were for. Bayview (Police District C), Sep 2025 to Aug 2026: 544 flights to calls here. Gray figures are citywide. Drone sent is the share of all police calls of that type in Bayview (Police District C) that had a flight, shown where there were at least 20 calls.
ReasonFlightsShareCitywide
Criminal Investigation53398%83%
Fire / Mutual Aid71%2%
Major or Critical Incidents41%2%
Call types that got a drone.
Call typeFlightsShareCitywideCallsDrone sent
WANTED VEHICLE / SUB7720%15%5059% (10%)
SUSPICIOUS VEHICLE5916%13%2,1591% (2%)
MISC4512%10%6283% (3%)
BURGLARY328%9%8092% (3%)
SHOT SPOTTER308%—25610% (11%)
ROBBERY277%5%7813% (14%)
PERSON W/GUN267%12%20110% (17%)
SUSPICIOUS PERSON236%11%1,5061% (0%)
ARREST MADE195%5%3216% (8%)
PERSON W/KNIFE144%—1468% (6%)
SHOTS FIRED144%—9911% (7%)
FIGHT NO WEAPON133%4%2,7300% (0%)
The calls that got a drone. Calls in Bayview (Police District C) that got a drone, with the citywide figure beside it.
ShareCalls
Priority A calls60% (citywide 63%)Priority A 194, B 70, C 61
Officer-initiated37% (citywide 32%)Officer on view 120, resident call 205
How calls with a drone ended. Resident calls in Bayview (Police District C) 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 2026270 (0%)0 (0%)0 (0%)
Jun 2026221 (5%)0 (0%)0 (0%)
May 202616000
Apr 2026210 (0%)0 (0%)1 (5%)
Mar 202613002
Feb 2026220 (0%)0 (0%)0 (0%)
Jan 202615000
Dec 202513000
Nov 202510000
Oct 202510001
Sep 20255000
All months since Oct 20242212 (1%)0 (0%)4 (2%)
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