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

Cincinnati, Ohio · one day

Tuesday 20 January 2026

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

46

drone flights over Cincinnati that day.

12:00 am

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

12 min

median flight. Half were shorter.

Cincinnati police drones flew 46 times on Tuesday 20 January 2026, the first at 12:00 am and the last at 11:46 pm EST, by Cincinnati Police Department's published record.

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

46 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:00 amCall for service18 min535a66f0
12:13 amCall for service18 minc737b96c
12:38 amCall for service10 minbad4f2e3
12:39 amCall for service12 min4204ad47
1:04 amCall for service14 minade679d6
1:13 amCall for service14 mincfa19a26
1:35 amCall for service18 mina228fad1
2:34 amCall for service14 min60012713
2:58 amCall for service16 min45a19b68
3:36 amCall for service10 min8f1a0888
3:48 amCall for service15 min9323188a
4:07 amCall for service19 mind5a367ed
4:28 amCall for service14 min995b20ba
5:09 amCall for service16 minf28eed2c
6:00 amCall for service46 se6c4293a
7:03 amCall for service12 min5d1ace9c
9:53 amCall for service2 min45e03ff1
10:59 amCall for service17 min508547fe
11:16 amCall for service2 min6f031dc0
11:18 amCall for service26 s3d40d2b3
12:43 pmCall for service17 min9e129f3e
1:01 pmCall for service7 min1c922764
1:16 pmCall for service10 min37119322
1:30 pmCall for service2 min5f001219
2:13 pmCall for service18 mina3fc41d5
2:35 pmCall for service18 min4b701def
3:30 pmCall for service10 mindd8a5db3
3:49 pmCall for service1 min 12 sfe57c71b
3:51 pmCall for service11 min95c6d152
4:53 pmCall for service7 min825cb1ad
5:23 pmCall for service13 min43edb46e
6:44 pmCall for service4 mina3d5af6a
6:48 pmCall for service8 min00fe2978
6:51 pmCall for service20 min7041ef08
7:05 pmCall for service8 min48184590
7:50 pmCall for service5 min7e104787
7:53 pmCall for service18 mindfd0bd8f
8:04 pmCall for service16 min5d086256
8:35 pmCall for service16 min04ad22cc
8:50 pmCall for service1 min 15 s988ffe15
9:50 pmCall for service11 min77ee0318
9:56 pmCall for service14 minff2c83c2
10:10 pmCall for service8 minbcfdbc43
11:11 pmCall for service9 mind7523f07
11:34 pmCall for service7 min4b265b1c
11:46 pmCall for service14 min18c591f6

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