Unstable approach — AAL1717

AAL1717 (UMB Bank NA) was operating from KORD to CZBB on 2026-06-15. SkyMeter detected a low approach-stability score at Boundary Bay Airport (CZBB) on runway 21 at 19:27 UTC. Trace data at the event: 1074 ft AGL, 150 kt GS. Approach stability score: 42/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 5 kt wind, 5 kt crosswind component. 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/4348 2026-03-08 07:00Z – 2026-11-01 06:59Z SFC–2,400 ft

  GRAND FORKS AFB, ND, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local

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

  MERIDIAN, ID, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• 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/4013 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

  Seattle, 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 →
• HAZARDS6/5042 2026-06-02 19:48Z – 2026-06-16 23:59Z SFC–1,000 ft

  LONGVIEW, WA, Tuesday, June 2, 2026 through Tuesday, June 16, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5717 2026-06-04 19:29Z – 2026-06-16 23:59Z SFC–1,000 ft

  LONGVIEW, WA, Thursday, June 4, 2026 through Tuesday, June 16, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5894 2026-06-05 20:31Z – 2026-06-19 02:00Z SFC–10,000 ft

  38NM SE TWIN FALLS, ID, Friday, June 5, 2026 through Friday, June 19, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5936 2026-06-06 03:00Z – 2026-06-19 02:00Z SFC–7,500 ft

  27NM SE TWIN FALLS, ID, Saturday, June 6, 2026 through Friday, June 19, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7480 2026-06-11 12:00Z – 2026-06-23 03:00Z SFC–9,500 ft

  24NM SW CHADRON, NE, Thursday, June 11, 2026 through Tuesday, June 23, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8221 2026-06-14 20:07Z – 2026-06-28 03:00Z SFC–6,000 ft

  22NM SE RICHLAND, WA, Sunday, June 14, 2026 through Sunday, June 28, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8252 2026-06-15 04:35Z – 2026-06-26 04:00Z SFC–5,500 ft

  12NM NE PASCO, WA, Monday, June 15, 2026 through Friday, June 26, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8253 2026-06-15 15:00Z – 2026-06-30 05:00Z SFC–6,000 ft

  3NM W BENTON CITY, WA, Monday, June 15, 2026 through Tuesday, June 30, 2026 UTC

  View FAA NOTAM →
• SECURITY6/7941 2026-06-15 16:00Z – 2026-06-16 01:00Z SFC–3,000 ft

  Seattle, WA, Monday, June 15, 2026 through Monday, June 15, 2026 Local

  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.

All events on this flight

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