Unstable approach — AEZ126F

LIEA · 02

2026-07-03 12:39 UTC· LIRF LIEA· B738

AEZ126F was operating from LIRF to LIEA on 2026-07-03. SkyMeter detected a low approach-stability score at Alghero-Fertilia Airport (LIEA) on runway 02 at 12:39 UTC. Trace data at the event: 936 ft AGL, 139 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, 1 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 02
  • 936 ft AGL at event
  • 139 kt ground speed
  • 0 fpm vertical
  • Approach stability 44/100
  • 9 kt wind
  • 1 kt crosswind component
  • 9,994 m visibility
  • LIEA 150850Z 03006KT 330V080 CAVOK 33/20 Q1014

Flight context

  • AEZ126F
  • B738
  • LIRF → LIEA
  • 2026-07-03 12:39 UTC
  • LIEA runway 02

All events on this flight

Unstable approach 12:39:22 UTC · LIEA runway 02 · 936 ft AGL · 139 kt GS
Unstable approach 12:39:22 UTC · LIEA runway 02 · 936 ft AGL · 139 kt GS
Unstable approach 12:39:22 UTC · LIEA runway 02 · 936 ft AGL · 139 kt GS
Unstable approach 12:39:22 UTC · LIEA runway 02 · 936 ft AGL · 139 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· LIEA