CityDroneWatch
  1. CityDroneWatch
  2. Ohio
  3. Cincinnati
  4. July 2026
  5. 27

Cincinnati, Ohio · one day

Monday 27 July 2026

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

45

drone flights over Cincinnati that day.

7:26 am

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

13 min

median flight. Half were shorter.

Cincinnati police drones flew 45 times on Monday 27 July 2026, the first at 7:26 am and the last at 11:35 pm EDT, by Cincinnati Police Department's published record.

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

12a1a2a3a4a5a6a7a8a9a10a11a12p1p2p3p4p5p6p7p8p9p10p11p

Why, in the agency's words

  1. Call for service100%

Flights, in order

45 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 (EDT)PurposeAirborneFlight
7:26 amCall for service20 min9a551485
8:23 amCall for service15 min20a7a4fe
8:39 amCall for service1 min 02 s80834349
8:46 amCall for service18 min2a0b1f27
10:04 amCall for service21 min79df24bb
10:33 amCall for service8 min591d0ba5
11:07 amCall for service12 min0cc71062
11:25 amCall for service18 minb1e5cf28
11:29 amCall for service21 min4068a233
11:44 amCall for service1 min 14 s6e9dc494
11:45 amCall for service23 mina3f15322
12:03 pmCall for service20 minb2fce303
12:09 pmCall for service18 minfa84e751
12:18 pmCall for service19 min61096a87
1:03 pmCall for service11 mine74c9614
1:13 pmCall for service15 mine8d3ef99
1:47 pmCall for service1 min 07 s8e9ba621
1:53 pmCall for service7 mine66104c7
2:06 pmCall for service15 min574bf547
2:15 pmCall for service17 min0442cf3f
2:15 pmCall for service37 sdcf3e482
2:22 pmCall for service18 minf42f5bca
2:23 pmCall for service19 mina6535bd9
2:35 pmCall for service18 mindb524dd4
2:54 pmCall for service5 mine23cde13
3:02 pmCall for service7 min03951649
3:05 pmCall for service8 min7a7f7c73
3:16 pmCall for service4 min5d1b9003
3:18 pmCall for service8 min5873b58e
3:22 pmCall for service5 min25b36d39
4:27 pmCall for service11 min35e4d4a1
4:38 pmCall for service16 mind89b017b
5:04 pmCall for service22 mind141150c
5:11 pmCall for service9 min4f478ced
5:22 pmCall for service6 min47e62a7b
5:51 pmCall for service10 minb5c22ff2
5:55 pmCall for service14 min1602510a
6:11 pmCall for service11 minaaaec2e6
6:57 pmCall for service13 min7ca1ca59
7:03 pmCall for service6 mine99eed50
9:09 pmCall for service14 minea2a88fa
9:56 pmCall for service10 mind8178a25
10:48 pmCall for service15 minb90bc585
11:32 pmCall for service12 min38cf2077
11:35 pmCall for service15 min11a9962c

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