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

Rochester, Minnesota · one day

Thursday 1 October 2026

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

8

drone flights over Rochester that day.

2:42 am

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

13 min

median flight. Half were shorter.

Rochester police drones flew 8 times on Thursday 1 October 2026, the first at 2:42 am and the last at 11:42 pm CDT, by Rochester Police Department's published record.

8 drawable flights of 8. 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 service50%
  2. Events50%

Flights, in order

8 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
2:42 amCall for service20 min3c3a53de
3:42 pmCall for service10 min686c8a10
4:57 pmCall for service23 mina25abc0b
6:22 pmCall for service19 minffb5d176
8:30 pmEvents10 min12b691c9
10:07 pmEvents13 min5ff20183
10:54 pmEvents11 minaa30ef04
11:42 pmEvents12 min4b88dbeb

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