Unstable approach — EJA759

EJA759 (Netjets Sales) was operating from KPDX to KGEG on 2026-07-20. SkyMeter detected a low approach-stability score at Spokane International Airport (KGEG) on runway 8 at 15:14 UTC. Trace data at the event: 3432 ft AGL, 122 kt GS. Approach stability score: 40/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, 4 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/4011 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

  BELLEVUE, WA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4033 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

  RENTON, WA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4034 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

  Renton, WA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4040 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

  Portland, OR, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/8071 2026-07-08 16:07Z – 2026-07-21 06:59Z SFC–400 ft

  PORTLAND, OR

  View FAA NOTAM →
• SECURITY6/8073 2026-07-12 17:07Z – 2026-07-21 06:59Z SFC–400 ft

  Renton, WA

  View FAA NOTAM →
• SECURITY6/8074 2026-07-12 17:07Z – 2026-07-21 06:59Z SFC–400 ft

  Renton, WA

  View FAA NOTAM →
• SECURITY6/8081 2026-07-12 17:07Z – 2026-07-21 06:59Z SFC–400 ft

  Bellevue, WA

  View FAA NOTAM →
• HAZARDS6/6314 2026-07-16 21:42Z – 2026-07-31 04:00Z SFC–8,500 ft

  12NM NW CLE ELUM, WA, Thursday, July 16, 2026 through Friday, July 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6401 2026-07-17 04:01Z – 2026-07-31 04:00Z SFC–8,500 ft

  12NM NW CLE ELUM, WA, Friday, July 17, 2026 through Friday, July 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6536 2026-07-17 21:00Z – 2026-08-01 04:00Z SFC–8,000 ft

  23NM NE PENDLETON, OR, Friday, July 17, 2026 through Saturday, August 1, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6537 2026-07-17 21:00Z – 2026-08-01 04:00Z SFC–9,000 ft

  14NM E WALLA WALLA, WA, Friday, July 17, 2026 through Saturday, August 1, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6564 2026-07-18 00:42Z – 2026-07-31 03:00Z SFC–9,000 ft

  24NM E PENDLETON, OR, Saturday, July 18, 2026 through Friday, July 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6568 2026-07-18 01:12Z – 2026-07-31 03:00Z SFC–6,000 ft

  48NM NE KENNEWICK, WA, Saturday, July 18, 2026 through Friday, July 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6571 2026-07-18 02:41Z – 2026-07-31 04:00Z SFC–3,500 ft

  19NM S MOSES LAKE, WA, Saturday, July 18, 2026 through Friday, July 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6666 2026-07-18 15:00Z – 2026-07-31 05:00Z SFC–8,000 ft

  23NM NE PENDLETON, OR, Saturday, July 18, 2026 through Friday, July 31, 2026 UTC

  View FAA NOTAM →
• SECURITY6/6147 2026-07-19 16:00Z – 2026-07-24 04:00Z SFC–1,000 ft

  Bellevue, WA, Sunday, July 19, 2026 through Thursday, July 23, 2026 Local

  View FAA NOTAM →
• HAZARDS6/6866 2026-07-20 14:00Z – 2026-08-04 04:00Z SFC–9,000 ft

  PENDLETON, OR, Monday, July 20, 2026 through Tuesday, August 4, 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