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

San Francisco, California · one day

Monday 28 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.

11 min

median flight. Half were shorter.

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

55 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 service96%
  2. Other4%

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 service7 min03d1421f
—Call for service7 min0ba4b89b
—Call for service14 min0c9f4710
—Call for service10 min0ea2ef08
—Call for service17 min18dc1e95
—Call for service2 min1c1c8950
—Call for service18 min1e40245b
—Call for service6 min20fa3090
—Call for service16 min21043dad
—Call for service11 min242cc747
—Call for service16 min2b0a5e08
—Call for service3 min2dcaafa2
—Call for service11 min32cc555f
—Call for service12 min36cfa9aa
—Call for service7 min3d4c3cee
—Call for service17 min3db5accf
—Call for service13 min44867c24
—Call for service10 min4714cdd1
—Call for service10 min4ec759e6
—Call for service12 min50aadb87
—Call for service12 min5363c4bf
—Other2 min5cda6fd9
—Call for service19 min5e6d8a0e
—Other17 min63d3c4ce
—Call for service10 min66d6cdcc
—Call for service8 min66fe6d0e
—Call for service12 min6cc434c2
—Call for service28 min7180371a
—Call for service12 min72e3ae61
—Call for service11 min75cf0526
—Call for service13 min76a19715
—Call for service4 min81c3e4d2
—Call for service16 min8c01d494
—Call for service10 min9c529327
—Call for service7 min9df8d2bc
—Call for service10 mina63970a4
—Call for service8 minaf2ab2ae
—Call for service6 minb1af24f0
—Call for service10 minb4a8bcca
—Call for service6 minc203b8e0
—Call for service19 minca375832
—Call for service17 mincdd01627
—Call for service18 mind37fcf28
—Call for service8 mind840d9cc
—Call for service3 minda85e7ef
—Call for service14 minddcd3fd5
—Call for service18 mine2147341
—Call for service8 mine2b13f6c
—Call for service4 mine2b53049
—Call for service10 minefd47e2f
—Call for service12 minf2218cd1
—Call for service13 minf305f67c
—Call for service10 minf8eaa238
—Call for service12 minfaba932a
—Call for service30 minff28e132

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.