CityDroneWatch
  1. CityDroneWatch
  2. California
  3. San Francisco
  4. January 2026
  5. 21

San Francisco, California · one day

Wednesday 21 January 2026

77 drone flights from San Francisco Police Department's published record.

77

drone flights over San Francisco that day.

—

times not published in this record.

13 min

median flight. Half were shorter.

San Francisco police drones flew 77 times on Wednesday 21 January 2026, times not published, by San Francisco Police Department's published record.

73 flights with a published block-level point of 77. The record gives no path.
One flight, at its published block

Hour by hour

Times not published in this record.

Why, in the agency's words

  1. Other84%
  2. Call for service16%

Flights, in order

77 flights. Those in the latest full month link to their own page; a flight with a sensitive stated purpose has no page of its own.

Takeoff (PST)PurposeAirborneFlight
—Call for service30 min03b88f80
—Other14 min0cf3e014
—Other17 min0cfcb8fc
—Other9 min11c167c9
—Other10 min12a600a6
—Other21 min14655d39
—Other10 min1b110722
—Other13 min1d62f71b
—Other10 min2785b84f
—Call for service13 min2d31b50c
—Other14 min332fbcb0
—Other6 min3565670c
—Other28 min37a34787
—Other10 min39aee8d9
—Other18 min39c269e3
—Other5 min42233e1b
—Other5 min456846ea
—Other15 min45f45243
—Other14 min48b0c865
—Call for service14 min4a5ba023
—Other13 min4aedde1d
—Other13 min4b880555
—Other9 min4d1f3974
—Other13 min4d346afc
—Other10 min5a863b7a
—Other10 min5e1b7df2
—Other11 min5f32a953
—Call for service26 min65fa1240
—Other6 min6907d099
—Other19 min6a85502a
—Other13 min6ab8e3c8
—Other5 min6c0f28f3
—Call for service5 min6c6a96b2
—Other10 min6ce0f65d
—Other20 min6eb8b9f0
—Other8 min70ac5c74
—Other6 min71d080d8
—Other7 min77c37229
—Other7 min7e59e528
—Other11 min7e92d704
—Other12 min89d1c810
—Other7 min8bbc8e28
—Other18 min9ab7f002
—Other15 min9aec8113
—Other28 min9ec61c5c
—Other7 min9fbed012
—Other7 mina46d9122
—Other10 mina6eb64c6
—Call for service15 mina8f61cc5
—Other14 minb6097ecb
—Call for service7 minb637f45e
—Other11 minbccebbda
—Other20 minbced50df
—Other20 minbf5a7a24
—Other10 minc10e31e3
—Other3 minc70524cc
—Call for service27 minc7d29e95
—Other5 minc91077d8
—Call for service1549 mincbf3a0cb
—Other13 mince103d84
—Other5 mincf663d99
—Other16 mind4ed645e
—Other30 mind4f074a5
—Other10 mind51c2bd5
—Other15 mind8f99b67
—Call for service27 mind9c5b7e9
—Other14 mindbdbc5f3
—Other13 mindce69726
—Other16 minddcbcdef
—Call for service13 mindfc701b0
—Call for service16 mine451794a
—Other30 mine8f69aba
—Other13 mine962250f
—Other10 mined4d7ed7
—Other20 minf56d73fd
—Other14 minfaabcd7b
—Other30 minff002fcc

How this page is made

  • Every flight in the agency's published record is counted and listed; drawn paths are the whole flight, simplified to 10 m.
  • The record's free-text description is never read into a page. A flight whose stated purpose names a domestic, sexual-assault, kidnapping, welfare, mental-health or juvenile matter is listed like any other but drawn as a generalised area, not a path.
  • Operators are the agency's own accounts in the record, numbered within the agency in order of first flight; no name or address is read into a page.
  • Purposes are the agency's own words, grouped into classes by a committed lookup table; unmatched values are "Other" and blank ones "Not stated".
  • Times are converted to the agency's clock through the IANA zone database, never a fixed offset.
  • A day is the agency's local calendar day of takeoff.

Corrections and questions: see the about page. See about this site for the sources and the publication rules.