Go-around — SWA2099

SWA2099 (Southwest Airlines) was operating from KCOS to KLAS on 2026-08-07. SkyMeter detected a go-around at McCarran International Airport (KLAS) on runway 26L at 20:11 UTC. Trace data at the event: 2801 ft AGL, 145 kt GS. METAR at the time reported 5 kt wind, 2 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/8010 2026-07-23 12:00Z – 2026-08-12 04:00Z SFC–16,500 ft

  19NM NE OURAY, CO, Thursday, July 23, 2026 through Wednesday, August 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8012 2026-07-23 12:00Z – 2026-08-12 04:00Z SFC–16,500 ft

  1NM N OURAY, CO, Thursday, July 23, 2026 through Wednesday, August 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8554 2026-07-26 12:00Z – 2026-08-10 03:00Z SFC–12,000 ft

  16NM W MONTICELLO, UT, Sunday, July 26, 2026 through Monday, August 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9111 2026-07-28 14:00Z – 2026-08-10 03:00Z SFC–14,500 ft

  14NM N LOS ALAMOS, NM, Tuesday, July 28, 2026 through Monday, August 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9802 2026-07-29 12:00Z – 2026-08-11 04:00Z SFC–16,500 ft

  1NM N OURAY, CO, Wednesday, July 29, 2026 through Tuesday, August 11, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9885 2026-07-29 12:00Z – 2026-08-12 04:00Z SFC–15,000 ft

  8NM S PAGOSA SPRINGS, CO, Wednesday, July 29, 2026 through Wednesday, August 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9841 2026-07-29 14:00Z – 2026-08-11 03:00Z SFC–11,500 ft

  11NM S CIMARRON, NM, Wednesday, July 29, 2026 through Tuesday, August 11, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0409 2026-07-30 04:00Z – 2026-08-12 04:00Z SFC–15,000 ft

  9NM SW PUEBLO, CO, Thursday, July 30, 2026 through Wednesday, August 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0882 2026-08-02 04:00Z – 2026-08-15 04:00Z SFC–15,000 ft

  8NM S PAGOSA SPRINGS, CO, Sunday, August 2, 2026 through Saturday, August 15, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1461 2026-08-04 12:00Z – 2026-08-18 04:00Z SFC–13,000 ft

  4NM W RICHFIELD, UT, Tuesday, August 4, 2026 through Tuesday, August 18, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1464 2026-08-04 12:00Z – 2026-08-18 04:00Z SFC–13,000 ft

  4NM W RICHFIELD, UT, Tuesday, August 4, 2026 through Tuesday, August 18, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1462 2026-08-04 13:00Z – 2026-09-01 04:00Z SFC–15,000 ft

  20NM SW PUEBLO, CO, Tuesday, August 4, 2026 through Tuesday, September 1, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1949 2026-08-05 12:00Z – 2026-08-19 04:00Z SFC–13,000 ft

  13NM SW CORTEZ, CO, Wednesday, August 5, 2026 through Wednesday, August 19, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2435 2026-08-06 13:00Z – 2026-08-20 04:00Z SFC–13,500 ft

  13NM N SANTA FE, NM, Thursday, August 6, 2026 through Thursday, August 20, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2767 2026-08-07 12:00Z – 2026-08-21 04:00Z SFC–16,500 ft

  1NM NE OURAY, CO, Friday, August 7, 2026 through Friday, August 21, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2842 2026-08-07 14:30Z – 2026-08-21 04:00Z SFC–13,500 ft

  13NM N SANTA FE, NM, Friday, August 7, 2026 through Friday, August 21, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2889 2026-08-07 19:58Z – 2026-08-21 04:00Z SFC–13,000 ft

  4NM W RICHFIELD, UT, Friday, August 7, 2026 through Friday, August 21, 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