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

Cincinnati, Ohio · one day

Monday 19 January 2026

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

41

drone flights over Cincinnati that day.

9:09 am

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

11 min

median flight. Half were shorter.

Cincinnati police drones flew 41 times on Monday 19 January 2026, the first at 9:09 am and the last at 11:12 pm EST, by Cincinnati Police Department's published record.

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

41 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
9:09 amCall for service7 mine245d85f
9:19 amCall for service9 min79684c00
10:31 amCall for service15 mine0465fa7
10:41 amCall for service15 min3e3dafae
11:07 amCall for service12 mind868b007
11:20 amCall for service10 min971650cc
11:35 amCall for service4 min0b729559
11:45 amCall for service14 minbf06afba
11:53 amCall for service13 min2eff55d1
12:29 pmCall for service12 min650c5f33
12:34 pmCall for service16 min3c168736
1:03 pmCall for service5 min7801caef
1:03 pmCall for service11 min9deec209
1:19 pmCall for service2 min49050b13
1:29 pmCall for service12 min2740fccb
1:48 pmCall for service1 min 18 s8659fc40
2:13 pmCall for service7 minac3028c0
2:21 pmCall for service8 mincab4de46
2:34 pmCall for service2 minc3f46228
2:51 pmCall for service15 minfdcbb3b3
3:06 pmCall for service16 min6f2fb6f8
3:29 pmCall for service13 minaac15afe
5:04 pmCall for service6 mincada7998
5:16 pmCall for service19 min21a6d4e6
5:19 pmCall for service12 minfb7df133
5:35 pmCall for service19 min10caa6b3
6:01 pmCall for service5 min42ddd073
6:16 pmCall for service8 min9e477b7d
6:31 pmCall for service9 min3fcd00e9
6:50 pmCall for service6 mine633f286
6:53 pmCall for service10 min1b9d4a52
7:09 pmCall for service11 min0d2338ba
7:56 pmCall for service6 minf45ed2e5
8:00 pmCall for service16 min2d9c1a7f
8:23 pmCall for service10 minf840232f
8:44 pmCall for service11 min8767e24e
9:07 pmCall for service13 mindab25d39
9:30 pmCall for service16 minc25d54eb
9:56 pmCall for service14 min69d3941e
10:44 pmCall for service19 min0581188c
11:12 pmCall for service10 min4eafa69e

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