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

Milwaukee, Wisconsin · one day

Thursday 1 October 2026

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

15

drone flights over Milwaukee that day.

11:41 am

first takeoff; the last was at 9:07 pm.

12 min

median flight. Half were shorter.

Milwaukee police drones flew 15 times on Thursday 1 October 2026, the first at 11:41 am and the last at 9:07 pm CDT, by Milwaukee Police Department's published record.

15 drawable flights of 15. 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. Call for service53%
  2. Training and testing33%
  3. Patrol support13%

Flights, in order

15 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
11:41 amTraining and testing20 min8fd2848a
12:20 pmTraining and testing3 mind7bd2552
12:25 pmTraining and testing1 min 54 s272d37f8
12:28 pmTraining and testing1 min 18 s9705fa17
12:30 pmTraining and testing2 mineb406bbe
5:26 pmPatrol support7 mine7f3287f
5:34 pmCall for service20 mindf808f30
5:49 pmCall for service19 minb3138ec8
6:03 pmCall for service16 minec431ecf
6:27 pmCall for service17 min704626ee
7:09 pmCall for service16 min75ee0885
7:33 pmCall for service12 min3c642256
7:46 pmPatrol support9 minf510bef1
8:09 pmCall for service17 min90cdfaa4
9:07 pmCall for service11 min39b8364d

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