Unstable approach — N363D

KABI · 17R

2026-06-07 20:41 UTC· KLBB → KABI· REGISTRATION PENDING· BE20

N363D (Registration Pending) was operating from KLBB to KABI on 2026-06-07. SkyMeter detected a low approach-stability score at Abilene Regional Airport (KABI) on runway 17R at 20:41 UTC. Trace data at the event: 2889 ft AGL, 166 kt GS. Approach stability score: 23/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 15 kt wind, 3 kt crosswind component, 14,484 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 17R
  • 2889 ft AGL at event
  • 166 kt ground speed
  • 0 fpm vertical
  • Approach stability 23/100
  • 15 kt wind
  • 3 kt crosswind component
  • 14,484 m visibility
  • KABI 141752Z 17013KT 9SM FEW038 OVC060 31/19 A2999 RMK AO2 SLP127 T03060194 10306 20244 58008

Flight context

  • N363D
  • Registration Pending
  • BE20
  • KLBB → KABI
  • 2026-06-07 20:41 UTC
  • KABI runway 17R

All events on this flight

Unstable approach 20:41:27 UTC · KABI runway 17R · 2,889 ft AGL · 166 kt GS
Unstable approach 20:41:27 UTC · KABI runway 17R · 2,889 ft AGL · 166 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· KABI