CityDroneWatch
  1. CityDroneWatch
  2. Colorado
  3. Arvada
  4. July 2026
  5. 3

Arvada, Colorado · one day

Friday 3 July 2026

19 drone flights from Arvada Police Department's published record.

19

drone flights over Arvada that day.

8:16 am

first takeoff; the last was at 10:15 pm.

10 min

median flight. Half were shorter.

Arvada police drones flew 19 times on Friday 3 July 2026, the first at 8:16 am and the last at 10:15 pm MDT, by Arvada Police Department's published record.

19 drawable flights of 19. 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, MDT.

12a1a2a3a4a5a6a7a8a9a10a11a12p1p2p3p4p5p6p7p8p9p10p11p

Why, in the agency's words

  1. Events37%
  2. Other32%
  3. Call for service21%
  4. Search5%
  5. Training and testing5%

Flights, in order

19 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 (MDT)PurposeAirborneFlight
8:16 amSearch4 min4a34cba4
8:22 amTraining and testing8 min4baca652
12:08 pmOther50 s34d407aa
3:00 pmOther7 min82bb81c3
3:37 pmOther18 min2ab2469f
4:07 pmOther13 min18e84fc5
5:33 pmCall for service16 min7a468e51
6:21 pmCall for service10 min032bfc47
6:33 pmOther5 mind559aa5d
6:41 pmCall for service15 min0d0d781b
7:24 pmEvents11 min7cc567d5
7:33 pmOther7 min2378a40a
8:30 pmEvents9 mincdd48ff7
8:42 pmCall for service11 minb1457724
9:06 pmEvents9 min6dcba952
9:25 pmEvents17 min8afcb5d8
9:43 pmEvents11 mind908369e
10:06 pmEvents6 min7964ab26
10:15 pmEvents10 min09881e78

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