CityDroneWatch
  1. CityDroneWatch
  2. Colorado
  3. Greeley
  4. April 2026
  5. 8

Greeley, Colorado · one day

Wednesday 8 April 2026

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

16

drone flights over Greeley that day.

12:12 am

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

12 min

median flight. Half were shorter.

Greeley police drones flew 16 times on Wednesday 8 April 2026, the first at 12:12 am and the last at 11:34 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
12:12 amCall for service2 min8a8baa85
12:24 amCall for service13 min3b11ea46
7:50 amCall for service12 min37226117
8:38 amCall for service18 mindbb16cdd
9:39 amCall for service18 min629f8f5f
10:03 amCall for service16 minc6c29e08
11:13 amCall for service17 min719a8c01
4:13 pmCall for service17 min9f399f5f
4:50 pmCall for service9 minb913430d
5:11 pmCall for service12 mindf887269
6:01 pmCall for service4 minc7aad53c
6:33 pmCall for service11 min582c676c
10:44 pmCall for service8 minf5837f4f
10:58 pmCall for service8 min5ad6d24f
11:14 pmCall for service14 minb1adce08
11:34 pmCall for service17 mind8a75a35

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