CityDroneWatch
  1. CityDroneWatch
  2. California
  3. San Francisco
  4. February 2026
  5. 7

San Francisco, California · one day

Saturday 7 February 2026

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

58

drone flights over San Francisco that day.

—

times not published in this record.

13 min

median flight. Half were shorter.

San Francisco police drones flew 58 times on Saturday 7 February 2026, times not published, by San Francisco Police Department's published record.

57 flights with a published block-level point of 58. 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 service91%
  2. Other9%

Flights, in order

58 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 (PST)PurposeAirborneFlight
—Call for service6 min09b70380
—Call for service6 min0ba90877
—Other1 min 00 s15750e19
—Call for service5 min1745588d
—Call for service16 min1a034d8e
—Other12 min1c2fce5f
—Call for service19 min1d46fb42
—Call for service18 min2033eee0
—Call for service23 min2eab52fb
—Call for service17 min330a9698
—Call for service10 min3425dd15
—Call for service8 min3b631630
—Call for service21 min40252d6c
—Call for service2 min50802072
—Call for service16 min5430f852
—Call for service28 min58715a26
—Call for service9 min59c8f04c
—Call for service4 min5bf1b306
—Call for service20 min5e9c6d8b
—Call for service6 min60d50a06
—Call for service8 min650e84af
—Call for service15 min6bc19b66
—Call for service15 min75fc3ff5
—Call for service15 min79c5eede
—Call for service17 min7c562c01
—Call for service15 min8022558a
—Other10 min8225c6a1
—Call for service14 min84dded8d
—Call for service19 min87e9048d
—Call for service13 min89700aa8
—Call for service17 min96370fd6
—Call for service19 mina5da9f6c
—Call for service7 mina742e221
—Call for service18 mina7bf1587
—Call for service3 minadfdc6e6
—Call for service16 minafc4ba5b
—Call for service7 minb4fa6562
—Call for service21 minb5c14331
—Call for service14 minb8aa413e
—Call for service18 minba021686
—Call for service21 minba8dd732
—Call for service11 minbba3e522
—Call for service11 minbe4207aa
—Call for service8 minc21e3151
—Call for service15 minc7f892a9
—Call for service10 minced834f1
—Call for service15 mind5ebc6ff
—Call for service13 mind9284592
—Call for service16 minda88a539
—Call for service10 mindb001dac
—Call for service7 mine3c70468
—Other1 min 00 se3d7a754
—Other1 min 00 se60fb4b4
—Call for service72 minea98d42f
—Call for service2 mineaa820eb
—Call for service9 minf9203e0d
—Call for service10 minfd992d4a
—Call for service13 minff939fd2

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: see the about page. See about this site for the sources and the publication rules.