Unstable approach — BTLE81

LKPD · 27

2026-07-15 08:28 UTC· LKPD LKPD· L39

BTLE81 was operating from LKPD to LKPD on 2026-07-15. SkyMeter detected a low approach-stability score at Pardubice Airport (LKPD) on runway 27 at 08:28 UTC. Trace data at the event: 1589 ft AGL, 146 kt GS. Approach stability score: 25/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 2 kt wind, 2 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 27
  • 1589 ft AGL at event
  • 146 kt ground speed
  • 0 fpm vertical
  • Approach stability 25/100
  • 2 kt wind
  • 2 kt crosswind component
  • 9,994 m visibility
  • LKPD 121800Z 03006KT 350V060 CAVOK 24/05 Q1026 NOSIG

Flight context

  • BTLE81
  • L39
  • LKPD → LKPD
  • 2026-07-15 08:28 UTC
  • LKPD runway 27

All events on this flight

Unstable approach 08:28:36 UTC · LKPD runway 27 · 1,589 ft AGL · 146 kt GS
Unstable approach 08:28:36 UTC · LKPD runway 27 · 1,589 ft AGL · 146 kt GS
Unstable approach 08:28:36 UTC · LKPD runway 27 · 1,589 ft AGL · 146 kt GS
Unstable approach 08:28:36 UTC · LKPD runway 27 · 1,589 ft AGL · 146 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· LKPD