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

Rochester, Minnesota · one day

Wednesday 13 May 2026

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

32

drone flights over Rochester that day.

8:02 am

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

9 min

median flight. Half were shorter.

Rochester police drones flew 32 times on Wednesday 13 May 2026, the first at 8:02 am and the last at 10:10 pm CDT, by Rochester Police Department's published record.

32 drawable flights of 32. 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 service41%
  2. Training and testing38%
  3. Events16%
  4. Not stated6%

Flights, in order

32 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
8:02 amEvents7 min23dd96ca
8:50 amTraining and testing7 min60f5045a
8:50 amTraining and testing6 minb387d49a
8:58 amTraining and testing9 min1563f9dc
9:00 amTraining and testing7 mine4d38df5
10:05 amTraining and testing2 min83d37933
10:05 amTraining and testing1 min 44 s1ca9481e
10:19 amCall for service9 min13dd516a
10:51 amTraining and testing10 mind78286d6
10:58 amTraining and testing10 min31b267c9
11:11 amTraining and testing9 minc4e69f8d
11:55 amCall for service17 min9bfeca00
1:10 pmCall for service7 min3970f92a
1:28 pmCall for service7 min7633fc20
1:46 pmNot stated8 minc0f23a13
2:10 pmCall for service5 mindac19082
4:18 pmCall for service16 min8027b964
4:52 pmTraining and testing6 min2fd5588f
4:53 pmTraining and testing5 minac9fdc67
5:01 pmCall for service11 min5cfaf325
5:10 pmCall for service15 mine2d5e99e
6:05 pmCall for service12 min454ac6cc
6:29 pmCall for service11 min232e85d2
6:47 pmCall for service12 min084400e5
7:07 pmTraining and testing4 min650dd691
7:07 pmNot stated3 mind2d92363
8:02 pmCall for service17 min017802cc
8:05 pmEvents15 min6b3683c5
9:04 pmEvents8 min33901d36
9:11 pmCall for service18 min100d42ad
9:33 pmEvents9 min6450e1d7
10:10 pmEvents16 min7d16c5a0

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: file an issue in the korvid-labs repository (demo).