Unstable approach — IBB69QN

GCRR · 03

2026-07-03 20:45 UTC· GCXO GCRR· AT76

IBB69QN was operating from GCXO to GCRR on 2026-07-03. SkyMeter detected a low approach-stability score at Lanzarote Airport (GCRR) on runway 03 at 20:45 UTC. Trace data at the event: 901 ft AGL, 135 kt GS. Approach stability score: 33/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, 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 03
  • 901 ft AGL at event
  • 135 kt ground speed
  • 0 fpm vertical
  • Approach stability 33/100
  • 5 kt wind
  • 1 kt crosswind component
  • 9,994 m visibility
  • GCRR 152130Z 01010KT 340V050 9999 FEW023 24/20 Q1016

Flight context

  • IBB69QN
  • AT76
  • GCXO → GCRR
  • 2026-07-03 20:45 UTC
  • GCRR runway 03

All events on this flight

Unstable approach 20:45:43 UTC · GCRR runway 03 · 901 ft AGL · 135 kt GS
Unstable approach 20:45:43 UTC · GCRR runway 03 · 901 ft AGL · 135 kt GS
Unstable approach 20:45:43 UTC · GCRR runway 03 · 901 ft AGL · 135 kt GS
Unstable approach 20:45:43 UTC · GCRR runway 03 · 901 ft AGL · 135 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· GCRR