CityDroneWatch
  1. CityDroneWatch
  2. Michigan
  3. Dearborn
  4. June 2026
  5. 20

Dearborn, Michigan · one day

Saturday 20 June 2026

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

50

drone flights over Dearborn that day.

12:00 am

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

9 min

median flight. Half were shorter.

Dearborn police drones flew 50 times on Saturday 20 June 2026, the first at 12:00 am and the last at 11:10 pm EDT, by Dearborn Police Department's published record.

50 drawable flights of 50. 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. Search42%
  2. Patrol support32%
  3. Traffic and crashes16%
  4. Call for service6%
  5. Other4%

Flights, in order

50 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:00 amPatrol support11 min45cd3dc8
12:02 amPatrol support20 min626892c3
12:20 amPatrol support15 min98415bb2
1:41 amSearch10 min43e57dca
1:57 amSearch5 min856f365f
2:08 amPatrol support6 mindac934bc
2:45 amSearch16 minfc63940e
3:55 amTraffic and crashes11 min8eb1faa4
7:05 amSearch9 min977487d7
7:19 amTraffic and crashes6 min86d0f73a
9:07 amCall for service8 min54f226d6
9:37 amPatrol support9 min1eaa4e8e
9:45 amPatrol support4 min99ae983f
9:48 amSearch7 min76d0491c
9:59 amPatrol support6 minced9f237
10:18 amTraffic and crashes6 minb988ed5e
10:30 amSearch12 minae07b32f
11:22 amPatrol support3 min3aa8fc7d
11:25 amOther1 min 52 s02c40809
11:37 amPatrol support5 min5e45252c
11:47 amCall for service5 min6a6acefb
11:50 amPatrol support15 min6598df8f
12:12 pmPatrol support3 min35664f9d
12:35 pmSearch15 min354f8e68
12:54 pmOther1 min 17 s449359ee
12:57 pmTraffic and crashes4 minf4ced5b5
1:03 pmSearch8 min486b7dc0
1:27 pmPatrol support3 minb127d87e
1:38 pmCall for service13 mindfc77d7e
1:50 pmSearch19 min7f8dd28a
2:14 pmSearch14 min673621ce
2:53 pmPatrol support5 min08bcd1b8
3:23 pmSearch12 min9925f71d
3:52 pmSearch7 min867cab58
4:35 pmTraffic and crashes5 min0a8509f2
4:42 pmTraffic and crashes14 mina61f827a
4:57 pmSearch22 minff3296ee
5:19 pmSearch20 min1f20c1da
6:34 pmTraffic and crashes4 min9992c780
7:24 pmSearch6 minc41f8bb8
7:37 pmSearch6 min930a571a
7:59 pmTraffic and crashes14 minc5cd7543
8:36 pmPatrol support12 min018253a9
8:58 pmSearch15 mind8c86bf5
9:16 pmSearch5 min97bfeff5
9:29 pmSearch11 min1cdd9cb9
9:42 pmSearch18 min0f2374ef
9:56 pmPatrol support9 min136e3128
10:10 pmSearch9 min8565eeae
11:10 pmPatrol support15 minb773732f

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.