CityDroneWatch
  1. CityDroneWatch
  2. Minnesota
  3. Rochester
  4. May 2026
  5. 31

Rochester, Minnesota · one day

Sunday 31 May 2026

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

16

drone flights over Rochester that day.

12:38 am

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

14 min

median flight. Half were shorter.

Rochester police drones flew 16 times on Sunday 31 May 2026, the first at 12:38 am and the last at 8:32 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 service81%
  2. Events12%
  3. Search6%

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:38 amCall for service16 min3f880489
12:52 amCall for service13 mind254cb9e
1:22 amCall for service17 min082ed616
10:18 amSearch16 mindb38a83e
11:09 amCall for service14 mine4acd3f9
11:42 amCall for service13 min43a2235b
12:21 pmCall for service11 min0709446b
1:28 pmCall for service9 minb33ba0cb
2:15 pmCall for service20 min01005a48
3:34 pmCall for service18 mindb8965f5
4:12 pmCall for service6 min18eba97b
4:30 pmEvents15 min534b002d
5:16 pmCall for service8 mindea5f43f
5:47 pmCall for service13 mina4fc5386
5:59 pmEvents16 min2d4dbeb1
8:32 pmCall for service4 mince3f0a51

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.