CityDroneWatch
  1. CityDroneWatch
  2. Wisconsin
  3. Milwaukee
  4. September 2026
  5. 2

Milwaukee, Wisconsin · one day

Wednesday 2 September 2026

39 drone flights from Milwaukee Police Department's published record.

39

drone flights over Milwaukee that day.

12:50 am

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

9 min

median flight. Half were shorter.

Milwaukee police drones flew 39 times on Wednesday 2 September 2026, the first at 12:50 am and the last at 10:42 pm CDT, by Milwaukee Police Department's published record.

39 drawable flights of 39. 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. Training and testing74%
  2. Call for service21%
  3. Patrol support5%

Flights, in order

39 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:50 amCall for service17 min892be51b
2:18 amPatrol support11 min0b631815
9:12 amTraining and testing1 min 19 sc4b7f674
11:41 amTraining and testing11 minefce64e9
12:21 pmTraining and testing9 minbe423b2e
12:33 pmTraining and testing8 min9fc8211f
12:33 pmTraining and testing8 min1de95246
12:42 pmTraining and testing9 minedc7b988
1:03 pmTraining and testing10 minc5c10e49
1:03 pmTraining and testing10 min32511687
1:15 pmTraining and testing10 minde188a45
1:15 pmTraining and testing2 mineb5bd29f
1:21 pmTraining and testing6 min502ce6bd
1:27 pmTraining and testing7 min36c6626c
2:29 pmTraining and testing27 mind9f3b92e
2:31 pmTraining and testing9 min8b565502
2:31 pmTraining and testing17 sc2e801aa
2:34 pmTraining and testing14 min4ac559c5
2:43 pmTraining and testing10 minde5a93c2
2:51 pmTraining and testing14 min836337fc
2:58 pmTraining and testing9 min0a0c7d82
2:59 pmTraining and testing7 min01e8ce91
3:09 pmTraining and testing7 min5deba2f1
3:10 pmTraining and testing12 min9655d9bd
3:10 pmTraining and testing9 min5261960d
3:19 pmTraining and testing6 min021cd965
3:21 pmTraining and testing5 min0b5cbdaa
3:24 pmCall for service10 min06298ba5
3:25 pmTraining and testing28 s1a977184
3:26 pmTraining and testing12 min2152e25b
3:27 pmTraining and testing5 mind855ae24
3:31 pmTraining and testing16 min2a86720e
3:35 pmCall for service17 minbfb2204a
5:19 pmCall for service23 min59e8c04c
6:38 pmCall for service9 min35728c19
7:59 pmCall for service19 mind780cc9f
9:37 pmPatrol support14 minbce4b4e5
10:11 pmCall for service16 mina0eaa787
10:42 pmCall for service6 min89f7e95b

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.