Unstable approach — FFT4545
69WT · 33W2026-06-01 16:40 UTC· KDEN → ?· BANK OF UTAH TRUSTEE· A21N
FFT4545 (Bank of Utah) had departed KDEN on 2026-06-01. SkyMeter detected a low approach-stability score at 69WT (69WT) on runway 33W at 16:40 UTC. Trace data at the event: 1086 ft AGL, 132 kt GS. Approach stability score: 43/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, 2 kt crosswind component. 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)- HAZARDS6/2318 2026-05-22 14:00Z – 2026-06-05 04:00Z SFC–9,000 ft
17NM SW HELENA, MT, Friday, May 22, 2026 through Friday, June 5, 2026 UTC
View FAA NOTAM → - HAZARDS6/2646 2026-05-25 15:00Z – 2026-06-08 04:00Z SFC–11,000 ft
22NM SE JACKSON, WY, Monday, May 25, 2026 through Monday, June 8, 2026 UTC
View FAA NOTAM → - HAZARDS6/3585 2026-05-28 14:00Z – 2026-06-11 03:00Z SFC–9,000 ft
74NM S MILES CITY, MT, Thursday, May 28, 2026 through Thursday, June 11, 2026 UTC
View FAA NOTAM → - HAZARDS6/3649 2026-05-28 14:00Z – 2026-06-11 03:00Z SFC–9,000 ft
74NM S MILES CITY, MT, Thursday, May 28, 2026 through Thursday, June 11, 2026 UTC
View FAA NOTAM → - HAZARDS6/3889 2026-05-28 22:59Z – 2026-06-10 04:00Z SFC–10,500 ft
11NM SE SPANISH FORK, UT, Thursday, May 28, 2026 through Wednesday, June 10, 2026 UTC
View FAA NOTAM → - HAZARDS6/3574 2026-05-29 14:00Z – 2026-06-10 02:00Z SFC–13,000 ft
38NM SE TWIN FALLS, ID, Friday, May 29, 2026 through Wednesday, June 10, 2026 UTC
View FAA NOTAM → - HAZARDS6/3888 2026-05-29 14:00Z – 2026-06-10 04:00Z SFC–13,000 ft
38NM SE TWIN FALLS, ID, Friday, May 29, 2026 through Wednesday, June 10, 2026 UTC
View FAA NOTAM → - HAZARDS6/3908 2026-05-29 14:00Z – 2026-06-12 04:00Z SFC–9,000 ft
23NM SE GLENDIVE, MT, Friday, May 29, 2026 through Friday, June 12, 2026 UTC
View FAA NOTAM → - SECURITY6/4158 2026-06-01 06:00Z – 2026-07-21 05:59Z SFC–400 ft
MERIDIAN, ID, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4164 2026-06-01 06:00Z – 2026-07-21 05:59Z SFC–400 ft
Sandy, UT, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4167 2026-06-01 06:00Z – 2026-07-21 05:59Z SFC–400 ft
Salt Lake City, UT, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4033 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
RENTON, WA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - HAZARDS6/4299 2026-06-01 13:00Z – 2026-06-04 23:00Z SFC–10,000 ft
43NM SW GREEN RIVER, WY, Monday, June 1, 2026 through Thursday, June 4, 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 33W
- 1086 ft AGL at event
- 132 kt ground speed
- 0 fpm vertical
- Approach stability 43/100
- 5 kt wind
- 2 kt crosswind component
Flight context
- FFT4545
- Bank of Utah
- A21N
- 2026-06-01 16:40 UTC
- 69WT runway 33W
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