Unstable approach — AAY3200
KATW · 212026-07-03 22:15 UTC· KPDX → KATW· ALLEGIANT AIR LLC· A320
AAY3200 (Allegiant AIR) was operating from KPDX to KATW on 2026-07-03. SkyMeter detected a low approach-stability score at Appleton International Airport (KATW) on runway 21 at 22:15 UTC. Trace data at the event: 2039 ft AGL, 174 kt GS. Approach stability score: 44/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 7 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/4040 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Portland, OR, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4041 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
PORTLAND, OR, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - HAZARDS6/9554 2026-06-22 13:00Z – 2026-07-06 04:00Z SFC–10,000 ft
37NM SW GRANGEVILLE, ID, Monday, June 22, 2026 through Monday, July 6, 2026 UTC
View FAA NOTAM → - HAZARDS6/9557 2026-06-22 13:00Z – 2026-07-07 04:00Z SFC–10,000 ft
37NM SW GRANGEVILLE, ID, Monday, June 22, 2026 through Tuesday, July 7, 2026 UTC
View FAA NOTAM → - HAZARDS6/0606 2026-06-25 14:00Z – 2026-07-10 04:00Z SFC–10,000 ft
37NM SW GRANGEVILLE, ID, Thursday, June 25, 2026 through Friday, July 10, 2026 UTC
View FAA NOTAM → - HAZARDS6/0614 2026-06-25 14:00Z – 2026-07-10 04:00Z SFC–10,000 ft
37NM SW GRANGEVILLE, ID, Thursday, June 25, 2026 through Friday, July 10, 2026 UTC
View FAA NOTAM → - HAZARDS6/1022 2026-06-27 14:00Z – 2026-07-12 04:00Z SFC–10,000 ft
37NM SW GRANGEVILLE, ID, Saturday, June 27, 2026 through Sunday, July 12, 2026 UTC
View FAA NOTAM → - HAZARDS6/1023 2026-06-27 14:00Z – 2026-07-12 04:00Z SFC–10,000 ft
37NM SW GRANGEVILLE, ID, Saturday, June 27, 2026 through Sunday, July 12, 2026 UTC
View FAA NOTAM → - HAZARDS6/1247 2026-06-28 22:17Z – 2026-07-10 16:00Z SFC–5,500 ft
7NM NW THE DALLES, OR, Sunday, June 28, 2026 through Friday, July 10, 2026 UTC
View FAA NOTAM → - HAZARDS6/1598 2026-06-30 15:00Z – 2026-07-11 23:00Z SFC–5,500 ft
7NM NW THE DALLES, OR, Tuesday, June 30, 2026 through Saturday, July 11, 2026 UTC
View FAA NOTAM → - HAZARDS6/2576 2026-07-02 13:00Z – 2026-07-16 02:00Z SFC–10,000 ft
38NM SW GRANGEVILLE, ID, Thursday, July 2, 2026 through Thursday, July 16, 2026 UTC
View FAA NOTAM → - HAZARDS6/2586 2026-07-02 13:00Z – 2026-07-16 02:00Z SFC–10,000 ft
38NM SW GRANGEVILLE, ID, Thursday, July 2, 2026 through Thursday, July 16, 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 21
- 2039 ft AGL at event
- 174 kt ground speed
- 0 fpm vertical
- Approach stability 44/100
- 7 kt wind
- 6 kt crosswind component
- 16,093 m visibility
- METAR KATW 162145Z 00000KT 10SM BKN037 22/14 A3033
Flight context
- AAY3200
- Allegiant AIR
- A320
- KPDX → KATW
- 2026-07-03 22:15 UTC
- KATW runway 21
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