CityDroneWatch
  1. CityDroneWatch
  2. Ohio
  3. Toledo
  4. August 2026
  5. 5

Toledo, Ohio · one day

Wednesday 5 August 2026

24 drone flights from Toledo Police Department's published record.

24

drone flights over Toledo that day.

1:43 am

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

17 min

median flight. Half were shorter.

Toledo police drones flew 24 times on Wednesday 5 August 2026, the first at 1:43 am and the last at 11:42 pm EDT, by Toledo Police Department's published record.

24 drawable flights of 24. 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. Other96%
  2. Not stated4%

Flights, in order

24 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
1:43 amOther26 minTOLOHPD-
2:17 amOther28 minTOLOHPD-
2:47 amOther29 minTOLOHPD-
7:30 amOther4 minTOLOHPD-
8:05 amOther21 minTOLOHPD-
8:54 amOther23 minTOLOHPD-
9:50 amNot stated2 minTOLOHPD-
10:28 amOther9 minTOLOHPD-
11:20 amOther8 minTOLOHPD-
11:54 amOther13 minTOLOHPD-
12:16 pmOther10 minTOLOHPD-
12:39 pmOther14 minTOLOHPD-
1:06 pmOther7 minTOLOHPD-
2:56 pmOther17 minTOLOHPD-
3:41 pmOther14 minTOLOHPD-
5:16 pmOther17 minTOLOHPD-
7:40 pmOther20 minTOLOHPD-
8:23 pmOther17 minTOLOHPD-
8:45 pmOther17 minTOLOHPD-
9:14 pmOther10 minTOLOHPD-
9:38 pmOther29 minTOLOHPD-
10:37 pmOther28 minTOLOHPD-
11:08 pmOther30 minTOLOHPD-
11:42 pmOther18 minTOLOHPD-

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