CityDroneWatch
  1. CityDroneWatch
  2. Colorado
  3. Arvada
  4. September 2026
  5. 15

Arvada, Colorado · one day

Tuesday 15 September 2026

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

14

drone flights over Arvada that day.

2:37 pm

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

9 min

median flight. Half were shorter.

Arvada police drones flew 14 times on Tuesday 15 September 2026, the first at 2:37 pm and the last at 9:34 pm MDT, by Arvada Police Department's published record.

14 drawable flights of 14. 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. Other29%
  2. Patrol support21%
  3. Traffic and crashes21%
  4. Training and testing14%
  5. Call for service7%
  6. Assisting another agency7%

Flights, in order

14 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
2:37 pmTraining and testing6 min006f51e2
3:17 pmPatrol support10 min4d6d2b7b
3:41 pmOther6 min461bcae3
4:08 pmTraffic and crashes10 minf48232c5
4:19 pmCall for service9 min5bb0a31f
4:29 pmOther10 min8377bac1
4:54 pmOther18 min502a110c
5:46 pmTraffic and crashes9 min4f26d487
6:27 pmAssisting another agency4 minaf6ce1ac
6:37 pmPatrol support4 mina1186f09
7:12 pmTraining and testing45 s0d80a6ba
7:15 pmPatrol support12 minf2415ed4
9:17 pmOther10 min73d492e7
9:34 pmTraffic and crashes4 mind88fbe67

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