CityDroneWatch
  1. CityDroneWatch
  2. Michigan
  3. Dearborn
  4. August 2026
  5. 25

Dearborn, Michigan · one day

Tuesday 25 August 2026

38 drone flights from Dearborn Police Department's published record.

38

drone flights over Dearborn that day.

12:37 am

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

7 min

median flight. Half were shorter.

Dearborn police drones flew 38 times on Tuesday 25 August 2026, the first at 12:37 am and the last at 11:50 pm EDT, by Dearborn Police Department's published record.

38 drawable flights of 38. 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. Patrol support37%
  2. Search26%
  3. Training and testing26%
  4. Call for service8%
  5. Traffic and crashes3%

Flights, in order

38 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:37 amSearch9 min9a74d4ee
1:11 amSearch20 min90855c8a
2:28 amSearch17 mine058ce12
3:27 amCall for service14 minf6bdd075
5:57 amPatrol support7 min1624f2a8
6:32 amPatrol support6 minc901c78d
6:43 amCall for service12 min13c758c1
8:11 amCall for service7 minf7f1fa5a
8:19 amTraffic and crashes7 min403a09eb
9:37 amTraining and testing5 minea472519
9:42 amPatrol support7 min1acfe8ba
9:49 amTraining and testing7 minb53f455a
9:59 amTraining and testing9 minfd5313f1
10:14 amTraining and testing10 mincd6351b4
10:25 amTraining and testing5 min09fef082
11:11 amPatrol support9 minf1695415
11:30 amPatrol support9 minbf1b9ef6
11:37 amSearch7 min5625d8d9
11:43 amTraining and testing3 minf197aabb
12:09 pmTraining and testing2 minc56d88e2
12:16 pmTraining and testing7 min55961a03
12:38 pmPatrol support7 min14dc3e3c
12:45 pmTraining and testing47 s8d3f13ff
12:47 pmTraining and testing6 mina1f1be0c
1:05 pmPatrol support4 min2c56cf61
1:41 pmPatrol support6 minbdc4cdef
5:52 pmPatrol support7 mine7035ecf
6:14 pmPatrol support10 min1f30e1cd
6:29 pmPatrol support7 min09cb6efc
6:40 pmPatrol support8 mine86155a9
8:39 pmSearch12 min5b833783
8:56 pmSearch8 min6249f638
9:07 pmSearch15 minaccc672d
9:51 pmPatrol support7 min772f8cf8
10:20 pmSearch8 min0d1e523b
10:51 pmSearch14 mind2b6dda2
11:31 pmSearch16 min9444fe97
11:50 pmPatrol support19 min29343f57

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.