Unstable approach — N8206W

KBDN · 34

2026-06-05 18:23 UTC· SKYKING AVIATION SERVICES LLC· P28A

N8206W (Skyking Aviation Services) was inbound to KBDN on 2026-06-05. SkyMeter detected a low approach-stability score at Bend Municipal Airport (KBDN) on runway 34 at 18:23 UTC. Trace data at the event: 4023 ft AGL, 83 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 7 kt wind, 16,093 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 34
  • 4023 ft AGL at event
  • 83 kt ground speed
  • 0 fpm vertical
  • Approach stability 33/100
  • 7 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • METAR KBDN 160655Z AUTO 30005KT 10SM -RA BKN060 OVC070 11/08 A3004 RMK AO2 P0002

Flight context

  • N8206W
  • Skyking Aviation Services
  • P28A
  • 2026-06-05 18:23 UTC
  • KBDN runway 34

All events on this flight

Unstable approach 18:23:28 UTC · KBDN runway 34 · 4,023 ft AGL · 83 kt GS
Unstable approach 18:23:28 UTC · KBDN runway 35 · 4,023 ft AGL · 83 kt GS
Unstable approach 18:23:28 UTC · KBDN runway 35 · 4,023 ft AGL · 83 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· KBDN