Go-around — AAY3641

AAY3641 (Sunrise Asset Management) was operating from KTTN to KPIE on 2026-06-27. SkyMeter detected a go-around at St Petersburg Clearwater International Airport (KPIE) on runway 17L at 18:56 UTC. Trace data at the event: 246 ft AGL, 133 kt GS, 0 fpm vertical. METAR at the time reported 6 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.

• SECURITY6/3961 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  Chester, PA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/3967 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  PHILADELPHIA, PA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/3968 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  Winston Salem, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/3970 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  White Sulphur Springs, WV, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/3971 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  Winston Salem, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/3973 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  WILMINGTON, DE, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4001 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  GREENSBORO, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4004 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  CHARLOTTE, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4005 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  Greensboro, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4007 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  Charlotte, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4131 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  MYRTLE BEACH, SC, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4132 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  Conway, SC, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4153 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  Tampa, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4156 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  TAMPA, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/6442 2026-06-10 04:01Z – 2026-07-20 03:59Z SFC–1,000 ft

  Philadelphia, PA, Wednesday, June 10, 2026 through Sunday, July 19, 2026 Local

  View FAA NOTAM →
• SECURITY6/9498 2026-06-24 11:00Z – 2026-06-30 23:59Z SFC–2,000 ft

  Baltimore, MD, Wednesday, June 24, 2026 through Tuesday, June 30, 2026 Local

  View FAA NOTAM →
• AIR SHOWS/SPORTS6/8970 2026-06-24 16:00Z – 2026-06-28 20:00Z SFC–15,000 ft

  Baltimore, MD, Wednesday, June 24, 2026 through Sunday, June 28, 2026 UTC

  View FAA NOTAM →
• VIP6/0778 2026-06-27 12:00Z – 2026-06-27 22:00Z SFC–9,999 ft

  Sterling, VA, Saturday, June 27, 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