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

Rochester, Minnesota · one day

Friday 1 May 2026

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

29

drone flights over Rochester that day.

12:32 am

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

12 min

median flight. Half were shorter.

Rochester police drones flew 29 times on Friday 1 May 2026, the first at 12:32 am and the last at 11:36 pm CDT, by Rochester Police Department's published record.

29 drawable flights of 29. 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 service62%
  2. Search17%
  3. Training and testing14%
  4. Other3%
  5. Not stated3%

Flights, in order

29 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:32 amCall for service6 min7499decf
12:49 amCall for service14 min79de7224
1:31 amCall for service14 min4dc0cb32
2:15 amCall for service22 minfc6e2d51
3:38 amCall for service14 mince139aed
1:27 pmSearch13 min80138254
1:45 pmSearch21 min509e4353
2:46 pmSearch8 minb13862ba
3:17 pmCall for service20 min29764728
3:49 pmCall for service7 mine26555ce
4:05 pmCall for service4 min21d52059
4:30 pmCall for service1 min 19 s125d3af6
4:57 pmTraining and testing16 min442dc285
4:57 pmTraining and testing14 min5928fc56
5:14 pmTraining and testing57 s8789196e
5:14 pmTraining and testing51 s14f7cd1f
5:43 pmOther12 min999fc23a
6:07 pmCall for service8 min7876217b
6:32 pmNot stated11 min16309f46
6:56 pmCall for service11 min9223ac0b
7:25 pmCall for service10 min7b89a3f7
7:41 pmSearch16 min6c098789
7:53 pmCall for service12 min8bc98c2b
8:12 pmCall for service7 min7dcb6f4c
8:42 pmCall for service19 min537515e2
8:56 pmCall for service18 minab6360c6
10:01 pmSearch15 min1f164835
11:08 pmCall for service12 mina6647537
11:36 pmCall for service11 min3c9b5233

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).