Unstable approach — AAY2503

KMLI · 27

2026-07-03 21:58 UTC· KPGD KMLI· ALLEGIANT AIR LLC· A320

AAY2503 (Allegiant AIR) was operating from KPGD to KMLI on 2026-07-03. SkyMeter detected a low approach-stability score at Quad City International Airport (KMLI) on runway 27 at 21:58 UTC. Trace data at the event: 1809 ft AGL, 173 kt GS. Approach stability score: 55/100. Scores in this band occur on roughly 10-15% of approaches at this runway, with multiple gates outside the per-runway envelope. METAR at the time reported 9 kt wind, 9 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/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/3979 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    ATLANTA, GA, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC

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

    CHATTANOOGA, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    CHATTANOOGA, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    MARIETTA, GA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Atlanta, GA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    LOUISVILLE, KY, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    LOUISVILLE, KY, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    CARMEL, IN, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    CINNCINATI, OH, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    MILFORD, OH, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    WESTFIELD, IN, 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/4161 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

    St, Louis, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    NASHVILLE, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Nashville, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    CLAYTON, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Kennesaw, GA, Wednesday, June 17, 2026 through Thursday, July 16, 2026 Local

    View FAA NOTAM →
  • SECURITY6/7205 2026-06-23 21:07Z – 2026-07-21 03:59Z SFC–400 ft

    Carmel, IN

    View FAA NOTAM →
  • SECURITY6/7208 2026-06-23 21:07Z – 2026-07-21 03:59Z SFC–400 ft

    Westfield, IN

    View FAA NOTAM →
  • UAS PUBLIC GATHERING6/0131 2026-06-30 11:00Z – 2026-07-07 02:00Z SFC–400 ft

    Columbus, OH, Tuesday, June 30, 2026 through Tuesday, July 7, 2026 UTC

    View FAA NOTAM →
  • SECURITY6/7972 2026-07-01 16:07Z – 2026-07-21 04:59Z SFC–400 ft

    Nashville, TN

    View FAA NOTAM →
  • SECURITY6/7967 2026-07-01 16:07Z – 2026-07-21 04:59Z SFC–400 ft

    Nashville, TN

    View FAA NOTAM →
  • SECURITY6/7194 2026-07-03 16:07Z – 2026-07-21 03:59Z SFC–400 ft

    Columbus, OH

    View FAA NOTAM →
  • AIR SHOWS/SPORTS6/1390 2026-07-03 19:00Z – 2026-07-06 02:00Z SFC–5,000 ft

    mattoon, IL, Friday, July 3, 2026 through Monday, July 6, 2026 UTC

    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 27
  • 1809 ft AGL at event
  • 173 kt ground speed
  • 0 fpm vertical
  • Approach stability 55/100
  • 9 kt wind
  • 9 kt crosswind component
  • 16,093 m visibility
  • KMLI 162352Z 08004KT 10SM OVC008 21/19 A3025 RMK AO2 SLP242 60000 T02110194 10217 20206 53002

Flight context

  • AAY2503
  • Allegiant AIR
  • A320
  • KPGD → KMLI
  • 2026-07-03 21:58 UTC
  • KMLI runway 27

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· KMLI