CityDroneWatch
  1. CityDroneWatch
  2. Ohio
  3. Cincinnati
  4. October 2025
  5. 13

Cincinnati, Ohio · one day

Monday 13 October 2025

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

45

drone flights over Cincinnati that day.

7:24 am

first takeoff; the last was at 8:09 pm.

13 min

median flight. Half were shorter.

Cincinnati police drones flew 45 times on Monday 13 October 2025, the first at 7:24 am and the last at 8:09 pm EDT, by Cincinnati Police Department's published record.

45 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:24 amCall for service7 min3850f8e8
7:42 amCall for service11 min94ec68ad
8:31 amCall for service19 mincda41bd9
8:46 amCall for service10 min123b2a25
9:14 amCall for service11 minb33e5f8a
9:32 amCall for service12 min458300cb
9:54 amCall for service12 min0ba5d167
10:46 amCall for service8 min61628baf
11:06 amCall for service20 mindb74d010
11:08 amCall for service14 mindf9c797a
11:32 amCall for service10 min89c089f1
11:50 amCall for service7 minc8186a83
12:00 pmCall for service21 minaf718043
12:23 pmCall for service21 min5708b4e1
12:52 pmCall for service19 min3ff69fc7
1:01 pmCall for service1 min 40 s6c44ead7
1:07 pmCall for service12 min359a7b7c
1:33 pmCall for service7 min6cee54df
2:03 pmCall for service20 min21d58ed9
2:14 pmCall for service6 min66ee0c0b
2:22 pmCall for service18 min50cfa8e4
2:35 pmCall for service12 mina65c8042
2:47 pmCall for service8 mindb7beb9b
3:09 pmCall for service19 min6335f54f
3:27 pmCall for service19 minfd2deae6
3:52 pmCall for service3 min81ec5511
3:57 pmCall for service14 min7c096403
4:07 pmCall for service9 min3fe4d299
4:15 pmCall for service7 mine139dc6d
4:23 pmCall for service8 min4295b73a
4:34 pmCall for service20 mind265db5f
4:57 pmCall for service19 mine05ebb89
5:05 pmCall for service19 min96edaf01
5:18 pmCall for service19 min4fa9e4aa
5:45 pmCall for service11 min30142813
6:10 pmCall for service14 min67353d76
6:22 pmCall for service20 min554de308
6:31 pmCall for service9 minc556a45c
6:44 pmCall for service10 min15e6389d
6:51 pmCall for service13 min2fe32335
7:06 pmCall for service16 min7a3bc75c
7:08 pmCall for service15 min1a257bad
7:47 pmCall for service13 min59fa6bf2
7:59 pmCall for service15 minbbcca4f4
8:09 pmCall for service16 mind4e8f518

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