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

Dearborn, Michigan · one day

Friday 17 April 2026

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

27

drone flights over Dearborn that day.

12:07 am

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

8 min

median flight. Half were shorter.

Dearborn police drones flew 27 times on Friday 17 April 2026, the first at 12:07 am and the last at 11:51 pm EDT, by Dearborn Police Department's published record.

27 drawable flights of 27. 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. Search30%
  2. Training and testing26%
  3. Traffic and crashes22%
  4. Patrol support11%
  5. Assisting another agency4%
  6. Other4%
  7. Call for service4%

Flights, in order

27 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:07 amSearch11 min8317983d
12:39 amPatrol support6 min78d310f3
1:00 amTraffic and crashes5 min972fc24e
1:12 amPatrol support10 minc2b630ee
2:22 amPatrol support4 mind6f9298b
2:41 amSearch18 mina055892a
11:40 amTraffic and crashes7 min64fce624
11:50 amAssisting another agency19 min5fd9237e
12:13 pmSearch7 min63f1af66
12:22 pmOther14 min61cde1b8
12:22 pmTraining and testing42 s662b8e88
1:02 pmTraining and testing8 min5c965359
1:23 pmTraining and testing14 minb633a636
1:48 pmTraining and testing2 min4f39ad17
1:58 pmTraining and testing16 min82608758
2:16 pmTraining and testing50 s215b0d5d
2:18 pmTraining and testing23 min2634f587
4:08 pmSearch7 min12fa9650
4:17 pmSearch17 min3e7bf3a0
4:40 pmSearch2 min730900d1
8:21 pmSearch13 min6301c003
8:49 pmSearch8 mine2bbb44c
9:25 pmCall for service7 minb66fbb35
9:34 pmTraffic and crashes6 min3d70bc9c
10:02 pmTraffic and crashes13 min6b8f8cb4
10:37 pmTraffic and crashes7 min6a48e814
11:51 pmTraffic and crashes8 minecac1793

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.