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

Cincinnati, Ohio · one day

Tuesday 14 October 2025

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

43

drone flights over Cincinnati that day.

8:24 am

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

14 min

median flight. Half were shorter.

Cincinnati police drones flew 43 times on Tuesday 14 October 2025, the first at 8:24 am and the last at 8:51 pm EDT, 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, EDT.

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 (EDT)PurposeAirborneFlight
8:24 amCall for service13 min3a302708
8:40 amCall for service21 mind1a5eaf0
8:48 amCall for service14 mineb4e4365
9:33 amCall for service15 minb0f75a27
9:57 amCall for service20 min94b68f54
10:22 amCall for service7 mindf860383
10:28 amCall for service12 min62b3b83c
10:29 amCall for service15 minafdbc8f5
11:02 amCall for service14 min28442327
11:09 amCall for service12 min145abaae
12:10 pmCall for service17 mina9a98b97
12:26 pmCall for service3 min214c0aeb
12:28 pmCall for service9 min0848c5bf
12:45 pmCall for service19 min60bbcaba
12:57 pmCall for service11 mine8ce3e89
2:31 pmCall for service21 min83a1d884
2:44 pmCall for service21 min9b1cff7e
2:58 pmCall for service15 mine3255052
3:05 pmCall for service18 min93d71be4
3:18 pmCall for service13 min175e7053
3:41 pmCall for service17 min2514f977
3:48 pmCall for service20 mine3891fa3
4:03 pmCall for service20 minb064501f
4:19 pmCall for service3 min37b62620
4:27 pmCall for service14 mine43da2fa
4:38 pmCall for service16 min5768d5b0
4:55 pmCall for service20 mine2392c10
4:59 pmCall for service19 mine40a2233
5:47 pmCall for service12 min81247ca7
5:51 pmCall for service15 min212c5ccb
6:12 pmCall for service15 minb5272b37
6:33 pmCall for service18 min899ca2c1
6:43 pmCall for service9 min30570f96
6:58 pmCall for service6 min0f249741
7:13 pmCall for service7 min3a979db5
7:31 pmCall for service5 min2d343086
7:35 pmCall for service11 mind36e90b1
7:40 pmCall for service16 min02915046
7:48 pmCall for service12 mined70ac56
8:00 pmCall for service3 min6d7657d1
8:07 pmCall for service15 min8d88b8a8
8:37 pmCall for service13 min53839692
8:51 pmCall for service14 minfcee9821

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