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

Cincinnati, Ohio · one day

Saturday 1 November 2025

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

44

drone flights over Cincinnati that day.

12:27 am

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

12 min

median flight. Half were shorter.

Cincinnati police drones flew 44 times on Saturday 1 November 2025, the first at 12:27 am and the last at 11:59 pm EDT, by Cincinnati Police Department's published record.

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

44 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
12:27 amCall for service9 min1c02bda8
12:42 amCall for service16 minfef5d9e9
12:54 amCall for service11 min670b6194
1:03 amCall for service15 min256f5054
6:16 amCall for service11 min1074ff57
6:59 amCall for service14 min56410056
8:13 amCall for service20 min4e8e0539
8:49 amCall for service5 min7d6bef0b
9:14 amCall for service17 min5cf07006
9:36 amCall for service14 minc9402dc9
9:39 amCall for service12 min08f3dd44
9:53 amCall for service7 minfca2cffb
10:00 amCall for service12 min66d4dc5c
10:17 amCall for service5 mina59c202a
10:22 amCall for service6 min9c677676
10:24 amCall for service12 min23b07e2a
10:37 amCall for service15 minf222838c
11:08 amCall for service13 min2cd2f1c9
12:47 pmCall for service5 min0e062402
1:38 pmCall for service21 minab86e604
1:49 pmCall for service17 min76b996da
2:54 pmCall for service12 min0f9b3ac8
4:01 pmCall for service19 min42254599
4:09 pmCall for service13 mindbf4c5f2
4:25 pmCall for service20 min576cd3f3
5:10 pmCall for service16 min0f3ecdb5
5:27 pmCall for service10 min8568335a
6:01 pmCall for service11 min6c9c7db8
6:29 pmCall for service14 min0fbe50d9
7:17 pmCall for service8 min823b9e81
7:44 pmCall for service10 min1c171978
8:00 pmCall for service5 minaebb4abd
8:06 pmCall for service13 minc9d3ac01
9:11 pmCall for service11 minc835972e
9:15 pmCall for service8 min9c63b87e
9:49 pmCall for service11 min0b66fc9a
10:07 pmCall for service15 min7c457543
10:23 pmCall for service10 min0d389c01
10:29 pmCall for service16 min5f9e7d9b
10:41 pmCall for service11 min5b184642
10:49 pmCall for service16 min9456c9fe
11:33 pmCall for service7 min86a24c32
11:50 pmCall for service17 min796f65af
11:59 pmCall for service10 min36f1b788

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