31
drone flights over Greeley that day.
12:42 am
first takeoff; the last was at 11:49 pm.
11 min
median flight. Half were shorter.
Greeley police drones flew 31 times on Friday 24 July 2026, the first at 12:42 am and the last at 11:49 pm MDT, by Greeley Police Department's published record.
One flight, takeoff to landingSensitive-purpose flight, as an area
Hour by hour
Takeoffs by hour, MDT.
Why, in the agency's words
Flights, in order
31 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) | Purpose | Airborne | Flight |
|---|---|---|---|
| 12:42 am | Call for service | 17 min | 1afced71 |
| 8:25 am | Call for service | 8 min | 5fd68184 |
| 8:30 am | Call for service | 19 min | 8f8f1ee0 |
| 9:53 am | Call for service | 15 min | 92209113 |
| 10:09 am | Call for service | 13 min | 768a86d7 |
| 10:24 am | Call for service | 10 min | 53087a79 |
| 10:34 am | Call for service | 4 min | 6f92912d |
| 12:23 pm | Call for service | 11 min | 8a5152fe |
| 12:57 pm | Call for service | 21 min | 8bea4bb3 |
| 1:18 pm | Call for service | 11 min | 29e8e784 |
| 2:47 pm | Call for service | 11 min | d4b06d8c |
| 3:00 pm | Call for service | 8 min | 9cddd1a5 |
| 3:37 pm | Call for service | 9 min | 52142994 |
| 4:00 pm | Call for service | 14 min | 07833011 |
| 4:42 pm | Call for service | 5 min | 007217d6 |
| 4:58 pm | Call for service | 10 min | d1804b7e |
| 5:26 pm | Call for service | 11 min | d1adaa09 |
| 5:35 pm | Call for service | 16 min | 01c33171 |
| 6:28 pm | Call for service | 21 min | 1c878765 |
| 6:47 pm | Call for service | 7 min | 1d0e0b4c |
| 7:24 pm | Call for service | 16 min | 78d895d2 |
| 8:13 pm | Call for service | 10 min | b454eeb0 |
| 8:37 pm | Call for service | 13 min | 26cf4822 |
| 9:12 pm | Call for service | 14 min | 208f59c6 |
| 9:16 pm | Call for service | 10 s | 5947bc43 |
| 9:24 pm | Call for service | 10 s | 196d5947 |
| 9:35 pm | Call for service | 2 min | f2015ead |
| 9:38 pm | Call for service | 1 min 45 s | 0dbc71cd |
| 9:40 pm | Call for service | 1 min 56 s | 31303e9a |
| 11:11 pm | Call for service | 53 s | c0224f6c |
| 11:49 pm | Call for service | 11 min | ff199d7e |
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).