Go-around — AAY169

KFLL · 28R

2026-06-01 14:01 UTC· KABE KFLL· ALLEGIANT AIR LLC· A320

AAY169 (Allegiant AIR) was operating from KABE to KFLL on 2026-06-01. SkyMeter detected a go-around at Fort Lauderdale Hollywood International Airport (KFLL) on runway 28R at 14:01 UTC. Trace data at the event: 596 ft AGL, 134 kt GS. METAR at the time reported 5 kt wind, 2 kt crosswind component, 6,437 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.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • SECURITY5/2809 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–2,000 ft

    Palm Beach, FL, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local

    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 →
  • 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/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/4129 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    BOCA RATON, FL, 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/4133 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    PALM BEACH GARDENS, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    FORT LAUDERDALE, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Palm Beach Gardens, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4380 2026-06-01 13:00Z – 2026-06-06 06:00Z SFC–2,500 ft

    MAYPORT, FL, Monday, June 1, 2026 through Saturday, June 6, 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.

Pilot review data

  • Runway 28R
  • 596 ft AGL at event
  • 134 kt ground speed
  • 0 fpm vertical
  • 5 kt wind
  • 2 kt crosswind component
  • 6,437 m visibility
  • KFLL 181953Z 09003KT 4SM TSRA BR FEW008 SCT020CB OVC070 23/22 A3002 RMK AO2 PK WND 10030/1854 WSHFT 1844 SLP164 OCNL LTGICCACG NE-SE TS NE-SE MOV NE P0077 T02330217 $

Flight context

  • AAY169
  • Allegiant AIR
  • A320
  • KABE → KFLL
  • 2026-06-01 14:01 UTC
  • KFLL runway 28R

All events on this flight

Go-around 14:01:42 UTC · KFLL runway 28R · 596 ft AGL · 134 kt GS
Go-around 14:01:42 UTC · KFLL runway 28R · 596 ft AGL · 134 kt GS

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

SkyMeter · trace data observed via ADS-B· KFLL