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

Cincinnati, Ohio · one day

Thursday 18 September 2025

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

44

drone flights over Cincinnati that day.

7:38 am

first takeoff; the last was at 8:36 pm.

13 min

median flight. Half were shorter.

Cincinnati police drones flew 44 times on Thursday 18 September 2025, the first at 7:38 am and the last at 8:36 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
7:38 amCall for service15 minf4252f5e
8:37 amCall for service12 min34c1ec50
8:42 amCall for service23 min8adc8a73
8:58 amCall for service17 mind4ade295
9:17 amCall for service11 min94986cc4
9:32 amCall for service11 mind3d81f52
10:00 amCall for service9 mind60bbae5
10:16 amCall for service10 min0484df57
10:34 amCall for service6 min7b536a53
10:39 amCall for service19 mind84043c0
11:02 amCall for service16 min65510ea6
11:16 amCall for service19 mine6d3d9ce
11:38 amCall for service14 min95979005
12:05 pmCall for service6 min19d2292d
12:31 pmCall for service22 min9d0e7da6
12:47 pmCall for service18 min5c6f8f1e
12:48 pmCall for service21 minb3cfc755
1:07 pmCall for service18 mindd739edd
1:19 pmCall for service5 mine71e51ed
1:38 pmCall for service21 mind986e334
1:57 pmCall for service14 min90286835
2:10 pmCall for service12 min1634a38e
2:14 pmCall for service8 min6cf9a4be
2:22 pmCall for service17 minda2b0add
2:29 pmCall for service10 min4fc5e020
2:38 pmCall for service13 min017af76e
3:01 pmCall for service13 min6151dffc
3:02 pmCall for service7 minc550b49b
3:41 pmCall for service18 min9adc7201
3:56 pmCall for service12 min2bcb207e
4:18 pmCall for service6 min4e46b04f
4:50 pmCall for service14 min788d8c41
5:00 pmCall for service11 min155ea865
5:13 pmCall for service9 min894a5d9e
5:54 pmCall for service9 mindfa5b57d
7:03 pmCall for service10 minfb912d04
7:11 pmCall for service20 min680b29e8
7:16 pmCall for service15 min4d153b6a
7:44 pmCall for service13 minff54cf44
8:13 pmCall for service8 min38331593
8:13 pmCall for service14 min34839ae6
8:22 pmCall for service8 minbc5fb98e
8:32 pmCall for service6 min9523cdad
8:36 pmCall for service16 minc670a50b

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