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

San Francisco, California · one day

Saturday 4 July 2026

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

59

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 59 times on Saturday 4 July 2026, times not published, by San Francisco Police Department's published record.

56 flights with a published block-level point of 59. 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 service97%
  2. Other3%

Flights, in order

59 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 service180 min0121718d
—Call for service16 min031a2ac5
—Call for service13 min03d90091
—Call for service20 min06ea9b3b
—Call for service5 min0780b6e5
—Call for service17 min091d44c1
—Call for service13 min14e00126
—Call for service11 min17538f32
—Call for service17 min19fe37f6
—Call for service20 min2115f652
—Call for service14 min26ba7f02
—Call for service4 min2dada705
—Call for service19 min3483387c
—Call for service13 min37940731
—Call for service16 min3cf4336b
—Call for service13 min3f6aa6db
—Call for service17 min4549cb3a
—Call for service8 min4567d48d
—Call for service15 min47db7a44
—Call for service2 min4f2f6ece
—Call for service19 min5424f033
—Call for service13 min5cbb9454
—Call for service7 min5e0ba89c
—Call for service16 min5eed81d0
—Call for service24 min65e74f71
—Call for service15 min66f898b6
—Call for service5 min69de1252
—Call for service17 min7271d410
—Call for service12 min72cce815
—Call for service20 min739abace
—Other8 min75e6afab
—Call for service5 min79f0e10d
—Call for service12 min7d1a7a8e
—Call for service15 min7f65febf
—Call for service26 min89b758b1
—Call for service13 min8cb80707
—Call for service23 min939cf14d
—Call for service200 min93dc471b
—Call for service17 min9b1f0eb7
—Call for service12 mina1fbec8c
—Call for service19 mina5188bc1
—Other24 mina65cbd56
—Call for service22 minab21d768
—Call for service12 minbb30586f
—Call for service10 minc028f1bc
—Call for service14 minc153ed3f
—Call for service6 minc4f06099
—Call for service8 mind5ea29b2
—Call for service7 mind5f52ada
—Call for service11 mine2c84276
—Call for service4 mine44d5987
—Call for service16 mine6626368
—Call for service10 mine752bf50
—Call for service19 minea46e141
—Call for service14 minec9254b5
—Call for service11 minf1fd40b8
—Call for service13 minfb2a835d
—Call for service3 minfbcf7e8b
—Call for service20 minfc18539a

How this page is made

  • Every flight in the agency's published record is counted and listed; drawn paths are the whole flight, takeoff to landing.
  • 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 fixed list of terms; unmatched values are "Other" and blank ones "Not stated".
  • Times are shown on the agency's own local clock.
  • 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.