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

Cincinnati, Ohio · one day

Thursday 15 January 2026

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

43

drone flights over Cincinnati that day.

12:23 am

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

13 min

median flight. Half were shorter.

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

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

43 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:23 amCall for service5 min9e0806d2
12:58 amCall for service10 min05c197e4
1:22 amCall for service16 min2f74a9cf
2:11 amCall for service14 minbc784dce
3:00 amCall for service6 minfed6e4d5
3:20 amCall for service13 min248763c6
4:58 amCall for service13 min7e292128
8:33 amCall for service6 minbcaa560c
8:55 amCall for service7 min1cfb735d
9:07 amCall for service2 min5bf24dea
9:25 amCall for service13 min2b9045ab
11:00 amCall for service12 min0724e4a1
11:13 amCall for service12 minea85a326
11:57 amCall for service16 minb1a1fa6a
11:59 amCall for service1 min 15 sc21115b5
1:15 pmCall for service6 min2129991f
1:24 pmCall for service13 minbc87310e
1:53 pmCall for service16 min22a6346c
2:39 pmCall for service15 min3c6870cb
2:50 pmCall for service21 min8ba620f0
2:56 pmCall for service7 min44d13691
3:05 pmCall for service21 min42ed595e
3:24 pmCall for service22 minc2d2b7b2
3:42 pmCall for service18 mina8c2d84e
3:58 pmCall for service19 mine77aed2c
4:33 pmCall for service15 min8431dae3
4:53 pmCall for service15 min9183398a
6:03 pmCall for service12 min30dc8c7a
6:26 pmCall for service5 min5f61c0e7
6:42 pmCall for service12 min4c27e8c9
6:56 pmCall for service17 min1a56fbb8
7:03 pmCall for service17 mina1c6eac1
7:13 pmCall for service17 minc5022594
7:14 pmCall for service1 min 02 sa57b0d2c
7:28 pmCall for service11 min42e30c4a
7:41 pmCall for service18 min1dde0090
9:45 pmCall for service10 mine550df74
9:46 pmCall for service8 min38d01ce1
9:56 pmCall for service10 min4e9de915
10:32 pmCall for service13 mina97e5376
10:41 pmCall for service15 mind5ee9f33
11:00 pmCall for service18 minbae04283
11:39 pmCall for service9 min401e4048

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.