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

Rochester, Minnesota · one day

Friday 13 February 2026

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

28

drone flights over Rochester that day.

8:19 am

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

8 min

median flight. Half were shorter.

Rochester police drones flew 28 times on Friday 13 February 2026, the first at 8:19 am and the last at 10:29 pm CST, by Rochester Police Department's published record.

28 drawable flights of 28. 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, CST.

12a1a2a3a4a5a6a7a8a9a10a11a12p1p2p3p4p5p6p7p8p9p10p11p

Why, in the agency's words

  1. Call for service36%
  2. Training and testing29%
  3. Not stated14%
  4. Events14%
  5. Traffic and crashes4%
  6. Search4%

Flights, in order

28 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 (CST)PurposeAirborneFlight
8:19 amNot stated6 minbdc4456f
8:31 amNot stated6 min7e7b607e
8:38 amNot stated8 min155bc949
9:20 amTraining and testing9 minb8f77fe2
9:32 amTraining and testing7 min87589a47
9:46 amTraining and testing1 min 38 s412ca405
9:53 amTraining and testing5 minb09854f8
10:01 amTraining and testing6 mind1b354ed
10:38 amCall for service3 min80d6e2d4
10:42 amTraining and testing8 min633e9689
11:43 amEvents13 min56be2904
12:01 pmCall for service15 min7686a5fa
1:00 pmTraffic and crashes7 min025d27b9
1:23 pmCall for service8 mina709f328
1:32 pmNot stated6 mine6a699af
2:23 pmTraining and testing6 mind27fa9b1
2:30 pmCall for service9 min4467e1b1
3:06 pmTraining and testing1 min 22 s853d0290
4:04 pmCall for service7 min4a079275
4:37 pmSearch12 min805f35f5
4:57 pmCall for service15 min3dfc24b7
6:45 pmEvents8 min8d1debe0
7:04 pmEvents12 mind2fe8cb5
8:05 pmCall for service12 min9825bb0a
8:26 pmEvents3 min3f6eba81
9:07 pmCall for service10 min16ab0355
9:32 pmCall for service15 minb33c5775
10:29 pmCall for service23 min61389a4a

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: see the about page. See about this site for the sources and the publication rules.