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

Cincinnati, Ohio · one day

Friday 9 January 2026

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

44

drone flights over Cincinnati that day.

4:07 am

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

14 min

median flight. Half were shorter.

Cincinnati police drones flew 44 times on Friday 9 January 2026, the first at 4:07 am and the last at 11:45 pm EST, by Cincinnati Police Department's published record.

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

44 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
4:07 amCall for service10 min26317b78
6:57 amCall for service17 minb87ad565
9:29 amCall for service15 mine960bae1
10:01 amCall for service14 min5993b941
10:14 amCall for service11 min2b930a76
10:35 amCall for service18 min4e8681bc
10:49 amCall for service24 min954503cd
11:08 amCall for service8 minea3c1d24
11:37 amCall for service11 min10ca8e4c
11:40 amCall for service14 min7dd9ed08
1:09 pmCall for service5 min702c22d3
2:10 pmCall for service14 min21effc98
2:35 pmCall for service12 min6884d377
2:54 pmCall for service1 min 24 s1a660e02
2:55 pmCall for service8 mine349de8c
3:09 pmCall for service15 min60181512
3:13 pmCall for service17 min59a3edb8
3:18 pmCall for service18 min4376f2cc
3:29 pmCall for service13 min36e73f70
3:57 pmCall for service12 min0e45977f
3:58 pmCall for service12 mind5ff3b12
4:31 pmCall for service5 min286e6f31
4:44 pmCall for service14 min5158674c
5:23 pmCall for service20 min559649b8
5:37 pmCall for service9 mind8807b56
6:35 pmCall for service17 min9bbe0ffe
7:02 pmCall for service19 minceda8cf0
7:09 pmCall for service15 mindde20b67
7:17 pmCall for service9 minea53e7ed
7:44 pmCall for service8 mineaa1aaae
7:45 pmCall for service15 min157381ef
8:39 pmCall for service19 min9c7b770d
8:41 pmCall for service1 min 47 s9ecc294f
8:51 pmCall for service9 min0f096072
9:14 pmCall for service12 min1797a664
9:25 pmCall for service18 min79d7e873
9:45 pmCall for service16 minf9f15e12
9:51 pmCall for service8 minaa99db46
10:08 pmCall for service15 minb022be09
10:13 pmCall for service10 mine8108df2
10:44 pmCall for service10 minc87e1b61
11:10 pmCall for service17 mind5a10267
11:36 pmCall for service15 min7c85955c
11:45 pmCall for service16 minb9cf719b

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: see the about page. See about this site for the sources and the publication rules.