CityDroneWatch
  1. CityDroneWatch
  2. Ohio
  3. Cincinnati
  4. February 2026
  5. 10

Cincinnati, Ohio · one day

Tuesday 10 February 2026

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

46

drone flights over Cincinnati that day.

12:35 am

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

12 min

median flight. Half were shorter.

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

43 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:35 amCall for service13 min0b87156d
1:00 amCall for service10 minbb23c64f
1:37 amCall for service16 minca0823e0
1:51 amCall for service20 min9f986669
2:14 amCall for service10 min68b49561
2:40 amCall for service10 min29e4859f
2:51 amCall for service5 min038bc179
5:26 amCall for service9 min7fedb0a8
5:38 amCall for service15 min63d61cc7
6:13 amCall for service10 minf6ad2079
8:02 amCall for service18 minccc3741e
8:35 amCall for service17 minc7b45df4
8:40 amCall for service5 mind5b622f4
8:45 amCall for service12 mincf016031
9:19 amCall for service17 min62ba0658
10:46 amCall for service10 min7751f64b
11:01 amCall for service11 min971420d4
11:19 amCall for service6 min9bcfd74f
12:06 pmCall for service15 min0e67c0d5
12:10 pmCall for service11 min9dc4ba3e
1:15 pmCall for service11 minb01b7e44
1:28 pmCall for service19 min4997c223
1:50 pmCall for service7 min8cbdf394
1:52 pmCall for service7 minf07a0454
2:03 pmCall for service13 mina449b053
2:39 pmCall for service8 minef1ceef2
3:16 pmCall for service7 min4c856149
3:25 pmCall for service14 minacb212d2
4:33 pmCall for service15 min2a3a4d28
4:50 pmCall for service10 mincaf561fd
4:54 pmCall for service20 min5cc5411a
5:05 pmCall for service20 min90e3b423
5:17 pmCall for service18 min6c9f9bf8
5:38 pmCall for service11 min04987ec7
6:07 pmCall for service6 minfb998f45
6:12 pmCall for service19 minabb6d10f
6:33 pmCall for service19 min1e331d8a
7:03 pmCall for service18 min3c0069da
8:09 pmCall for service12 mina36ba555
8:24 pmCall for service11 min81e822fd
9:14 pmCall for service14 minf42b2162
10:02 pmCall for service8 minb0752d53
10:41 pmCall for service12 minbdcef7d2
10:53 pmCall for service11 min702c5a03
11:01 pmCall for service15 min3b0b538f
11:26 pmCall for service14 min0b52a52c

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.