CityDroneWatch
  1. CityDroneWatch
  2. Ohio
  3. Cincinnati
  4. March 2026
  5. 3

Cincinnati, Ohio · one day

Tuesday 3 March 2026

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

43

drone flights over Cincinnati that day.

1:33 am

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

7 min

median flight. Half were shorter.

Cincinnati police drones flew 43 times on Tuesday 3 March 2026, the first at 1:33 am and the last at 11:33 pm EST, 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, EST.

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 (EST)PurposeAirborneFlight
1:33 amCall for service1 min 32 s532f66f9
1:36 amCall for service1 min 21 sb813c493
1:40 amCall for service1 min 21 s1534dfbc
10:09 amCall for service17 minc1f47164
10:26 amCall for service22 min8e81d862
10:53 amCall for service19 min2044762a
11:09 amCall for service16 min94d46c3e
12:25 pmCall for service11 min27c50cfc
1:35 pmCall for service4 min6b7b416d
1:41 pmCall for service4 min4fb5429c
1:46 pmCall for service4 minca8388c7
1:51 pmCall for service2 min467987d8
2:32 pmCall for service6 mina43ba087
3:07 pmCall for service10 min65e1c7bb
3:11 pmCall for service19 min8b2d03f1
3:24 pmCall for service16 min9ac76dcc
3:30 pmCall for service15 min345e40e5
3:47 pmCall for service17 min4a64264c
3:50 pmCall for service4 minc30fa1fc
3:58 pmCall for service5 mindb2339b4
4:04 pmCall for service1 min 58 s54ced689
4:08 pmCall for service1 min 21 s8324add2
4:08 pmCall for service20 min5c52123e
4:10 pmCall for service1 min 10 s5421a3be
4:20 pmCall for service7 mince8aa496
4:23 pmCall for service17 min7c49e3ac
4:37 pmCall for service7 mine983e417
4:44 pmCall for service14 min500104aa
4:55 pmCall for service9 minb046cbcb
5:18 pmCall for service1 min 39 sc2405deb
5:49 pmCall for service7 minb2ff11b7
5:51 pmCall for service5 min65959d13
5:58 pmCall for service1 min 55 s97436891
7:37 pmCall for service19 min8d77cfbb
7:46 pmCall for service10 min601c99fd
8:04 pmCall for service19 minde657dcf
8:25 pmCall for service9 min10e37dfe
8:44 pmCall for service19 minabaaf7e9
9:05 pmCall for service19 min89bc5bd1
9:44 pmCall for service3 min78198fbe
9:56 pmCall for service13 mina7be02e1
11:07 pmCall for service3 min5c403d4b
11:33 pmCall for service7 min9e6e7499

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