Unstable approach — LN30LJ

LN30LJ (Worldwide Aircraft Services) was operating from KBUF to KABQ on 2026-08-29. SkyMeter detected a low approach-stability score at Salina Municipal Airport (KSLN) on runway 17 at 18:23 UTC. Trace data at the event: 2377 ft AGL, 144 kt GS. Approach stability score: 68/100. Scores in this band occur on roughly 10-15% of approaches at this runway, with multiple gates outside the per-runway envelope. METAR at the time reported 20 kt wind, 3 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.

• SECURITY6/0708 2026-08-01 00:01Z – 2027-08-01 23:59Z SFC–400 ft

  Goodlettsville, TN, Saturday, August 1, 2026 through Sunday, August 1, 2027 UTC

  View FAA NOTAM →
• HAZARDS6/1462 2026-08-04 13:00Z – 2026-09-01 04:00Z SFC–15,000 ft

  20NM SW PUEBLO, CO, Tuesday, August 4, 2026 through Tuesday, September 1, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5409 2026-08-17 04:00Z – 2026-08-30 04:00Z SFC–13,500 ft

  13NM N SANTA FE, NM, Monday, August 17, 2026 through Sunday, August 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6216 2026-08-19 03:00Z – 2026-09-02 03:00Z SFC–13,500 ft

  13NM N SANTA FE, NM, Wednesday, August 19, 2026 through Wednesday, September 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8502 2026-08-27 14:00Z – 2026-09-09 03:00Z SFC–15,000 ft

  48NM NW TAOS, NM, Thursday, August 27, 2026 through Wednesday, September 9, 2026 UTC

  View FAA NOTAM →
• SECURITY6/6997 2026-08-27 15:00Z – 2026-08-31 03:00Z SFC–400 ft

  Plymouth, MI, Thursday, August 27, 2026 through Sunday, August 30, 2026 Local

  View FAA NOTAM →
• HAZARDS6/8590 2026-08-27 18:00Z – 2026-09-09 03:00Z SFC–13,500 ft

  13NM N SANTA FE, NM, Thursday, August 27, 2026 through Wednesday, September 9, 2026 UTC

  View FAA NOTAM →
• SECURITY6/6989 2026-08-27 21:00Z – 2026-09-02 21:00Z SFC–400 ft

  Asheville, NC, Thursday, August 27, 2026 through Wednesday, September 2, 2026 Local

  View FAA NOTAM →
• SECURITY6/6995 2026-08-28 10:00Z – 2026-08-30 23:59Z SFC–400 ft

  Grand Blanc, MI, Friday, August 28, 2026 through Sunday, August 30, 2026 Local

  View FAA NOTAM →
• AIR SHOWS/SPORTS6/8224 2026-08-28 14:00Z – 2026-08-30 23:00Z SFC–16,000 ft

  Bunker Hill, IN, Friday, August 28, 2026 through Sunday, August 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8806 2026-08-28 15:04Z – 2026-09-12 03:00Z SFC–15,000 ft

  30NM W TAOS, NM, Friday, August 28, 2026 through Saturday, September 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8869 2026-08-28 21:32Z – 2026-09-12 03:00Z SFC–10,000 ft

  18NM SW LOVELAND, CO, Friday, August 28, 2026 through Saturday, September 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8889 2026-08-28 23:25Z – 2026-09-12 04:00Z SFC–13,500 ft

  15NM SW LAS VEGAS, NM, Friday, August 28, 2026 through Saturday, September 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9082 2026-08-29 13:00Z – 2026-09-12 04:00Z SFC–13,500 ft

  15NM SW LAS VEGAS, NM, Saturday, August 29, 2026 through Saturday, September 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8870 2026-08-29 14:00Z – 2026-09-12 03:00Z SFC–15,000 ft

  30NM W TAOS, NM, Saturday, August 29, 2026 through Saturday, September 12, 2026 UTC

  View FAA NOTAM →
• AIR SHOWS/SPORTS6/7379 2026-08-29 18:00Z – 2026-08-30 22:00Z SFC–16,500 ft

  Janesville, WI, Saturday, August 29, 2026 through Sunday, August 30, 2026 UTC

  View FAA NOTAM →

SkyMeter cross-referenced this flight against FAA-published TFRs that were active during its window and within its geographic bounding box. Overlap doesn't necessarily mean violation — the aircraft may have been outside the TFR’s precise polygon or flying under air-traffic-control coordination.

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