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

Cincinnati, Ohio · one day

Tuesday 17 February 2026

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

42

drone flights over Cincinnati that day.

12:14 am

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

10 min

median flight. Half were shorter.

Cincinnati police drones flew 42 times on Tuesday 17 February 2026, the first at 12:14 am and the last at 11:43 pm EST, by Cincinnati Police Department's published record.

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

42 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:14 amCall for service13 min859aaead
12:52 amCall for service2 min36c9aac5
2:03 amCall for service11 minafe62c96
2:57 amCall for service14 min98010e62
4:15 amCall for service3 min31bd24a6
4:46 amCall for service6 min4e54e50d
9:19 amCall for service3 min85b953f4
9:23 amCall for service2 min38c8806e
9:48 amCall for service10 mind6394579
11:39 amCall for service8 min37134a89
11:47 amCall for service12 mined43dab7
12:15 pmCall for service17 minf7733a85
12:20 pmCall for service4 min28178b7b
12:27 pmCall for service1 min 38 scc77cd4b
12:55 pmCall for service2 minceec50eb
1:13 pmCall for service12 min61adac1c
2:48 pmCall for service11 min7356d9fb
3:00 pmCall for service15 minab430cf6
3:15 pmCall for service15 minea1acb10
3:38 pmCall for service13 mine87d2a80
3:57 pmCall for service16 min25733691
4:08 pmCall for service3 mince40b8ac
4:26 pmCall for service8 min5122fc40
4:43 pmCall for service13 min3edfb99c
5:00 pmCall for service11 min78f9495c
5:51 pmCall for service13 min5bd04df5
6:36 pmCall for service15 min23e221bd
7:19 pmCall for service10 min3b6fe064
7:34 pmCall for service12 min677f15cf
7:56 pmCall for service4 minf43eb57c
8:08 pmCall for service7 min85031a6a
9:02 pmCall for service16 min62aa9bdd
9:03 pmCall for service4 min71fffe83
9:48 pmCall for service17 min8ec8da0d
10:00 pmCall for service4 min22577f12
10:32 pmCall for service11 min51a439bd
10:55 pmCall for service10 minf5a143a4
10:59 pmCall for service8 minde858dc6
11:08 pmCall for service10 min274c6f5d
11:14 pmCall for service3 min4666ccbb
11:21 pmCall for service8 min6ec4cebb
11:43 pmCall for service11 min33dbf9ac

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.