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

San Francisco, California · one day

Friday 28 August 2026

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

18

drone flights over San Francisco that day.

—

times not published in this record.

14 min

median flight. Half were shorter.

San Francisco police drones flew 18 times on Friday 28 August 2026, times not published, by San Francisco Police Department's published record.

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

18 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 service19 min01dd230f
—Call for service10 min03bf1f91
—Call for service13 min077c3dfc
—Call for service12 min2563ac3b
—Call for service12 min25fdfcb0
—Call for service19 min2e075b68
—Call for service6 min41d207fb
—Other1 min 00 s47a0ce9c
—Call for service15 min4ccbe275
—Call for service21 min4d3d774a
—Call for service20 min79255352
—Call for service16 minabff342a
—Call for service15 minc1fd7e1c
—Call for service18 mincacec51f
—Call for service19 minea5c3f92
—Call for service8 minea5d5f45
—Call for service10 minecf79603
—Call for service7 minf8eeae25

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