CityDroneWatch
  1. CityDroneWatch
  2. Ohio
  3. Cincinnati
  4. January 2026
  5. 22

Cincinnati, Ohio · one day

Thursday 22 January 2026

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

37

drone flights over Cincinnati that day.

12:15 am

first takeoff; the last was at 11:35 pm.

13 min

median flight. Half were shorter.

Cincinnati police drones flew 37 times on Thursday 22 January 2026, the first at 12:15 am and the last at 11:35 pm EST, by Cincinnati Police Department's published record.

37 drawable flights of 37. 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, EST.

12a1a2a3a4a5a6a7a8a9a10a11a12p1p2p3p4p5p6p7p8p9p10p11p

Why, in the agency's words

  1. Call for service100%

Flights, in order

37 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 (EST)PurposeAirborneFlight
12:15 amCall for service11 minaeff7ce6
12:56 amCall for service14 min95d172d3
1:58 amCall for service11 mina8f0f315
2:17 amCall for service11 min12f4348a
4:33 amCall for service12 min21b486f0
9:50 amCall for service19 min87994382
10:12 amCall for service18 min2144043c
10:32 amCall for service20 min5baf3fa0
10:55 amCall for service9 min18494273
11:29 amCall for service10 min6dc63e0e
11:45 amCall for service11 min0147d105
11:46 amCall for service9 minefb934eb
11:58 amCall for service4 min6a86bab4
12:39 pmCall for service9 min8d07733b
12:48 pmCall for service25 minaa968278
12:49 pmCall for service15 min4a3e1ba6
1:23 pmCall for service22 min09e26537
1:27 pmCall for service3 minb6b7dd22
1:47 pmCall for service25 mind6ad3927
2:15 pmCall for service24 minb3aea3df
2:33 pmCall for service1 min 21 s1b8c6f1a
2:42 pmCall for service25 mind221cd8f
3:28 pmCall for service24 min337c145d
4:09 pmCall for service15 minb25a3508
4:19 pmCall for service9 min6122b838
5:24 pmCall for service15 min8837c7d5
5:51 pmCall for service10 min09f75864
7:24 pmCall for service14 minf30b97f7
7:25 pmCall for service10 min4e2e7c96
7:49 pmCall for service17 mine6d77096
7:59 pmCall for service14 min19401c92
8:36 pmCall for service16 min224fed2c
10:22 pmCall for service14 mine314a993
10:31 pmCall for service13 mina802ffc7
10:44 pmCall for service6 mina7316951
11:14 pmCall for service8 min44afd2dd
11:35 pmCall for service6 minee8fc6ce

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