CityDroneWatch
  1. CityDroneWatch
  2. Minnesota
  3. Rochester
  4. October 2026
  5. 7

Rochester, Minnesota · one day

Wednesday 7 October 2026

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

16

drone flights over Rochester that day.

12:15 am

first takeoff; the last was at 10:27 pm.

8 min

median flight. Half were shorter.

Rochester police drones flew 16 times on Wednesday 7 October 2026, the first at 12:15 am and the last at 10:27 pm CDT, by Rochester 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, CDT.

12a1a2a3a4a5a6a7a8a9a10a11a12p1p2p3p4p5p6p7p8p9p10p11p

Why, in the agency's words

  1. Call for service56%
  2. Events31%
  3. Other6%
  4. Training and testing6%

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 (CDT)PurposeAirborneFlight
12:15 amEvents17 min2973eabc
1:38 amEvents4 min614e70d6
1:48 amEvents12 minb1d46932
2:38 amEvents10 minf84d6a6a
1:03 pmEvents19 min9e7f80bf
2:02 pmCall for service7 min2afffab9
3:37 pmCall for service8 min2291a36e
4:00 pmCall for service6 min025967b2
7:11 pmCall for service3 min6cd8ff99
7:35 pmCall for service4 min11df16c9
8:15 pmCall for service8 min8c80136c
8:33 pmCall for service15 min1618ad8d
8:45 pmOther6 minbfa8598e
9:18 pmTraining and testing1 min 29 s0a409001
9:34 pmCall for service12 mincb35a98c
10:27 pmCall for service16 min3d4d39ff

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: see the about page. See about this site for the sources and the publication rules.