CityDroneWatch
  1. CityDroneWatch
  2. Colorado
  3. Greeley
  4. June 2026
  5. 22

Greeley, Colorado · one day

Monday 22 June 2026

17 drone flights from Greeley Police Department's published record.

17

drone flights over Greeley that day.

9:20 am

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

12 min

median flight. Half were shorter.

Greeley police drones flew 17 times on Monday 22 June 2026, the first at 9:20 am and the last at 11:43 pm MDT, by Greeley Police Department's published record.

17 drawable flights of 17. 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. Call for service100%

Flights, in order

17 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
9:20 amCall for service3 mind6f90c84
11:19 amCall for service16 mindd70bc19
11:59 amCall for service9 min92521a5f
12:10 pmCall for service5 min95a2f784
12:46 pmCall for service7 min9ae620b5
1:07 pmCall for service12 mine7aa1bb5
3:14 pmCall for service17 min8423f092
3:40 pmCall for service19 minfa1746f8
4:26 pmCall for service10 min761e85de
5:41 pmCall for service17 minfa43b6ad
6:29 pmCall for service8 min5e516ad3
6:41 pmCall for service11 minb86a3272
8:27 pmCall for service9 mina1d2225e
9:38 pmCall for service19 min9baaf69f
10:27 pmCall for service13 minf85fb3ba
11:19 pmCall for service17 mind48ad56b
11:43 pmCall for service13 min182a576b

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