CityDroneWatch
  1. CityDroneWatch
  2. Michigan
  3. Dearborn
  4. May 2026
  5. 27

Dearborn, Michigan · one day

Wednesday 27 May 2026

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

55

drone flights over Dearborn that day.

3:26 am

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

11 min

median flight. Half were shorter.

Dearborn police drones flew 55 times on Wednesday 27 May 2026, the first at 3:26 am and the last at 11:15 pm EDT, by Dearborn Police Department's published record.

55 drawable flights of 55. 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 support47%
  2. Search44%
  3. Traffic and crashes5%
  4. Training and testing4%

Flights, in order

55 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
3:26 amSearch10 min7e3274ff
3:40 amPatrol support6 minb5b7a603
6:41 amPatrol support15 minf823aa7f
7:24 amPatrol support6 min721d0736
8:02 amPatrol support21 min097f8b7d
8:24 amPatrol support14 min62042591
8:25 amPatrol support5 minef9cca14
8:39 amPatrol support15 min57218037
8:48 amPatrol support20 min38e692cb
9:09 amPatrol support22 min3c2e6612
9:35 amPatrol support22 minc23e80c3
9:58 amPatrol support17 min7563b62a
10:16 amPatrol support3 mindcb69964
10:19 amPatrol support6 min843f4619
10:39 amSearch8 min13c7b392
11:32 amPatrol support22 minfc934cc7
11:53 amPatrol support20 min40bddf10
12:15 pmPatrol support19 min413e5f05
12:21 pmPatrol support6 minfc9000c7
12:30 pmPatrol support17 min22dec6fa
12:39 pmPatrol support18 min8dab6c06
12:54 pmPatrol support19 min3e7bd2dd
1:12 pmSearch19 min99d89d31
1:15 pmPatrol support3 min4ba8aa9f
1:31 pmPatrol support16 min1bc1b394
2:11 pmSearch3 min630def78
2:15 pmSearch8 min73d8d4ba
2:18 pmTraffic and crashes8 mind0c4f228
2:20 pmTraining and testing8 min6f660362
2:56 pmSearch13 minc6b17be6
3:02 pmTraining and testing1 min 21 s449e57ad
3:08 pmSearch16 mind96660b1
3:11 pmTraffic and crashes4 min87a2459e
4:01 pmSearch17 min53c98910
4:11 pmSearch9 mina4572852
4:21 pmSearch5 minb0abffa8
4:32 pmSearch11 minae4fb05b
4:36 pmSearch10 min2f8c98ce
4:45 pmSearch11 min4ddf2256
5:36 pmSearch6 min54cdefd8
5:48 pmSearch3 min6cf81740
5:57 pmSearch6 minb037ec11
6:04 pmTraffic and crashes16 min729e9004
6:06 pmSearch6 mind3dbd8cb
6:18 pmSearch4 min4102952e
6:29 pmSearch17 min978f0f81
6:32 pmSearch14 min26d86f65
6:52 pmSearch14 minaa5bf749
7:07 pmSearch13 min6cd50b1f
8:09 pmPatrol support7 minfd2523ff
8:44 pmSearch20 minec642bad
9:44 pmPatrol support9 minbc83946d
10:23 pmSearch11 minc2d656bf
10:42 pmPatrol support14 min6c509722
11:15 pmPatrol support17 min68062d42

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.