CityDroneWatch
  1. CityDroneWatch
  2. Colorado
  3. Durango
  4. August 2026
  5. 5

Durango, Colorado · one day

Wednesday 5 August 2026

8 drone flights from Durango Police Department's published record.

8

drone flights over Durango that day.

2:01 pm

first takeoff; the last was at 8:59 pm.

10 min

median flight. Half were shorter.

Durango police drones flew 8 times on Wednesday 5 August 2026, the first at 2:01 pm and the last at 8:59 pm MDT, by Durango Police Department's published record.

8 drawable flights of 8. 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. Patrol support100%

Flights, in order

8 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
2:01 pmPatrol support16 minef3b76b9
4:41 pmPatrol support9 min8e497617
5:56 pmPatrol support19 mined90aead
7:05 pmPatrol support5 min7f434087
7:16 pmPatrol support11 min270c2e6c
7:30 pmPatrol support15 mindddb427f
8:33 pmPatrol support6 mina0f43045
8:59 pmPatrol support8 mind1433163

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