Go-around — EJA417

EJA417 (Netjets Sales) was operating from KMAF to KLAS on 2026-07-02. SkyMeter detected a go-around at McCarran International Airport (KLAS) on runway 26L at 20:08 UTC. Trace data at the event: 2468 ft AGL, 142 kt GS. METAR at the time reported 8 kt wind, 6 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.

• SECURITY6/0092 2026-01-04 00:01Z – 2026-07-04 23:59Z SFC–500 ft

  CALEXICO, CA, Saturday, January 3, 2026 through Saturday, July 4, 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 →
• HAZARDS6/9420 2026-06-20 21:25Z – 2026-07-04 04:00Z SFC–12,000 ft

  40NM SE ALBUQUERQUE, NM, Saturday, June 20, 2026 through Saturday, July 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9456 2026-06-21 13:00Z – 2026-07-05 04:00Z SFC–12,000 ft

  40NM SE ALBUQUERQUE, NM, Sunday, June 21, 2026 through Sunday, July 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9455 2026-06-21 14:00Z – 2026-07-05 04:00Z SFC–9,000 ft

  14NM E PAYSON, AZ, Sunday, June 21, 2026 through Sunday, July 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9496 2026-06-21 14:00Z – 2026-07-05 03:00Z SFC–13,000 ft

  33NM W SHOW LOW, AZ, Sunday, June 21, 2026 through Sunday, July 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9548 2026-06-22 14:00Z – 2026-07-05 04:00Z SFC–10,000 ft

  16NM NE SAN CARLOS, AZ, Monday, June 22, 2026 through Sunday, July 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9854 2026-06-23 14:00Z – 2026-07-06 04:00Z SFC–10,000 ft

  45NM E MESA, AZ, Tuesday, June 23, 2026 through Monday, July 6, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0608 2026-06-25 13:00Z – 2026-07-09 03:00Z SFC–14,000 ft

  15NM W LOS ALAMOS, NM, Thursday, June 25, 2026 through Thursday, July 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0842 2026-06-26 14:00Z – 2026-07-09 03:00Z SFC–10,500 ft

  13NM SW FLAGSTAFF, AZ, Friday, June 26, 2026 through Thursday, July 9, 2026 UTC

  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/1096 2026-06-28 14:00Z – 2026-07-11 04:00Z SFC–9,000 ft

  16NM S GLOBE, AZ, Sunday, June 28, 2026 through Saturday, July 11, 2026 UTC

  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/2670 2026-07-02 15:55Z – 2026-07-03 03:00Z SFC–13,800 ft

  35NM NW SILVER CITY, NM, Thursday, July 2, 2026 through Friday, July 3, 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 →

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.

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