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

Rochester, Minnesota · one day

Saturday 13 June 2026

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

16

drone flights over Rochester that day.

9:31 am

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

12 min

median flight. Half were shorter.

Rochester police drones flew 16 times on Saturday 13 June 2026, the first at 9:31 am and the last at 11: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. Call for service94%
  2. Events6%

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
9:31 amCall for service21 min7700daae
10:21 amCall for service14 minbf419d27
10:43 amCall for service9 min4f2f29f0
11:05 amCall for service12 mina0b32a21
1:38 pmCall for service9 min84a72375
2:18 pmCall for service11 min1fe18388
4:34 pmCall for service15 mine7552f45
5:19 pmCall for service12 min71771552
6:30 pmCall for service6 minebd175ea
7:23 pmCall for service5 mince536c68
7:50 pmCall for service12 minb6e88d25
8:45 pmCall for service7 minc7f94b25
9:30 pmCall for service14 min8d2a1a85
10:03 pmCall for service12 minbd0457e5
10:20 pmCall for service6 min54de4f54
11:46 pmEvents4 min6a16c51e

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.