Go-around — VLG8JE

LEAS · 11

2025-10-30 17:17 UTC· EGLL → LEBB· A320

VLG8JE was operating from EGLL to LEBB on 2025-10-30. SkyMeter detected a go-around at Asturias Airport (LEAS) on runway 11 at 17:17 UTC. Trace data at the event: 306 ft AGL, 150 kt GS, 0 fpm vertical. METAR at the time reported 9 kt wind, 9 kt crosswind component, 9,999 m visibility. A go-around is a discontinued landing approach in which the pilot adds power and climbs back to a safe altitude before re-attempting the approach or proceeding to an alternate. It is a routine safety response, not an emergency, and is taught as the standard reaction to any unstable approach. Detection algorithm and known limitations: see SkyMeter methodology.

Pilot review data

  • Runway 11
  • 306 ft AGL at event
  • 150 kt ground speed
  • 0 fpm vertical
  • 9 kt wind
  • 9 kt crosswind component
  • 9,999 m visibility
  • METAR LEAS 271730Z 10003KT 050V160 9999 FEW060 20/18 Q1017 NOSIG

Flight context

  • VLG8JE
  • A320
  • EGLL → LEBB
  • 2025-10-30 17:17 UTC
  • LEAS runway 11

All events on this flight

Go-around 17:17:51 UTC · LEAS runway 11 · 306 ft AGL · 150 kt GS
Go-around 17:17:51 UTC · LEAS runway 11 · 306 ft AGL · 150 kt GS
Go-around 17:32:50 UTC · LEAS runway 11 · 331 ft AGL · 152 kt GS
Go-around 17:32:50 UTC · LEAS runway 11 · 331 ft AGL · 152 kt GS
Go-around 17:17:34 UTC · LEBB runway 12 · 304 ft AGL · 147 kt GS
Go-around 17:17:34 UTC · LEBB runway 12 · 304 ft AGL · 147 kt GS
Go-around 17:32:37 UTC · LEBB runway 12 · 333 ft AGL · 153 kt GS
Go-around 17:32:37 UTC · LEBB runway 12 · 333 ft AGL · 153 kt GS
Go-around 17:17:34 UTC · LEBB runway 12 · 304 ft AGL · 147 kt GS
Go-around 17:17:34 UTC · LEBB runway 12 · 304 ft AGL · 147 kt GS
Go-around 17:32:37 UTC · LEBB runway 12 · 333 ft AGL · 153 kt GS
Go-around 17:32:37 UTC · LEBB runway 12 · 333 ft AGL · 153 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· LEAS