Unstable approach — DAL2479
KPWM · 292026-08-29 17:00 UTC· KATL → KPWM· BANK OF UTAH TRUSTEE· A321
DAL2479 (Bank of Utah) was operating from KATL to KPWM on 2026-08-29. SkyMeter detected a low approach-stability score at Portland International Jetport (KPWM) on runway 29 at 17:00 UTC. Trace data at the event: 1159 ft AGL, 146 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 9 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)- SECURITY5/2811 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–1,000 ft
NEW YORK, NY, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local
View FAA NOTAM → - SECURITY6/5076 2026-08-19 15:00Z – 2026-08-30 22:00Z SFC–1,000 ft
Williamsport, PA, Wednesday, August 19, 2026 through Sunday, August 30, 2026 Local
View FAA NOTAM → - SECURITY6/7002 2026-08-24 13:00Z – 2026-09-13 07:00Z SFC–1,000 ft
Flushing, NY, Monday, August 24, 2026 through Sunday, September 13, 2026 Local
View FAA NOTAM → - UAS PUBLIC GATHERING6/6427 2026-08-26 13:00Z – 2026-09-08 03:59Z SFC–400 ft
Syracuse, NY, Wednesday, August 26, 2026 through Tuesday, September 8, 2026 UTC
View FAA NOTAM → - UAS PUBLIC GATHERING6/7351 2026-08-27 12:00Z – 2026-10-13 03:00Z SFC–400 ft
Timonium, MD, Thursday, August 27, 2026 through Tuesday, October 13, 2026 UTC
View FAA NOTAM → - SECURITY6/6997 2026-08-27 15:00Z – 2026-08-31 03:00Z SFC–400 ft
Plymouth, MI, Thursday, August 27, 2026 through Sunday, August 30, 2026 Local
View FAA NOTAM → - SECURITY6/6989 2026-08-27 21:00Z – 2026-09-02 21:00Z SFC–400 ft
Asheville, NC, Thursday, August 27, 2026 through Wednesday, September 2, 2026 Local
View FAA NOTAM → - SECURITY6/6995 2026-08-28 10:00Z – 2026-08-30 23:59Z SFC–400 ft
Grand Blanc, MI, Friday, August 28, 2026 through Sunday, August 30, 2026 Local
View FAA NOTAM → - VIP6/8638 2026-08-28 20:00Z – 2026-08-30 21:00Z SFC–4,999 ft
Middleburg, VA, Friday, August 28, 2026 through Sunday, August 30, 2026 Local
View FAA NOTAM → - UAS PUBLIC GATHERING6/7354 2026-08-28 22:00Z – 2026-08-30 03:59Z SFC–400 ft
Foxborough, MA, Friday, August 28, 2026 through Sunday, August 30, 2026 UTC
View FAA NOTAM → - VIP6/8771 2026-08-29 13:00Z – 2026-08-30 02:00Z SFC–9,999 ft
Sterling, VA, Saturday, August 29, 2026 through Saturday, August 29, 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 29
- 1159 ft AGL at event
- 146 kt ground speed
- 0 fpm vertical
- Approach stability 44/100
- 9 kt wind
- 6 kt crosswind component
- 16,093 m visibility
- KPWM 161851Z 16011KT 10SM FEW065 SCT250 21/14 A3026 RMK AO2 SLP248 T02110144 $
Flight context
- DAL2479
- Bank of Utah
- A321
- KATL → KPWM
- 2026-08-29 17:00 UTC
- KPWM runway 29
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