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

Rochester, Minnesota · one day

Friday 22 May 2026

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

15

drone flights over Rochester that day.

12:50 am

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

12 min

median flight. Half were shorter.

Rochester police drones flew 15 times on Friday 22 May 2026, the first at 12:50 am and the last at 10:30 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 testing40%

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:50 amCall for service9 minaa2f1e58
8:29 amTraining and testing13 min159a83a6
8:31 amTraining and testing13 min11529a3d
8:54 amTraining and testing3 min6ee6bf8e
9:00 amTraining and testing5 minbd822bbf
9:54 amCall for service12 min7cd719ea
10:31 amCall for service7 minb1dea55e
10:44 amCall for service14 min56826816
10:46 amCall for service13 minf8280457
12:23 pmCall for service14 minf5fc58cf
2:28 pmTraining and testing10 min54cd1319
7:39 pmTraining and testing3 min5d5132a3
7:57 pmCall for service12 minf66a8fc2
9:45 pmCall for service16 min37e27ea3
10:30 pmCall for service7 min6c0929f2

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.