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

San Francisco, California · one day

Monday 3 August 2026

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

16

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 16 times on Monday 3 August 2026, times not published, by San Francisco Police Department's published record.

12 flights with a published block-level point of 16. 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 service94%
  2. Other6%

Flights, in order

16 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 service11 min06e90b7a
—Call for service11 min0990cad7
—Call for service3 min0b0b139e
—Call for service5 min221b10cd
—Call for service16 min2275fa36
—Call for service11 min26e50b1b
—Call for service5 min2b14fc2a
—Call for service10 min3174460a
—Call for service5 min3569ad53
—Call for service6 min42510996
—Other10 min666d70e2
—Call for service3 min7e153af7
—Call for service8 mina60d12d8
—Call for service14 minbcf1788a
—Call for service5 mincdbeaceb
—Call for service17 minf3f3b20c

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