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

Greeley, Colorado · one day

Friday 26 June 2026

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

16

drone flights over Greeley that day.

5:44 am

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

14 min

median flight. Half were shorter.

Greeley police drones flew 16 times on Friday 26 June 2026, the first at 5:44 am and the last at 11:52 pm MDT, by Greeley Police Department's published record.

16 drawable flights of 16. 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

16 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
5:44 amCall for service19 min70517f94
7:33 amCall for service16 mindf03de51
8:55 amCall for service15 min8fe30779
10:44 amCall for service14 mine56860f2
11:43 amCall for service15 min81d7bc60
12:17 pmCall for service9 min597a1a9d
1:12 pmCall for service20 minc5a7ad31
2:26 pmCall for service14 min19db8acc
2:54 pmCall for service17 min2ae3c2c5
3:34 pmCall for service14 minfcd09b6e
7:19 pmCall for service10 minb4cfc17c
9:10 pmCall for service11 min9c31c8cf
10:23 pmCall for service16 mine25b636e
10:41 pmCall for service16 min40a60359
11:49 pmCall for service13 min718f7046
11:52 pmCall for service13 mind3192296

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