CityDroneWatch
  1. CityDroneWatch
  2. Wisconsin
  3. Milwaukee
  4. July 2026
  5. 22

Milwaukee, Wisconsin · one day

Wednesday 22 July 2026

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

44

drone flights over Milwaukee that day.

12:16 am

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

15 min

median flight. Half were shorter.

Milwaukee police drones flew 44 times on Wednesday 22 July 2026, the first at 12:16 am and the last at 10:39 pm CDT, by Milwaukee Police Department's published record.

44 drawable flights of 44. 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 testing43%
  2. Patrol support30%
  3. Call for service25%
  4. Not stated2%

Flights, in order

44 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:16 amCall for service7 minc7613562
1:55 amPatrol support25 mindf069383
6:52 amTraining and testing52 s07fb09fe
7:25 amPatrol support19 min2e4c18fe
7:46 amPatrol support23 minef6bfc30
8:22 amPatrol support9 minb1785324
9:36 amTraining and testing25 min3f8792f1
9:39 amTraining and testing23 min8983344a
10:06 amTraining and testing28 minb06325ce
10:10 amTraining and testing23 mina95f1d52
11:23 amTraining and testing1 min 41 s958dcfa2
12:26 pmNot stated23 mina710fef8
12:46 pmCall for service14 mince4a6f9f
12:54 pmTraining and testing22 minabefb7b1
1:01 pmCall for service3 min4e2e79ab
1:02 pmCall for service7 min5fe06fb6
2:46 pmTraining and testing1 min 10 s7cfbb076
2:47 pmTraining and testing19 min56628df9
2:47 pmTraining and testing59 s994a7df9
2:50 pmTraining and testing25 min52dfdb57
3:14 pmTraining and testing24 min71175910
3:20 pmTraining and testing24 min599f5144
3:43 pmTraining and testing26 s961b5f63
3:44 pmTraining and testing34 s253c5fc5
3:47 pmTraining and testing26 sbf4bbc7d
3:48 pmTraining and testing24 minbf6d2633
3:49 pmTraining and testing24 min8e041288
4:11 pmPatrol support15 min0ec3e386
4:35 pmCall for service46 s4eb9e992
5:21 pmPatrol support19 minf175fc3a
5:25 pmPatrol support10 min6e2565cc
5:33 pmCall for service5 min5cf11513
5:45 pmCall for service7 min0976e9bd
6:29 pmCall for service15 minf1e77cd1
7:11 pmTraining and testing47 sf698ab52
7:15 pmPatrol support19 minb48eaeb8
7:37 pmPatrol support16 min97498433
8:14 pmPatrol support18 min09f1730d
9:38 pmPatrol support10 min44d58a8b
9:52 pmCall for service17 min685ab12a
10:03 pmCall for service3 min7069bf74
10:06 pmPatrol support16 min61bc7c28
10:14 pmPatrol support12 min5e4e25c7
10:39 pmCall for service13 min85a98da3

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