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

Cincinnati, Ohio · one day

Friday 5 September 2025

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

41

drone flights over Cincinnati that day.

7:37 am

first takeoff; the last was at 9:38 pm.

16 min

median flight. Half were shorter.

Cincinnati police drones flew 41 times on Friday 5 September 2025, the first at 7:37 am and the last at 9:38 pm EDT, by Cincinnati Police Department's published record.

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

41 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:37 amCall for service14 min7ede38dd
7:52 amCall for service11 minff8610ec
8:08 amCall for service10 min24db5b8f
8:24 amCall for service21 min30dab592
8:56 amCall for service21 mind30f0abd
10:19 amCall for service8 minbee83872
11:18 amCall for service14 minab40f5ec
11:52 amCall for service19 min8d6d39ad
12:05 pmCall for service22 min0e6b8385
12:14 pmCall for service8 minae026177
12:29 pmCall for service16 mincf7a882c
12:46 pmCall for service22 minf1f6bc17
1:06 pmCall for service21 mineb041d82
1:22 pmCall for service21 min375e05db
1:40 pmCall for service18 mincd8f051f
2:25 pmCall for service45 s13722207
2:32 pmCall for service9 min9622d34e
2:53 pmCall for service17 min7c9b2f92
2:55 pmCall for service13 mind604371f
3:25 pmCall for service12 min4806fd46
3:27 pmCall for service1 min 11 sa83a1087
3:31 pmCall for service18 min510cb0dc
3:44 pmCall for service16 min3209bade
4:06 pmCall for service8 min7b6ac7c8
4:07 pmCall for service14 mincc903c05
4:39 pmCall for service21 min9e85488c
4:41 pmCall for service1 min 19 s5ffb4721
4:41 pmCall for service18 min9d4c7a56
5:04 pmCall for service20 min4f27fe73
5:35 pmCall for service22 minadaf3198
5:38 pmCall for service13 mind78bce5a
6:20 pmCall for service21 min52f22e09
6:40 pmCall for service15 minc55ffee6
6:58 pmCall for service17 min5cfa2959
7:25 pmCall for service10 min2b98d47b
7:38 pmCall for service18 min7fcdd94e
8:05 pmCall for service16 min9cff2378
8:51 pmCall for service8 min4d0cbbce
9:01 pmCall for service17 min20237db0
9:24 pmCall for service12 min237b83df
9:38 pmCall for service12 minf2efd161

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