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

Dearborn, Michigan · one day

Wednesday 3 June 2026

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

48

drone flights over Dearborn that day.

12:58 am

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

9 min

median flight. Half were shorter.

Dearborn police drones flew 48 times on Wednesday 3 June 2026, the first at 12:58 am and the last at 11:33 pm EDT, by Dearborn Police Department's published record.

48 drawable flights of 48. 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. Search35%
  2. Traffic and crashes27%
  3. Patrol support17%
  4. Training and testing15%
  5. Other4%
  6. Call for service2%

Flights, in order

48 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:58 amPatrol support14 min563a2759
3:32 amPatrol support6 minf97def98
5:58 amTraffic and crashes10 min051952ae
6:15 amTraffic and crashes10 min7c6070e0
7:05 amOther10 minf3158cf6
7:17 amOther9 min414d21cb
7:30 amTraffic and crashes9 min2ea94167
8:02 amTraining and testing10 mincc8e8600
8:13 amTraining and testing7 min62e8f674
8:40 amTraffic and crashes6 min730fe23c
8:52 amSearch4 mincd22fe32
9:00 amTraffic and crashes9 minb62f9608
9:15 amCall for service11 minf3b974c7
9:23 amTraining and testing2 min925c8e90
9:28 amPatrol support7 min7b648125
9:52 amSearch13 min07e8d948
10:53 amTraining and testing9 mine41dfd87
10:58 amTraining and testing12 minae64935b
11:27 amTraffic and crashes7 min2b433d2c
11:45 amTraffic and crashes8 mina97df188
11:53 amPatrol support8 minba2309ea
12:02 pmPatrol support3 minb53a3ff7
12:06 pmTraining and testing4 minb6062e6f
12:12 pmSearch4 minb1c3bc3f
12:46 pmSearch7 min895ae4ac
1:06 pmPatrol support15 min9bb200f4
1:13 pmPatrol support16 mina688714f
1:32 pmPatrol support11 min50a3d38c
1:50 pmTraining and testing12 minbac244f6
2:37 pmSearch7 minab34d7f5
3:00 pmSearch7 min77b53b84
3:22 pmSearch8 min687e4729
3:41 pmSearch14 min47b8a043
4:00 pmTraffic and crashes12 minc0a9de55
4:39 pmTraffic and crashes3 mincf13b788
4:47 pmSearch13 min02d09582
5:04 pmSearch16 min26514ff4
5:23 pmSearch13 minec601789
5:54 pmSearch11 min52ce98d5
6:32 pmSearch6 minb71cfb78
6:51 pmSearch15 min0900d771
7:19 pmSearch6 min914fd754
7:28 pmTraffic and crashes4 min0b53151e
7:35 pmSearch11 minde9e1b3a
9:06 pmSearch13 min3a15ee56
10:14 pmTraffic and crashes9 min1fa4afc1
10:38 pmTraffic and crashes7 mine630c5c4
11:33 pmTraffic and crashes9 min3d815c63

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.