Unstable approach — ELY343

LSZH · 34

2026-07-19 18:59 UTC· LLBG LSZH· B738

ELY343 was operating from LLBG to LSZH on 2026-07-19. SkyMeter detected a low approach-stability score at Zürich Airport (LSZH) on runway 34 at 18:59 UTC. Trace data at the event: 2265 ft AGL, 151 kt GS. Approach stability score: 38/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, 4 kt crosswind component, 9,994 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 34
  • 2265 ft AGL at event
  • 151 kt ground speed
  • 0 fpm vertical
  • Approach stability 38/100
  • 7 kt wind
  • 4 kt crosswind component
  • 9,994 m visibility
  • LSZH 121250Z 04010KT 010V080 CAVOK 31/12 Q1023 NOSIG

Flight context

  • ELY343
  • B738
  • LLBG → LSZH
  • 2026-07-19 18:59 UTC
  • LSZH runway 34

All events on this flight

Unstable approach 18:59:19 UTC · LSZH runway 34 · 2,265 ft AGL · 151 kt GS
Unstable approach 18:59:19 UTC · LSZH runway 34 · 2,265 ft AGL · 151 kt GS
Unstable approach 18:59:19 UTC · LSZH runway 34 · 2,265 ft AGL · 151 kt GS
Unstable approach 18:59:19 UTC · LSZH runway 34 · 2,265 ft AGL · 151 kt GS

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

SkyMeter · trace data observed via ADS-B· LSZH