CityDroneWatch
  1. CityDroneWatch
  2. Michigan
  3. Dearborn
  4. April 2026
  5. 28

Dearborn, Michigan · one day

Tuesday 28 April 2026

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

42

drone flights over Dearborn that day.

12:09 am

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

7 min

median flight. Half were shorter.

Dearborn police drones flew 42 times on Tuesday 28 April 2026, the first at 12:09 am and the last at 11:45 pm EDT, by Dearborn Police Department's published record.

42 drawable flights of 42. 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. Training and testing33%
  2. Search24%
  3. Traffic and crashes19%
  4. Call for service12%
  5. Patrol support7%
  6. Assisting another agency5%

Flights, in order

42 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:09 amTraffic and crashes5 minbb04ab61
5:59 amTraining and testing1 min 29 s8fa177b2
6:02 amTraining and testing3 minc5bd431a
6:11 amTraining and testing3 minb0713528
6:24 amPatrol support13 mind462a968
7:32 amTraining and testing53 s3c64c133
7:41 amTraining and testing1 min 43 s49eea6e4
7:48 amTraining and testing3 mina2629e91
8:07 amTraining and testing3 min46c538d9
8:11 amTraining and testing4 mina29ba806
8:19 amTraining and testing2 min2df45fc3
8:25 amTraining and testing3 min7a8de6a3
10:13 amTraffic and crashes8 min1ad6c8ce
11:09 amSearch19 min8616195b
11:29 amSearch9 mind6fe4913
12:02 pmPatrol support3 minc086b12f
12:13 pmSearch5 minfd51138d
12:19 pmTraining and testing3 min42ad5f2e
12:27 pmTraining and testing7 minb7251bbe
3:11 pmTraining and testing7 min8c9a7b4f
3:20 pmTraining and testing7 min95868da6
3:51 pmSearch6 mine4337255
4:15 pmSearch12 min7a67dc15
4:34 pmSearch14 min650b840c
4:57 pmSearch17 mine5535f7f
5:32 pmAssisting another agency17 minc1da89a2
7:06 pmSearch3 min0751b650
7:10 pmAssisting another agency6 mind712fa14
7:19 pmSearch12 min4ef772db
7:33 pmSearch7 min6d5ed1dc
8:06 pmCall for service9 min50973b9e
8:19 pmCall for service13 minf0b462d1
8:34 pmTraffic and crashes10 minf99ea9a7
9:01 pmPatrol support7 mind7535b4d
9:47 pmTraffic and crashes5 min5096fc37
10:00 pmTraffic and crashes5 minb60d83c8
10:13 pmCall for service16 mina8804612
10:36 pmTraffic and crashes9 min2677497f
10:51 pmTraffic and crashes7 minb8a08df1
11:05 pmTraffic and crashes6 mince433d91
11:19 pmCall for service8 min55f91410
11:45 pmCall for service9 min6b16ea5a

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.