CityDroneWatch
  1. CityDroneWatch
  2. Colorado
  3. Aurora
  4. May 2026
  5. 28

Aurora, Colorado · one day

Thursday 28 May 2026

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

20

drone flights over Aurora that day.

12:38 am

first takeoff; the last was at 11:57 pm.

16 min

median flight. Half were shorter.

Aurora police drones flew 20 times on Thursday 28 May 2026, the first at 12:38 am and the last at 11:57 pm MDT, by Aurora Police Department's published record.

20 drawable flights of 20. 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 stated70%
  2. Other15%
  3. Call for service15%

Flights, in order

20 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
12:38 amOther13 minAUPD-260
8:31 amNot stated6 minAUPD-260
8:38 amNot stated19 minAUPD-260
9:22 amCall for service28 minAUPD-260
9:27 amNot stated20 minAUPD-260
10:16 amNot stated18 minAUPD-260
10:24 amOther14 minAUPD-260
11:05 amNot stated17 minAUPD-260
11:49 amNot stated18 minAUPD-260
11:52 amNot stated4 minAUPD-260
3:23 pmNot stated15 minAUPD-260
4:08 pmNot stated2 minAUPD-260
4:11 pmNot stated1 min 30 sAUPD-260
4:14 pmNot stated20 minAUPD-260
4:43 pmNot stated4 minAUPD-260
5:15 pmCall for service26 minAUPD-260
5:35 pmOther8 minAUPD-260
6:48 pmCall for service11 minAUPD-260
8:26 pmNot stated25 minAUPD-260
11:57 pmNot stated19 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).