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

San Francisco, California · one day

Sunday 21 June 2026

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

14

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 14 times on Sunday 21 June 2026, times not published, by San Francisco Police Department's published record.

13 flights with a published block-level point of 14. 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 service86%
  2. Other14%

Flights, in order

14 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 service8 min174f743b
—Call for service11 min31468bef
—Call for service4 min472ae2ad
—Other10 min48e5b5db
—Call for service8 min4a61966e
—Call for service7 min550a288f
—Call for service7 min82bc5387
—Call for service18 minac6904ab
—Call for service11 minb39cba95
—Call for service9 minc58c3777
—Call for service9 minea531fac
—Other12 minf2617db2
—Call for service8 minf5395714
—Call for service10 minfc0a80eb

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).