Go-around — AAL1564

AAL1564 (Wilmington Trust) was operating from KPHX to KBOS on 2026-05-24. SkyMeter detected a go-around at General Edward Lawrence Logan International Airport (KBOS) on runway 04R at 20:19 UTC. Trace data at the event: 565 ft AGL, 137 kt GS. METAR at the time reported 14 kt wind, 12 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/0618 2026-05-15 13:00Z – 2026-05-28 04:00Z SFC–13,500 ft

  22NM NE RUIDOSO, NM, Friday, May 15, 2026 through Thursday, May 28, 2026 UTC

  View FAA NOTAM →
• SECURITY6/9784 2026-05-16 12:00Z – 2026-06-12 22:00Z SFC–400 ft

  Moyock, NC, Saturday, May 16, 2026 through Friday, June 12, 2026 Local

  View FAA NOTAM →
• HAZARDS6/0887 2026-05-16 18:37Z – 2026-05-30 04:00Z SFC–10,500 ft

  19NM SW TUCUMCARI, NM, Saturday, May 16, 2026 through Saturday, May 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1015 2026-05-18 00:28Z – 2026-06-01 04:00Z SFC–15,500 ft

  22NM NE RUIDOSO, NM, Monday, May 18, 2026 through Monday, June 1, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1358 2026-05-19 00:52Z – 2026-06-02 02:00Z SFC–10,000 ft

  5NM S CAMPO, CO, Tuesday, May 19, 2026 through Tuesday, June 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1626 2026-05-19 22:38Z – 2026-06-02 04:00Z SFC–15,500 ft

  22NM NE RUIDOSO, NM, Tuesday, May 19, 2026 through Tuesday, June 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2354 2026-05-22 12:00Z – 2026-06-04 04:00Z SFC–15,500 ft

  22NM NE RUIDOSO, NM, Friday, May 22, 2026 through Thursday, June 4, 2026 UTC

  View FAA NOTAM →
• VIP6/2122 2026-05-22 20:30Z – 2026-05-24 23:00Z SFC–17,999 ft

  Bedminster, NJ, Friday, May 22, 2026 through Sunday, May 24, 2026 Local

  View FAA NOTAM →
• VIP6/2125 2026-05-22 20:30Z – 2026-05-24 23:00Z SFC–17,999 ft

  Bedminster, NJ, Friday, May 22, 2026 through Sunday, May 24, 2026 Local

  View FAA NOTAM →
• VIP6/2150 2026-05-22 21:00Z – 2026-05-25 14:00Z SFC–4,999 ft

  CINCINNATI, OH, Friday, May 22, 2026 through Monday, May 25, 2026 Local

  View FAA NOTAM →
• UAS PUBLIC GATHERING6/1028 2026-05-23 15:00Z – 2026-05-25 22:00Z SFC–400 ft

  Charlottesville, VA, Saturday, May 23, 2026 through Monday, May 25, 2026 UTC

  View FAA NOTAM →
• UAS PUBLIC GATHERING6/1154 2026-05-23 16:00Z – 2026-05-25 04:00Z SFC–400 ft

  chicago, IL, Saturday, May 23, 2026 through Monday, May 25, 2026 UTC

  View FAA NOTAM →
• VIP6/2530 2026-05-23 21:00Z – 2026-05-25 14:00Z SFC–4,999 ft

  CINCINNATI, OH, Saturday, May 23, 2026 through Monday, May 25, 2026 Local

  View FAA NOTAM →
• SECURITY6/1953 2026-05-24 12:00Z – 2026-05-24 23:59Z SFC–2,000 ft

  Indianapolis, IN, Sunday, May 24, 2026 Local

  View FAA NOTAM →
• SECURITY6/2014 2026-05-24 12:00Z – 2026-05-24 17:00Z SFC–2,000 ft

  Indianapolis, IN, Sunday, May 24, 2026 Local

  View FAA NOTAM →
• VIP6/2512 2026-05-24 12:00Z – 2026-05-24 23:00Z SFC–9,999 ft

  Sterling, VA, Sunday, May 24, 2026 Local

  View FAA NOTAM →
• SECURITY6/2322 2026-05-24 20:20Z – 2026-05-24 23:00Z SFC–2,000 ft

  Morristown, NJ, Sunday, May 24, 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.

All events on this flight

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