CityDroneWatch
  1. CityDroneWatch
  2. Minnesota
  3. Rochester
  4. June 2026
  5. 3

Rochester, Minnesota · one day

Wednesday 3 June 2026

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

16

drone flights over Rochester that day.

3:56 am

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

9 min

median flight. Half were shorter.

Rochester police drones flew 16 times on Wednesday 3 June 2026, the first at 3:56 am and the last at 4:46 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. Training and testing31%
  2. Events31%
  3. Call for service25%
  4. Other6%
  5. Traffic and crashes6%

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
3:56 amCall for service13 min90e24c43
7:40 amOther14 min03b6a7e3
9:54 amTraining and testing5 min787ced21
10:05 amTraining and testing7 min2812f3b0
11:00 amEvents16 min226df711
11:05 amEvents9 min365bf186
12:02 pmTraining and testing1 min 21 sa520fb09
12:03 pmTraining and testing1 min 30 s15b8ae51
12:09 pmEvents21 min216e226e
12:24 pmCall for service17 min1d45db53
1:44 pmEvents15 min7e8b133a
1:57 pmCall for service4 minacbd50e3
2:15 pmCall for service9 mine1800b5d
2:58 pmEvents10 min58f93c56
4:12 pmTraining and testing2 min6647497e
4:46 pmTraffic and crashes8 min47bb1ab3

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.