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

Rochester, Minnesota · one day

Tuesday 29 September 2026

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

15

drone flights over Rochester that day.

12:29 am

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

14 min

median flight. Half were shorter.

Rochester police drones flew 15 times on Tuesday 29 September 2026, the first at 12:29 am and the last at 10:18 pm CDT, by Rochester Police Department's published record.

15 drawable flights of 15. 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 service60%
  2. Training and testing20%
  3. Events13%
  4. Other7%

Flights, in order

15 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:29 amCall for service10 min272b4ed9
5:08 amCall for service17 minc4ca0cdb
12:09 pmCall for service16 min0dce78b4
5:21 pmCall for service16 min0bd0bab8
5:41 pmCall for service9 min0b3f4568
6:00 pmOther5 minfd06d3ab
6:25 pmTraining and testing16 mina9ae718b
6:39 pmCall for service18 min7652ec51
7:01 pmCall for service11 min92d828e4
7:14 pmEvents8 min027f1ab0
7:46 pmCall for service14 min256a5052
7:58 pmTraining and testing14 min24940242
8:32 pmEvents12 min05d6e8be
9:53 pmCall for service20 min529225a9
10:18 pmTraining and testing3 mine22775e6

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.