CityDroneWatch
  1. CityDroneWatch
  2. California
  3. Concord
  4. July 2026
  5. 1

Concord, California · one day

Wednesday 1 July 2026

15 drone flights from Concord Police Department's published record.

15

drone flights over Concord that day.

9:41 am

first takeoff; the last was at 9:59 pm.

9 min

median flight. Half were shorter.

Concord police drones flew 15 times on Wednesday 1 July 2026, the first at 9:41 am and the last at 9:59 pm PDT, by Concord Police Department's published record.

15 drawable flights of 15. Each path is the whole flight, simplified; a flight with a sensitive stated purpose is drawn as an area.
One flight, takeoff to landingSensitive-purpose flight, as an area

Hour by hour

Takeoffs by hour, PDT.

12a1a2a3a4a5a6a7a8a9a10a11a12p1p2p3p4p5p6p7p8p9p10p11p

Why, in the agency's words

  1. Call for service60%
  2. Traffic and crashes27%
  3. Search7%
  4. Events7%

Flights, in order

15 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
9:41 amCall for service1 min 47 s26047867
11:26 amCall for service14 min92535361
11:38 amCall for service4 minff12b6bf
11:44 amTraffic and crashes11 min70644df3
12:19 pmSearch8 min19986a48
4:05 pmCall for service19 minc0cbbe8f
4:46 pmCall for service8 minc3678b34
7:46 pmCall for service4 min0cf63046
7:56 pmTraffic and crashes6 minf76d79a4
8:23 pmCall for service14 min61efd240
8:43 pmEvents9 min1fb83bc2
9:27 pmCall for service7 min19d9851d
9:27 pmCall for service9 min9fccdaed
9:48 pmTraffic and crashes10 minf6645a13
9:59 pmTraffic and crashes13 min439c9a32

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