Go-around — AAY9201

AAY9201 (Sunrise Asset Management) was operating from KPVU to KLAS on 2026-07-03. SkyMeter detected a go-around at McCarran International Airport (KLAS) on runway 26L at 04:02 UTC. Trace data at the event: 2618 ft AGL, 138 kt GS. METAR at the time reported 7 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.

• HAZARDS6/9356 2026-06-20 13:00Z – 2026-07-03 04:00Z SFC–11,000 ft

  46 NM NW MESQUITE, NV, Saturday, June 20, 2026 through Friday, July 3, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9359 2026-06-20 13:00Z – 2026-07-03 04:00Z SFC–11,000 ft

  39 NM NW MESQUITE, NV, Saturday, June 20, 2026 through Friday, July 3, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9412 2026-06-20 17:53Z – 2026-07-03 04:00Z SFC–11,000 ft

  27NM SW PROVO, UT, Saturday, June 20, 2026 through Friday, July 3, 2026 UTC

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

  39 NM NW MESQUITE, NV, Sunday, June 21, 2026 through Saturday, July 4, 2026 UTC

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

  37NM NW MESQUITE, NV, Sunday, June 21, 2026 through Saturday, July 4, 2026 UTC

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

  27NM SW PROVO, UT, Sunday, June 21, 2026 through Saturday, July 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9981 2026-06-23 13:28Z – 2026-07-07 15:00Z SFC–13,500 ft

  3NM E BEAVER, UT, Tuesday, June 23, 2026 through Tuesday, July 7, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9985 2026-06-23 13:54Z – 2026-07-07 15:00Z SFC–11,000 ft

  27NM SW PROVO, UT, Tuesday, June 23, 2026 through Tuesday, July 7, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0134 2026-06-23 17:52Z – 2026-07-07 04:00Z SFC–13,500 ft

  3NM E BEAVER, UT, Tuesday, June 23, 2026 through Tuesday, July 7, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0416 2026-06-24 14:54Z – 2026-07-07 04:00Z SFC–13,500 ft

  3NM E BEAVER, UT, Wednesday, June 24, 2026 through Tuesday, July 7, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1019 2026-06-26 23:25Z – 2026-07-08 04:00Z SFC–11,000 ft

  27NM SW PROVO, UT, Friday, June 26, 2026 through Wednesday, July 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1072 2026-06-27 14:12Z – 2026-07-10 04:00Z SFC–11,000 ft

  27NM SW PROVO, UT, Saturday, June 27, 2026 through Friday, July 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1074 2026-06-27 14:41Z – 2026-07-10 04:00Z SFC–11,000 ft

  7NM S SCIPIO, UT, Saturday, June 27, 2026 through Friday, July 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1144 2026-06-28 14:00Z – 2026-07-11 04:00Z SFC–11,000 ft

  27NM SW PROVO, UT, Sunday, June 28, 2026 through Saturday, July 11, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1220 2026-06-28 16:15Z – 2026-07-11 04:00Z SFC–15,500 ft

  3NM E BEAVER, UT, Sunday, June 28, 2026 through Saturday, July 11, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1335 2026-06-29 01:32Z – 2026-07-13 04:00Z SFC–12,000 ft

  6NM S SCIPIO, UT, Monday, June 29, 2026 through Monday, July 13, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2594 2026-07-02 13:00Z – 2026-07-15 04:00Z SFC–12,000 ft

  23NM S PANACA, NV, Thursday, July 2, 2026 through Wednesday, July 15, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2593 2026-07-02 14:00Z – 2026-07-13 05:00Z SFC–12,000 ft

  12NM N PIOCHE, NV, Thursday, July 2, 2026 through Monday, July 13, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2595 2026-07-02 14:00Z – 2026-07-13 05:00Z SFC–12,000 ft

  12NM N PIOCHE, NV, Thursday, July 2, 2026 through Monday, July 13, 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