CityDroneWatch
  1. CityDroneWatch
  2. Minnesota
  3. Rochester
  4. September 2026
  5. 11

Rochester, Minnesota · one day

Friday 11 September 2026

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

14

drone flights over Rochester that day.

11:49 am

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

10 min

median flight. Half were shorter.

Rochester police drones flew 14 times on Friday 11 September 2026, the first at 11:49 am and the last at 8:59 pm CDT, by Rochester Police Department's published record.

14 drawable flights of 14. 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 service57%
  2. Not stated14%
  3. Events14%
  4. Training and testing7%
  5. Other7%

Flights, in order

14 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
11:49 amNot stated9 min518f150d
12:34 pmCall for service6 min1232b6c4
12:59 pmEvents7 mind17a312f
2:23 pmEvents14 min8cc662d3
3:17 pmTraining and testing1 min 35 s757c5d00
3:54 pmCall for service13 mine6cc9977
5:28 pmCall for service7 minaece05f5
5:41 pmOther12 mindc3a8c4d
6:01 pmCall for service14 min593339d7
7:19 pmCall for service23 minba061e32
7:44 pmCall for service16 min766482d6
8:23 pmCall for service11 min5bf0f0b8
8:39 pmNot stated44 sda1f725c
8:59 pmCall for service9 min04ef0c49

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.