CityDroneWatch
  1. CityDroneWatch
  2. Ohio
  3. Cincinnati
  4. September 2025
  5. 11

Cincinnati, Ohio · one day

Thursday 11 September 2025

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

43

drone flights over Cincinnati that day.

7:35 am

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

12 min

median flight. Half were shorter.

Cincinnati police drones flew 43 times on Thursday 11 September 2025, the first at 7:35 am and the last at 8:35 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
7:35 amCall for service15 min24efc2c9
7:59 amCall for service46 sd3f7c8ab
8:10 amCall for service19 minc26afc86
8:13 amCall for service4 mine8411172
8:22 amCall for service10 min6a63a566
8:44 amCall for service22 min3a99a4c6
9:11 amCall for service21 mind1fec0a9
9:19 amCall for service12 mindc470ab1
9:45 amCall for service1 min 11 scbe5e273
9:59 amCall for service22 min6b6f6bc1
10:08 amCall for service18 mina3136a99
10:39 amCall for service19 min53db3d4f
11:18 amCall for service22 minde0a60f2
11:42 amCall for service43 sba3838f0
11:46 amCall for service20 min269ac872
12:48 pmCall for service9 mine2672ff6
1:19 pmCall for service3 minc577fe68
1:45 pmCall for service20 minef5f3010
1:46 pmCall for service21 minc75f47cd
2:10 pmCall for service7 min9dd648dd
2:17 pmCall for service3 min496ba89a
2:22 pmCall for service18 min1d9077b3
2:27 pmCall for service16 min5a6a8533
2:53 pmCall for service1 min 37 sa97440c3
3:10 pmCall for service20 mind2884333
3:26 pmCall for service6 minad2554c8
4:12 pmCall for service16 minbcf70a84
4:17 pmCall for service5 min1a4d5011
5:01 pmCall for service15 minb9f5c7cc
5:12 pmCall for service8 mind19e3508
5:21 pmCall for service15 mina21a315a
5:31 pmCall for service11 min349714bb
6:14 pmCall for service22 min8f7aa2a9
6:16 pmCall for service9 min7da24221
6:27 pmCall for service4 min9397e15e
6:37 pmCall for service11 minad94a244
6:42 pmCall for service6 mineef8a387
6:52 pmCall for service14 min29ed073e
7:56 pmCall for service12 min743446a9
8:03 pmCall for service11 min4fd20114
8:17 pmCall for service17 min775df6a7
8:20 pmCall for service9 min4f1066da
8:35 pmCall for service6 minf4fb8a3e

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