CityDroneWatch
  1. CityDroneWatch
  2. Ohio
  3. Cincinnati
  4. October 2025
  5. 20

Cincinnati, Ohio · one day

Monday 20 October 2025

42 drone flights from Cincinnati Police Department's published record.

42

drone flights over Cincinnati that day.

8:21 am

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

12 min

median flight. Half were shorter.

Cincinnati police drones flew 42 times on Monday 20 October 2025, the first at 8:21 am and the last at 9:22 pm EDT, by Cincinnati Police Department's published record.

42 drawable flights of 42. 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, EDT.

12a1a2a3a4a5a6a7a8a9a10a11a12p1p2p3p4p5p6p7p8p9p10p11p

Why, in the agency's words

  1. Call for service100%

Flights, in order

42 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 (EDT)PurposeAirborneFlight
8:21 amCall for service16 min3b4ae524
8:40 amCall for service21 min80f3f9a8
9:17 amCall for service18 mine136a847
9:33 amCall for service3 min7086d9d1
10:02 amCall for service17 min27b719b3
10:32 amCall for service18 mind5de0235
10:39 amCall for service13 minc7dab0a3
10:52 amCall for service14 min2d2a0538
10:58 amCall for service14 min0336f976
11:39 amCall for service20 min41a05f0d
12:06 pmCall for service21 minfc31966e
1:20 pmCall for service1 min 10 s8987c02a
1:24 pmCall for service20 min69ac2c64
1:48 pmCall for service12 min5e572d66
2:03 pmCall for service5 min2649ec00
2:09 pmCall for service54 sa8c3fe5f
2:11 pmCall for service13 min56d65555
2:22 pmCall for service3 minefe83c64
2:23 pmCall for service10 mine596e3b2
3:01 pmCall for service7 mineb08447f
3:11 pmCall for service13 min2faadbcf
3:13 pmCall for service11 min2052adee
3:36 pmCall for service7 min620d40a1
3:39 pmCall for service17 min413f8ae5
3:41 pmCall for service19 min2e7a3f95
4:01 pmCall for service7 min11035172
4:45 pmCall for service9 min52df75c0
5:21 pmCall for service17 min5b83a1d7
5:28 pmCall for service11 min449072d1
6:46 pmCall for service11 mine866f01d
6:49 pmCall for service13 minbc393848
6:59 pmCall for service15 mine0796518
7:26 pmCall for service12 mina807c31f
7:31 pmCall for service6 min3a5be095
7:40 pmCall for service9 minc785e7a1
8:11 pmCall for service12 mina0c4cfcf
8:20 pmCall for service15 min2b2cc100
8:30 pmCall for service3 min98d82a8c
8:37 pmCall for service13 min665edaec
8:40 pmCall for service11 min9543a9e0
9:14 pmCall for service6 minec43defc
9:22 pmCall for service8 min37a58f7a

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