CityDroneWatch
  1. CityDroneWatch
  2. California
  3. San Francisco
  4. August 2026
  5. 2

San Francisco, California · one day

Sunday 2 August 2026

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

15

drone flights over San Francisco that day.

—

times not published in this record.

12 min

median flight. Half were shorter.

San Francisco police drones flew 15 times on Sunday 2 August 2026, times not published, by San Francisco Police Department's published record.

10 flights with a published block-level point of 15. 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 service100%

Flights, in order

15 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 min0fc9d187
—Call for service16 min3b3f38bf
—Call for service6 min59cc8435
—Call for service13 min5af2759e
—Call for service13 min68babbb6
—Call for service5 min77333194
—Call for service16 min849fdcbf
—Call for service17 min84ad73b8
—Call for service12 min9cefd04c
—Call for service8 min9f861801
—Call for service1 min 00 scf7309f2
—Call for service16 mine766c83d
—Call for service12 minee9009c0
—Call for service10 minfabdb106
—Call for service9 minfe71e05e

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: file an issue in the korvid-labs repository (demo).