DroneRecord
  1. Drone Record
  2. Minnesota
  3. Rochester
  4. February 2026
  5. 20

Rochester, Minnesota · one day

Friday 20 February 2026

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

18

drone flights over Rochester that day.

10:32 am

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

10 min

median flight. Half were shorter.

Rochester police drones flew 18 times on Friday 20 February 2026, the first at 10:32 am and the last at 10:57 pm CST, by Rochester Police Department's published record.

15 drawable flights of 18. Each path is simplified, and its first and last 200 m are removed.
One flight; takeoff and landing removed

Hour by hour

Takeoffs by hour, CST.

12a1a2a3a4a5a6a7a8a9a10a11a12p1p2p3p4p5p6p7p8p9p10p11p

Why, in the agency's words

  1. Events44%
  2. Call for service33%
  3. Training and testing17%
  4. Search6%

Flights, in order

18 listable flights. Flights in the latest full month link to their own page.

Takeoff (CST)PurposeAirborneFlight
10:32 amCall for service10 mine7264d8d
11:46 amCall for service5 mine9df2ec2
11:58 amCall for service7 mince752515
12:49 pmSearch18 mind8fb5b85
1:21 pmCall for service9 min486e73fb
1:31 pmCall for service16 minb3d47444
2:05 pmCall for service20 min6bfec550
4:25 pmTraining and testing48 s29885b40
5:00 pmTraining and testing6 min6a35dc72
5:27 pmTraining and testing1 min 11 s4d53c4a9
6:58 pmEvents18 mined3cdd8a
7:18 pmEvents13 minad2e7d43
7:37 pmEvents3 min81acbce6
8:15 pmEvents5 min02d392b7
8:46 pmEvents20 min15a028f0
9:24 pmEvents12 minc48514b7
10:29 pmEvents10 minec542632
10:57 pmEvents13 minff1e0645

How this page is made

  • Nothing that landed in the last 48 hours is counted, listed or drawn.
  • Drawn paths are simplified to 10 m and lose their first and last 200 m; flights too short to keep an interior are counted but not drawn.
  • The record's free-text description is never read into a page. Flights whose stated purpose names a domestic, sexual-assault, kidnapping, welfare, mental-health or juvenile matter are counted in totals and appear in neither the flight list nor on the map.
  • 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).