CityDroneWatch
  1. CityDroneWatch
  2. Colorado
  3. Aurora
  4. April 2026
  5. 1

Aurora, Colorado · one day

Wednesday 1 April 2026

21 drone flights from Aurora Police Department's published record.

21

drone flights over Aurora that day.

8:06 am

first takeoff; the last was at 8:30 pm.

14 min

median flight. Half were shorter.

Aurora police drones flew 21 times on Wednesday 1 April 2026, the first at 8:06 am and the last at 8:30 pm MDT, by Aurora Police Department's published record.

21 drawable flights of 21. 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. Not stated52%
  2. Other48%

Flights, in order

21 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:06 amOther20 minAUPD-260
8:30 amOther3 minAUPD-260
9:04 amNot stated14 minAUPD-260
9:44 amNot stated18 minAUPD-260
11:20 amNot stated26 minAUPD-260
11:59 amOther1 min 24 sAUPD-260
12:09 pmOther18 minAUPD-260
12:40 pmNot stated1 min 24 sAUPD-260
1:02 pmOther10 minAUPD-260
1:36 pmNot stated17 minAUPD-260
1:54 pmOther7 minAUPD-260
2:17 pmNot stated6 minAUPD-260
2:56 pmNot stated19 minAUPD-260
3:37 pmOther14 minAUPD-260
3:55 pmNot stated1 min 18 sAUPD-260
3:58 pmNot stated14 minAUPD-260
4:32 pmOther12 minAUPD-260
4:33 pmNot stated18 minAUPD-260
5:56 pmOther24 minAUPD-260
7:41 pmOther27 minAUPD-260
8:30 pmNot stated4 minAUPD-260

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