Unstable approach — N2017F
KALO · 182026-08-17 13:40 UTC· KD02 → KALO· BANK OF UTAH TRUSTEE· AT6T
N2017F (Bank of Utah) was operating from KD02 to KALO on 2026-08-17. SkyMeter detected a low approach-stability score at Waterloo Regional Airport (KALO) on runway 18 at 13:40 UTC. Trace data at the event: 1963 ft AGL, 168 kt GS. Approach stability score: 32/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 4 kt wind, 4 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.
Pilot review data
- Runway 18
- 1963 ft AGL at event
- 168 kt ground speed
- 0 fpm vertical
- Approach stability 32/100
- 4 kt wind
- 4 kt crosswind component
- 16,093 m visibility
- KALO 162154Z 12006KT 10SM OVC028 22/17 A3022 RMK AO2 SLP233 T02220167 $
Flight context
- N2017F
- Bank of Utah
- AT6T
- KD02 → KALO
- 2026-08-17 13:40 UTC
- KALO runway 18
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