Unstable approach — AAY1329

AAY1329 (Allegiant AIR) was operating from KSFB to KMLI on 2026-06-17. SkyMeter detected a low approach-stability score at Quad City International Airport (KMLI) on runway 09 at 22:04 UTC. Trace data at the event: 1738 ft AGL, 242 kt GS. Approach stability score: 48/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 5 kt wind, 3 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.

• 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/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/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/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 →
• HAZARDS6/5656 2026-06-04 16:19Z – 2026-06-18 00:15Z SFC–2,000 ft

  22NM SW TALLAHASSEE, FL, Thursday, June 4, 2026 through Thursday, June 18, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5771 2026-06-04 21:47Z – 2026-06-18 00:15Z SFC–3,500 ft

  22NM SW TALLAHASSEE, FL, Thursday, June 4, 2026 through Thursday, June 18, 2026 UTC

  View FAA NOTAM →
• SECURITY6/7495 2026-06-17 04:01Z – 2026-06-18 03:59Z SFC–1,000 ft

  Atlanta, GA, Wednesday, June 17, 2026 through Wednesday, June 17, 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 →

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