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

Rochester, Minnesota · one day

Friday 27 February 2026

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

17

drone flights over Rochester that day.

12:12 am

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

9 min

median flight. Half were shorter.

Rochester police drones flew 17 times on Friday 27 February 2026, the first at 12:12 am and the last at 11:36 pm CST, by Rochester Police Department's published record.

17 drawable flights of 17. 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. Call for service82%
  2. Search6%
  3. Traffic and crashes6%
  4. Events6%

Flights, in order

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

Takeoff (CST)PurposeAirborneFlight
12:12 amCall for service1 min 39 sccd3b2bc
12:20 amCall for service9 mineee4cff4
1:57 amCall for service6 min37bda2dc
3:22 amCall for service6 minf2ff4407
10:55 amCall for service10 min636d03fe
11:46 amCall for service14 min20969b50
12:34 pmCall for service20 min7fc02fb7
12:55 pmCall for service21 min26f55f17
5:54 pmSearch12 minf29d155d
6:23 pmTraffic and crashes8 min64318f30
6:31 pmCall for service10 min23f93153
6:54 pmCall for service6 min60a4cd23
9:15 pmCall for service10 minac03381e
9:49 pmEvents16 min7230f195
10:37 pmCall for service6 min765e3960
11:24 pmCall for service8 min820de0af
11:36 pmCall for service9 minb65fda81

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