Unstable approach — AAY1116

KPIT · 28L

2026-06-07 22:03 UTC· KPIE → KPIT· ALLEGIANT AIR LLC· A320

AAY1116 (Allegiant AIR) was operating from KPIE to KPIT on 2026-06-07. SkyMeter detected a low approach-stability score at Pittsburgh International Airport (KPIT) on runway 28L at 22:03 UTC. Trace data at the event: 2317 ft AGL, 158 kt GS. Approach stability score: 41/100. Scores below 50 occur on under 10% of approaches at this runway and indicate the v2 scorer flagged the approach as highly anomalous (three or more gates exceeded the runway's P90 envelope simultaneously). METAR at the time reported 6 kt wind, 6 kt crosswind component, 16,093 m visibility. The approach-stability score rates the final approach against stabilized-approach gates (glideslope, lateral deviation, descent rate, and IAS) at defined altitudes. A low score means one or more of those were outside the normal envelope for how the approach was flown. The score is graded by guidance type, so instrument approaches (ILS or an aligned straight-in) are held to the full gate set, while visual and pattern arrivals are surfaced only when the score is clearly low. The score is advisory and observational, a deviation measure, not an assertion of an accident. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • SECURITY6/2644 2026-05-27 11:00Z – 2026-06-12 22:00Z SFC–400 ft

    Brunswick, GA, Wednesday, May 27, 2026 through Friday, June 12, 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/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/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 →

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 28L
  • 2317 ft AGL at event
  • 158 kt ground speed
  • 0 fpm vertical
  • Approach stability 41/100
  • 6 kt wind
  • 6 kt crosswind component
  • 16,093 m visibility
  • KPIT 141651Z 31004KT 10SM SCT050 BKN075 BKN100 22/19 A3000 RMK AO2 RAE19 TSB29E50 SLP158 OCNL LTG DSNT SE P0003 T02170189

Flight context

  • AAY1116
  • Allegiant AIR
  • A320
  • KPIE → KPIT
  • 2026-06-07 22:03 UTC
  • KPIT runway 28L

All events on this flight

Unstable approach 22:03:04 UTC · KPIT runway 28L · 2,317 ft AGL · 158 kt GS
Unstable approach 22:03:04 UTC · KPIT runway 28L · 2,317 ft AGL · 158 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· KPIT