CityDroneWatch
  1. CityDroneWatch
  2. California
  3. San Francisco
  4. September 2026
  5. 29

San Francisco, California · one day

Tuesday 29 September 2026

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

55

drone flights over San Francisco that day.

—

times not published in this record.

10 min

median flight. Half were shorter.

San Francisco police drones flew 55 times on Tuesday 29 September 2026, times not published, by San Francisco Police Department's published record.

52 flights with a published block-level point of 55. 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. Call for service98%
  2. Other2%

Flights, in order

55 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 (PDT)PurposeAirborneFlight
—Call for service5 min04a3fe04
—Call for service15 min054a2926
—Call for service7 min086f2957
—Call for service23 min093852bd
—Call for service12 min0d943621
—Call for service15 min14d1147d
—Call for service18 min194c4d67
—Call for service17 min1e3234e1
—Call for service8 min1e84610e
—Call for service7 min251dbfec
—Call for service14 min28e45776
—Call for service12 min302868f2
—Call for service7 min35373ae0
—Call for service7 min3a0386f3
—Call for service2 min3a138d11
—Call for service19 min3ec098c4
—Call for service6 min3f500256
—Call for service19 min4325e2eb
—Call for service9 min45d9a392
—Call for service10 min4858a4c3
—Call for service3 min4d7ee01a
—Call for service14 min5e77c7e5
—Call for service7 min685bb965
—Call for service16 min6990701b
—Call for service2 min6dd7e71a
—Call for service15 min6e52bcfd
—Other16 min6ed00a86
—Call for service5 min79796172
—Call for service16 min7fcedc8c
—Call for service7 min816295fd
—Call for service17 min83535996
—Call for service13 min83d20150
—Call for service7 min8667366f
—Call for service24 min91321561
—Call for service9 min979706b0
—Call for service12 min99c5fbd0
—Call for service16 mina58e2a69
—Call for service13 mina660c6e7
—Call for service10 mina72b1859
—Call for service8 minb3bb7962
—Call for service15 minbc5918b9
—Call for service6 minbe497b71
—Call for service12 minc0634ed9
—Call for service7 minc2506593
—Call for service5 minc45702e5
—Call for service6 mind58ee04f
—Call for service2 mindc4dbe48
—Call for service10 mine0eaf729
—Call for service5 mine39cd99f
—Call for service22 mine4e560b0
—Call for service9 minec05edde
—Call for service5 minee859fbb
—Call for service11 minef921b14
—Call for service17 minf7443f24
—Call for service14 minf9e46758

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.