drone flights over Milwaukee that day.

12:10 am

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

14 min

median flight. Half were shorter.

Milwaukee police drones flew 35 times on Thursday 23 July 2026, the first at 12:10 am and the last at 10:24 pm CDT, by Milwaukee Police Department's published record.

35 drawable flights of 35. 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

Training and testing63%
Patrol support17%
Call for service14%
Not stated3%
Events3%

Flights, in order

35 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)	Purpose	Airborne	Flight
12:10 am	Call for service	19 min	`d5c5527c`
8:13 am	Training and testing	57 s	`58e7e74f`
10:16 am	Training and testing	15 min	`ddb0e054`
10:16 am	Training and testing	11 min	`bdc0ac33`
10:30 am	Training and testing	27 min	`fdaf69f6`
10:32 am	Training and testing	8 min	`af0655da`
10:46 am	Training and testing	13 min	`db3ccc07`
10:59 am	Training and testing	9 min	`bceff997`
11:01 am	Training and testing	27 min	`baf70682`
11:18 am	Training and testing	4 min	`ae4dbff3`
11:23 am	Training and testing	21 min	`b7ca3d8d`
11:31 am	Training and testing	23 min	`fdc7aa79`
11:51 am	Training and testing	3 min	`84254499`
1:39 pm	Training and testing	21 min	`ec527546`
1:41 pm	Training and testing	28 min	`e206e9d6`
2:05 pm	Training and testing	20 min	`008ac641`
2:13 pm	Training and testing	25 min	`bdf0dabf`
2:41 pm	Training and testing	22 min	`65a39dfe`
2:43 pm	Training and testing	26 min	`194d4075`
3:07 pm	Training and testing	21 min	`562ea44e`
3:10 pm	Patrol support	6 min	`92f16665`
3:12 pm	Training and testing	24 min	`8f58881f`
3:32 pm	Not stated	1 min 51 s	`b5c18863`
3:43 pm	Training and testing	5 min	`91a0a311`
3:52 pm	Training and testing	7 min	`c60148b7`
4:10 pm	Call for service	18 min	`2c9c4230`
4:30 pm	Call for service	14 min	`c1b67867`
6:19 pm	Call for service	47 s	`1a1a64cb`
7:03 pm	Patrol support	12 min	`399c960e`
7:30 pm	Patrol support	10 min	`2f64036d`
7:45 pm	Patrol support	7 min	`30c77c36`
7:50 pm	Events	15 min	`81237b5c`
9:32 pm	Patrol support	4 min	`b8adaece`
10:04 pm	Patrol support	17 min	`1aae3f9c`
10:24 pm	Call for service	11 min	`829c170a`

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