CityDroneWatch
  1. CityDroneWatch
  2. Ohio
  3. Cincinnati
  4. September 2026
  5. 12

Cincinnati, Ohio · one day

Saturday 12 September 2026

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

44

drone flights over Cincinnati that day.

12:33 am

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

11 min

median flight. Half were shorter.

Cincinnati police drones flew 44 times on Saturday 12 September 2026, the first at 12:33 am and the last at 11:45 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:33 amCall for service19 min23302bfb
12:47 amCall for service10 mincdf51fd7
12:59 amCall for service16 min866d06f1
1:23 amCall for service17 min29b6b70f
1:42 amCall for service6 min3a8733a3
1:49 amCall for service13 minc446ca82
2:09 amCall for service9 minaab7c3e8
2:30 amCall for service7 min62a94e6b
2:45 amCall for service13 min84dd1576
3:23 amCall for service11 min95dcdb40
4:28 amCall for service7 min1c3a4186
6:15 amCall for service3 min238fe3f7
6:18 amCall for service3 min55f3ee5c
6:20 amCall for service8 mina58da708
6:26 amCall for service11 minbc8d6d2a
6:45 amCall for service19 mind9dd35a2
7:07 amCall for service2 min1ca35086
7:10 amCall for service3 min7b83637f
7:46 amCall for service8 min5049d793
7:51 amCall for service6 min84173460
7:58 amCall for service1 min 05 s27f0603c
7:59 amCall for service9 mindbab8ae7
8:22 amCall for service8 min41df0b25
8:55 amCall for service4 min09b4596e
9:00 amCall for service18 min9ec5270e
9:38 amCall for service13 min9935fa94
10:16 amCall for service11 mindeddcd0a
10:29 amCall for service16 min336c697b
10:47 amCall for service17 minea2e5c32
11:06 amCall for service10 mine78c823a
7:23 pmCall for service18 min496a6850
7:44 pmCall for service5 min116137a5
8:08 pmCall for service8 minfd75bcf4
8:16 pmCall for service11 min2af9c4c9
8:57 pmCall for service14 mindff3e69e
9:10 pmCall for service18 min8d96238b
9:31 pmCall for service13 min14942f9b
9:47 pmCall for service11 minc403aaef
10:15 pmCall for service10 min4e4b80d7
10:23 pmCall for service18 min3eb7594a
10:40 pmCall for service21 minab09cdb4
10:54 pmCall for service15 min26577e85
11:31 pmCall for service15 min3e982656
11:45 pmCall for service16 min270341e3

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