Go-around — AAL2353

AAL2353 (Bank of Utah) was operating from KDFW to KPWM on 2026-08-02. SkyMeter detected a go-around at Portland International Jetport (KPWM) on runway 11 at 20:20 UTC. Trace data at the event: 997 ft AGL, 178 kt GS. METAR at the time reported 9 kt wind, 9 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.

• SECURITY5/2811 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–1,000 ft

  NEW YORK, NY, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local

  View FAA NOTAM →
• HAZARDS6/6848 2026-07-20 00:32Z – 2026-08-03 23:45Z SFC–3,000 ft

  2NM W SHULERVILLE, SC, Monday, July 20, 2026 through Monday, August 3, 2026 UTC

  View FAA NOTAM →
• AIR SHOWS/SPORTS6/7538 2026-07-28 19:30Z – 2026-08-02 21:00Z SFC–16,000 ft

  Montgomery, NY, Tuesday, July 28, 2026 through Sunday, August 2, 2026 UTC

  View FAA NOTAM →
• AIR SHOWS/SPORTS6/7540 2026-07-28 19:30Z – 2026-08-02 21:00Z SFC–16,000 ft

  Montgomery, NY, Tuesday, July 28, 2026 through Sunday, August 2, 2026 UTC

  View FAA NOTAM →
• AIR SHOWS/SPORTS6/8398 2026-07-28 19:30Z – 2026-08-02 21:00Z SFC–15,000 ft

  Montgomery, NY, Tuesday, July 28, 2026 through Sunday, August 2, 2026 UTC

  View FAA NOTAM →
• AIR SHOWS/SPORTS6/8401 2026-07-28 19:30Z – 2026-08-02 21:00Z SFC–15,000 ft

  Montgomery, NY, Tuesday, July 28, 2026 through Sunday, August 2, 2026 UTC

  View FAA NOTAM →
• AIR SHOWS/SPORTS6/8368 2026-07-29 19:00Z – 2026-08-02 21:00Z SFC–15,000 ft

  Montgomery, NY, Wednesday, July 29, 2026 through Sunday, August 2, 2026 UTC

  View FAA NOTAM →
• AIR SHOWS/SPORTS6/8379 2026-07-29 19:00Z – 2026-08-02 21:00Z SFC–15,000 ft

  Montgomery, NY, Wednesday, July 29, 2026 through Sunday, August 2, 2026 UTC

  View FAA NOTAM →
• UAS PUBLIC GATHERING6/8930 2026-07-30 16:00Z – 2026-08-03 03:00Z SFC–400 ft

  Chicago, IL, Thursday, July 30, 2026 through Monday, August 3, 2026 UTC

  View FAA NOTAM →
• SECURITY6/0567 2026-07-31 18:00Z – 2026-08-02 23:30Z SFC–2,000 ft

  Morristown, NJ, Friday, July 31, 2026 through Sunday, August 2, 2026 Local

  View FAA NOTAM →
• VIP6/0568 2026-07-31 19:00Z – 2026-08-03 22:30Z SFC–4,999 ft

  Middleburg, VA, Friday, July 31, 2026 through Monday, August 3, 2026 Local

  View FAA NOTAM →
• VIP6/9922 2026-07-31 19:15Z – 2026-08-02 22:45Z SFC–17,999 ft

  Bedminster, NJ, Friday, July 31, 2026 through Sunday, August 2, 2026 Local

  View FAA NOTAM →
• VIP6/9923 2026-07-31 19:15Z – 2026-08-02 22:45Z SFC–17,999 ft

  Bedminster, NJ, Friday, July 31, 2026 through Sunday, August 2, 2026 Local

  View FAA NOTAM →
• SECURITY6/0708 2026-08-01 00:01Z – 2027-08-01 23:59Z SFC–400 ft

  Goodlettsville, TN, Saturday, August 1, 2026 through Sunday, August 1, 2027 UTC

  View FAA NOTAM →
• SECURITY6/0650 2026-08-01 16:00Z – 2026-08-02 22:00Z SFC–400 ft

  Michigan City, IN, Saturday, August 1, 2026 through Sunday, August 2, 2026 Local

  View FAA NOTAM →
• SECURITY6/0028 2026-08-01 19:00Z – 2026-08-03 03:59Z SFC–400 ft

  East Rutherford, NJ, Saturday, August 1, 2026 through Sunday, August 2, 2026 Local

  View FAA NOTAM →
• UAS PUBLIC GATHERING6/8932 2026-08-02 12:00Z – 2026-08-03 05:00Z SFC–400 ft

  st louis, MO, Sunday, August 2, 2026 through Monday, August 3, 2026 UTC

  View FAA NOTAM →
• VIP6/0981 2026-08-02 19:30Z – 2026-08-02 21:30Z SFC–17,999 ft

  Morristown, NJ, Sunday, August 2, 2026 Local

  View FAA NOTAM →
• VIP6/0983 2026-08-02 19:30Z – 2026-08-02 21:30Z SFC–17,999 ft

  Morristown, NJ, Sunday, August 2, 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.

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