CityDroneWatch
  1. CityDroneWatch
  2. Minnesota
  3. Minnetonka
  4. August 2026
  5. 25

Minnetonka, Minnesota · one day

Tuesday 25 August 2026

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

8

drone flights over Minnetonka that day.

8:15 am

first takeoff; the last was at 4:12 pm.

11 min

median flight. Half were shorter.

Minnetonka police drones flew 8 times on Tuesday 25 August 2026, the first at 8:15 am and the last at 4:12 pm CDT, by Minnetonka 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, CDT.

12a1a2a3a4a5a6a7a8a9a10a11a12p1p2p3p4p5p6p7p8p9p10p11p

Why, in the agency's words

  1. Call for service88%
  2. Training and testing12%

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 (CDT)PurposeAirborneFlight
8:15 amCall for service13 min02ee9518
8:55 amCall for service8 min523a647f
1:33 pmCall for service20 min6e98bdaa
1:55 pmCall for service18 min54b6666f
3:17 pmCall for service12 minecbe525b
3:51 pmTraining and testing10 min5e8ee168
4:01 pmCall for service9 min3991d5cf
4:12 pmCall for service7 mind68cc7a5

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