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

San Francisco, California · one day

Wednesday 30 September 2026

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

48

drone flights over San Francisco that day.

—

times not published in this record.

9 min

median flight. Half were shorter.

San Francisco police drones flew 48 times on Wednesday 30 September 2026, times not published, by San Francisco Police Department's published record.

48 flights with a published block-level point of 48. 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

48 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 service22 min01d98bb1
—Call for service22 min0466bf1a
—Call for service9 min0b75cd6e
—Call for service15 min1497896c
—Call for service3 min15196e56
—Call for service13 min15be7f64
—Call for service18 min17fe50bf
—Call for service9 min1faa1ba5
—Call for service9 min22ebece4
—Call for service9 min28b4763e
—Call for service13 min2b2414b3
—Call for service2 min3378861f
—Call for service9 min3717b202
—Call for service8 min39ffebfd
—Call for service20 min3b041dcf
—Call for service13 min3ce85a97
—Call for service19 min3d6e61b1
—Call for service1 min 00 s42e14bd9
—Call for service6 min455211c3
—Call for service5 min471647e9
—Call for service10 min4a2c0915
—Call for service14 min4d213d0f
—Call for service9 min4e023b81
—Call for service6 min528280f0
—Call for service7 min57328e4a
—Call for service7 min5a386146
—Call for service14 min7028edac
—Call for service10 min7781b2cf
—Call for service11 min7a2a6b67
—Call for service8 min7bfa2dc7
—Call for service10 min843a134d
—Call for service7 min8842179d
—Call for service14 min8b02020c
—Call for service11 mina72c4773
—Call for service6 mina8c50324
—Call for service5 minae64ff7b
—Call for service9 minb59b28f7
—Call for service9 minb7fc6788
—Call for service4 minccc02791
—Call for service4 mincd1fb372
—Call for service7 mind16f0d94
—Call for service8 mindc4af651
—Call for service9 mine2e231a7
—Call for service19 minf0e78e2a
—Call for service2 minf211884e
—Other10 minf62b58de
—Call for service10 minfa9ecabf
—Call for service5 minff315690

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.