CityDroneWatch
  1. CityDroneWatch
  2. Nevada
  3. Las Vegas
  4. February 2026
  5. 2

Las Vegas, Nevada · one day

Monday 2 February 2026

62 drone flights from Las Vegas Metropolitan Police Department's published record.

62

drone flights over Las Vegas that day.

12:11 am

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

—

durations not published in this record.

Las Vegas police drones flew 62 times on Monday 2 February 2026, the first at 12:11 am and the last at 11:11 pm PST, by Las Vegas Metropolitan Police Department's published record.

62 flights with a published block-level point of 62. The record gives no path.
One flight, at its published block

Hour by hour

Takeoffs by hour, PST.

12a1a2a3a4a5a6a7a8a9a10a11a12p1p2p3p4p5p6p7p8p9p10p11p

Why, in the agency's words

  1. Not stated100%

Flights, in order

62 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 (PST)PurposeAirborneFlight
12:11 amNot stated—985abb67
12:38 amNot stated—dae8e65a
1:33 amNot stated—10b85196
2:01 amNot stated—18968f5d
2:28 amNot stated—c48132d5
2:55 amNot stated—b33b39eb
7:56 amNot stated—d089232a
8:06 amNot stated—cb93b7b5
8:42 amNot stated—bc803519
8:55 amNot stated—299ad64e
9:27 amNot stated—309b5b46
10:10 amNot stated—5acc6ec5
10:31 amNot stated—fa62a4a5
10:35 amNot stated—51c70596
10:53 amNot stated—5ceb9a27
10:54 amNot stated—65265dae
11:09 amNot stated—58267d96
11:12 amNot stated—82c91021
12:58 pmNot stated—637f953e
1:13 pmNot stated—3c578bbb
1:16 pmNot stated—14467ead
1:30 pmNot stated—c144eae0
1:31 pmNot stated—53809fe3
1:41 pmNot stated—fa5c9d75
1:53 pmNot stated—110d64a3
2:17 pmNot stated—50a02841
2:19 pmNot stated—72df5fb9
2:24 pmNot stated—af67d532
2:57 pmNot stated—1ba3de67
3:08 pmNot stated—5366f875
3:19 pmNot stated—01ab35fd
3:19 pmNot stated—e5960780
3:24 pmNot stated—0e7e048f
4:22 pmNot stated—531ed87d
4:46 pmNot stated—3694e124
4:59 pmNot stated—00e49b8e
5:05 pmNot stated—a7da69d2
5:18 pmNot stated—2e78f1e8
5:21 pmNot stated—f465034d
5:27 pmNot stated—86d265ad
5:35 pmNot stated—d194fa89
5:49 pmNot stated—eb230828
6:25 pmNot stated—213d8312
6:51 pmNot stated—1e047f44
7:01 pmNot stated—50d8b8ce
7:13 pmNot stated—018675b6
7:30 pmNot stated—9c6bafa0
8:10 pmNot stated—4c665799
8:16 pmNot stated—9aca2819
8:19 pmNot stated—4aa46e91
8:33 pmNot stated—29383578
8:39 pmNot stated—e298719a
8:55 pmNot stated—9b1aa9aa
9:00 pmNot stated—e208ecfd
9:14 pmNot stated—972bd08d
9:18 pmNot stated—beb788bb
9:30 pmNot stated—6de26431
10:13 pmNot stated—a2e2c7c1
10:17 pmNot stated—c69c0ebb
10:21 pmNot stated—3ba38026
10:34 pmNot stated—3b7bca37
11:11 pmNot stated—6fca4bf1

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.