CityDroneWatch
  1. CityDroneWatch
  2. Ohio
  3. Cincinnati
  4. February 2026
  5. 21

Cincinnati, Ohio · one day

Saturday 21 February 2026

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

45

drone flights over Cincinnati that day.

12:10 am

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

12 min

median flight. Half were shorter.

Cincinnati police drones flew 45 times on Saturday 21 February 2026, the first at 12:10 am and the last at 11:21 pm EST, by Cincinnati Police Department's published record.

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

45 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
12:10 amCall for service15 min7eaf8c9c
12:14 amCall for service10 min28ebad67
12:39 amCall for service12 mina816b0c1
12:54 amCall for service12 min0594c2ad
1:02 amCall for service8 min9593eb31
1:40 amCall for service10 minf5980673
1:54 amCall for service9 min0a88d94f
2:00 amCall for service10 min7a7edee8
2:19 amCall for service17 minf3d070bd
2:37 amCall for service10 min4608944c
4:42 amCall for service5 min83efccef
4:58 amCall for service17 min4d5f0a90
5:16 amCall for service9 min5cdcb9a4
6:19 amCall for service13 minf8111e33
7:31 amCall for service19 min0221667a
8:31 amCall for service13 min65fe7d5c
9:54 amCall for service19 min37067a5e
10:40 amCall for service11 mine3d3e2c5
11:13 amCall for service17 min257bc90d
11:36 amCall for service16 minde239f3f
11:54 amCall for service9 minc5ce0841
2:28 pmCall for service1 min 19 scdb8cbda
2:53 pmCall for service12 min73baf6a1
3:21 pmCall for service18 min716682d1
3:22 pmCall for service9 mind700ac38
4:00 pmCall for service5 min61d5c71a
4:11 pmCall for service12 min1de8342c
4:24 pmCall for service24 mincdeaf9d7
4:27 pmCall for service2 minc473be57
5:09 pmCall for service7 min1ddacefe
5:37 pmCall for service19 minc2361503
6:03 pmCall for service17 mina159dca6
6:38 pmCall for service7 min944a83ad
6:55 pmCall for service13 minc3c5e9bf
7:33 pmCall for service17 min57c05837
7:49 pmCall for service21 min982c22d1
8:13 pmCall for service12 min462b36e0
8:59 pmCall for service15 min2d4acbda
10:03 pmCall for service15 mine539a113
10:23 pmCall for service19 min498e5a9a
10:47 pmCall for service8 min07c1c461
10:49 pmCall for service13 minff23f38f
11:05 pmCall for service15 minccb15ee1
11:06 pmCall for service11 min1a43164c
11:21 pmCall for service14 minb67d42b1

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: see the about page. See about this site for the sources and the publication rules.