Go-around — VOI1740
KLAS · 26L2026-07-11 20:52 UTC· MMHO → KLAS· WILMINGTON TRUST CO TRUSTEE· A21N
VOI1740 (Wilmington Trust) was operating from MMHO to KLAS on 2026-07-11. SkyMeter detected a go-around at McCarran International Airport (KLAS) on runway 26L at 20:52 UTC. Trace data at the event: 2442 ft AGL, 153 kt GS. METAR at the time reported 8 kt wind, 7 kt crosswind component, 16,093 m visibility. A go-around is a discontinued landing approach in which the pilot adds power and climbs back to a safe altitude before re-attempting the approach or proceeding to an alternate. It is a routine safety response, not an emergency, and is taught as the standard reaction to any unstable approach. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY6/4165 2026-02-14 07:00Z – 2026-08-15 06:59Z SFC–400 ft
Nogales, AZ, Saturday, February 14, 2026 through Friday, August 14, 2026 Local
View FAA NOTAM → - SECURITY6/3948 2026-06-01 07:00Z – 2026-07-21 06:59Z
MESA, AZ, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC
View FAA NOTAM → - SECURITY6/3966 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Mesa, AZ, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/7079 2026-06-27 01:07Z – 2026-07-21 06:59Z SFC–400 ft
Mesa, AZ
View FAA NOTAM → - SECURITY6/7078 2026-06-27 01:07Z – 2026-07-21 06:59Z SFC–400 ft
Mesa, AZ
View FAA NOTAM → - HAZARDS6/1244 2026-06-28 21:00Z – 2026-07-12 04:00Z SFC–10,500 ft
13NM SW FLAGSTAFF, AZ, Sunday, June 28, 2026 through Sunday, July 12, 2026 UTC
View FAA NOTAM → - HAZARDS6/1322 2026-06-29 03:00Z – 2026-07-13 16:00Z SFC–10,500 ft
13NM SW FLAGSTAFF, AZ, Monday, June 29, 2026 through Monday, July 13, 2026 UTC
View FAA NOTAM → - HAZARDS6/1323 2026-06-29 16:00Z – 2026-07-13 03:00Z SFC–10,500 ft
13NM SW FLAGSTAFF, AZ, Monday, June 29, 2026 through Monday, July 13, 2026 UTC
View FAA NOTAM → - HAZARDS6/1728 2026-06-30 03:00Z – 2026-07-13 16:00Z SFC–8,500 ft
13NM SW FLAGSTAFF, AZ, Tuesday, June 30, 2026 through Monday, July 13, 2026 UTC
View FAA NOTAM → - HAZARDS6/2561 2026-07-02 16:00Z – 2026-07-15 03:00Z SFC–12,000 ft
13NM SW FLAGSTAFF, AZ, Thursday, July 2, 2026 through Wednesday, July 15, 2026 UTC
View FAA NOTAM → - SECURITY6/2656 2026-07-05 00:01Z – 2027-01-02 23:59Z SFC–500 ft
Coyote Wells, CA, Saturday, July 4, 2026 through Saturday, January 2, 2027 Local
View FAA NOTAM → - SECURITY6/2657 2026-07-05 00:01Z – 2027-01-02 23:59Z SFC–500 ft
Calexico, CA, Saturday, July 4, 2026 through Saturday, January 2, 2027 Local
View FAA NOTAM → - HAZARDS6/3016 2026-07-06 14:00Z – 2026-07-20 04:00Z SFC–11,000 ft
7NM SW FLAGSTAFF, AZ, Monday, July 6, 2026 through Monday, July 20, 2026 UTC
View FAA NOTAM → - HAZARDS6/3339 2026-07-07 14:00Z – 2026-07-21 04:00Z SFC–11,000 ft
7NM SW FLAGSTAFF, AZ, Tuesday, July 7, 2026 through Tuesday, July 21, 2026 UTC
View FAA NOTAM → - HAZARDS6/3341 2026-07-07 14:00Z – 2026-07-21 04:00Z SFC–8,500 ft
9NM S FLAGSTAFF, AZ, Tuesday, July 7, 2026 through Tuesday, July 21, 2026 UTC
View FAA NOTAM → - HAZARDS6/3393 2026-07-07 14:00Z – 2026-07-21 04:00Z SFC–11,000 ft
7NM SW FLAGSTAFF, AZ, Tuesday, July 7, 2026 through Tuesday, July 21, 2026 UTC
View FAA NOTAM → - SECURITY6/4405 2026-07-11 06:00Z – 2026-07-12 13:00Z SFC–17,999 ft
Libby AAF, AZ, Friday, July 10, 2026 through Sunday, July 12, 2026 Local
View FAA NOTAM →
SkyMeter cross-referenced this flight against FAA-published TFRs that were active during its window and within its geographic bounding box. Overlap doesn't necessarily mean violation — the aircraft may have been outside the TFR’s precise polygon or flying under air-traffic-control coordination.
Pilot review data
- Runway 26L
- 2442 ft AGL at event
- 153 kt ground speed
- 0 fpm vertical
- 8 kt wind
- 7 kt crosswind component
- 16,093 m visibility
- KLAS 170656Z 18011G22KT 10SM CLR 27/18 A2998 RMK AO2 SLP124 T02670178
Flight context
- VOI1740
- Wilmington Trust
- A21N
- MMHO → KLAS
- 2026-07-11 20:52 UTC
- KLAS runway 26L
Automated analysis. Events shown on this page (such as go-around, unstable approach, or runway events) are heuristic classifications produced by algorithms from publicly broadcast ADS-B data. They are intended to surface flights of interest for further review — they are not findings of fact, and they do not determine pilot fault, regulatory compliance, or the cause of any occurrence. Coverage gaps and sensor noise can affect accuracy. Only the relevant civil aviation authority or accident investigation body can make official determinations. How we detect events · Dispute or correct this data