Unstable approach — XLJ909

XLJ909 (Xcel JET Management) was operating from K6S5 to KBFI on 2026-09-01. SkyMeter detected a low approach-stability score at Boeing Field King County International Airport (KBFI) on runway 14L at 20:05 UTC. Trace data at the event: 1074 ft AGL, 120 kt GS. Approach stability score: 44/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 8 kt wind, 7 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.

• HAZARDS6/6719 2026-08-20 14:00Z – 2026-09-02 04:00Z SFC–11,000 ft

  12NM W PLAINS, MT, Thursday, August 20, 2026 through Wednesday, September 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6935 2026-08-21 15:00Z – 2026-09-04 04:00Z SFC–10,000 ft

  48NM NE OROFINO, ID, Friday, August 21, 2026 through Friday, September 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7094 2026-08-22 03:30Z – 2026-09-04 04:00Z SFC–10,000 ft

  12NM NW CLE ELUM, WA, Saturday, August 22, 2026 through Friday, September 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7095 2026-08-22 14:00Z – 2026-09-05 04:00Z SFC–11,000 ft

  10NM W PLAINS, MT, Saturday, August 22, 2026 through Saturday, September 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7122 2026-08-23 03:50Z – 2026-09-05 04:00Z SFC–13,500 ft

  20NM N LEAVENWORTH, WA, Sunday, August 23, 2026 through Saturday, September 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7285 2026-08-23 18:00Z – 2026-09-06 04:00Z SFC–8,500 ft

  GRANDVIEW, WA, Sunday, August 23, 2026 through Sunday, September 6, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7286 2026-08-23 19:00Z – 2026-09-06 04:00Z SFC–10,000 ft

  12NM NW CLE ELUM, WA, Sunday, August 23, 2026 through Sunday, September 6, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7337 2026-08-24 14:00Z – 2026-09-08 03:30Z SFC–10,000 ft

  11NM SE HAMILTON, MT, Monday, August 24, 2026 through Tuesday, September 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7668 2026-08-25 14:00Z – 2026-09-08 03:30Z SFC–10,000 ft

  11NM SE HAMILTON, MT, Tuesday, August 25, 2026 through Tuesday, September 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8096 2026-08-26 14:00Z – 2026-09-08 04:00Z SFC–10,000 ft

  37NM SE TACOMA, WA, Wednesday, August 26, 2026 through Tuesday, September 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8106 2026-08-26 14:00Z – 2026-09-10 03:30Z SFC–12,500 ft

  11NM SE HAMILTON, MT, Wednesday, August 26, 2026 through Thursday, September 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8520 2026-08-27 15:00Z – 2026-09-10 04:30Z SFC–9,000 ft

  15NM E KELLOGG, ID, Thursday, August 27, 2026 through Thursday, September 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8758 2026-08-28 02:30Z – 2026-09-10 04:00Z SFC–10,000 ft

  12NM NW CLE ELUM, WA, Friday, August 28, 2026 through Thursday, September 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8759 2026-08-28 15:00Z – 2026-09-11 03:00Z SFC–5,000 ft

  3NM N LEWISTON, ID, Friday, August 28, 2026 through Friday, September 11, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9172 2026-08-30 01:00Z – 2026-09-14 03:00Z SFC–14,500 ft

  10NM N LEAVENWORTH, WA, Sunday, August 30, 2026 through Monday, September 14, 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