Unstable approach — N406NL

KSLE · 31

2026-08-10 22:26 UTC· PAKW KSLE· L&N TRANSIT LLC· F2TH

N406NL (L&n Transit) was operating from PAKW to KSLE on 2026-08-10. SkyMeter detected a low approach-stability score at Salem Municipal Airport/McNary Field (KSLE) on runway 31 at 22:26 UTC. Trace data at the event: 1288 ft AGL, 144 kt GS. Approach stability score: 45/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 10 kt wind, 9 kt crosswind component, 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 31
  • 1288 ft AGL at event
  • 144 kt ground speed
  • 0 fpm vertical
  • Approach stability 45/100
  • 10 kt wind
  • 9 kt crosswind component
  • 16,093 m visibility
  • KSLE 160956Z AUTO 34004KT 10SM CLR 12/11 A3003 RMK AO2 SLP170 T01220106 $

Flight context

  • N406NL
  • L&n Transit
  • F2TH
  • PAKW → KSLE
  • 2026-08-10 22:26 UTC
  • KSLE runway 31

All events on this flight

Unstable approach 22:26:20 UTC · KSLE runway 31 · 1,288 ft AGL · 144 kt GS
Unstable approach 22:26:20 UTC · KSLE runway 31 · 1,288 ft AGL · 144 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· KSLE