Go-around — AAL1883

AAL1883 (American Airlines) was operating from KDFW to KBZN on 2026-08-03. SkyMeter detected a go-around at Jackson Hole Airport (KJAC) on runway 01 at 21:39 UTC. Trace data at the event: 7855 ft AGL, 152 kt GS. METAR at the time reported 8 kt wind, 1 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/7220 2026-07-21 04:00Z – 2026-08-04 04:00Z SFC–12,000 ft

  19NM SW MEEKER, CO, Tuesday, July 21, 2026 through Tuesday, August 4, 2026 UTC

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

  7NM SE STEAMBOAT SPRINGS, CO, Tuesday, July 21, 2026 through Tuesday, August 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7702 2026-07-22 13:08Z – 2026-08-05 04:00Z SFC–11,500 ft

  11NM SW CRAIG, CO, Wednesday, July 22, 2026 through Wednesday, August 5, 2026 UTC

  View FAA NOTAM →
• 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/8871 2026-07-27 14:00Z – 2026-08-09 04:00Z SFC–8,000 ft

  83NM N SPEARFISH, SD, Monday, July 27, 2026 through Sunday, August 9, 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/9566 2026-07-28 17:15Z – 2026-08-11 04:00Z SFC–10,000 ft

  33NM SW PHILIP, SD, Tuesday, July 28, 2026 through Tuesday, August 11, 2026 UTC

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

  19NM NW GRAND JUNCTION, CO, Wednesday, July 29, 2026 through Wednesday, August 12, 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/0749 2026-08-01 15:00Z – 2026-08-14 03:00Z SFC–13,000 ft

  13NM S SAFFORD, AZ, Saturday, August 1, 2026 through Friday, August 14, 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/0881 2026-08-02 13:00Z – 2026-08-16 03:00Z SFC–14,000 ft

  26NM SW PRICE, UT, Sunday, August 2, 2026 through Sunday, August 16, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0876 2026-08-02 14:00Z – 2026-08-09 02:00Z SFC–13,000 ft

  30NM NW ALBUQUERQUE, NM, Sunday, August 2, 2026 through Sunday, August 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1232 2026-08-03 17:11Z – 2026-08-05 04:00Z SFC–13,000 ft

  13NM SW CORTEZ, CO, Monday, August 3, 2026 through Wednesday, August 5, 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