Unstable approach — N32KE

N32KE (Taildragger) was operating from CYXS to KCOE on 2026-08-27. SkyMeter detected a low approach-stability score at Coeur D'Alene - Pappy Boyington Field (KCOE) on runway 24 at 23:32 UTC. Trace data at the event: 3369 ft AGL, 139 kt GS. Approach stability score: 43/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, 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.

• HAZARDS6/5097 2026-08-14 15:00Z – 2026-08-28 03:00Z SFC–9,000 ft

  42NM NW SPOKANE, WA, Friday, August 14, 2026 through Friday, August 28, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5135 2026-08-14 18:00Z – 2026-08-29 04:00Z SFC–13,500 ft

  26NM NW LEAVENWORTH, WA, Friday, August 14, 2026 through Saturday, August 29, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5247 2026-08-16 14:00Z – 2026-08-31 04:00Z SFC–10,500 ft

  19NM N OMAK, WA, Sunday, August 16, 2026 through Monday, August 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5245 2026-08-16 15:00Z – 2026-08-30 05:00Z SFC–12,000 ft

  47NM NE BELLINGHAM, WA, Sunday, August 16, 2026 through Sunday, August 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5941 2026-08-18 04:00Z – 2026-08-31 04:00Z SFC–13,500 ft

  26NM NW LEAVENWORTH, WA, Tuesday, August 18, 2026 through Monday, August 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5939 2026-08-18 14:00Z – 2026-08-31 05:00Z SFC–10,000 ft

  21NM S PORT ANGELES, WA, Tuesday, August 18, 2026 through Monday, August 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5940 2026-08-18 15:00Z – 2026-08-31 04:00Z SFC–7,500 ft

  20NM E OKANOGAN, WA, Tuesday, August 18, 2026 through Monday, August 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6931 2026-08-21 00:15Z – 2026-08-31 04:00Z SFC–8,000 ft

  12NM N KETTLE FALLS, WA, Friday, August 21, 2026 through Monday, August 31, 2026 UTC

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

  19NM N OMAK, WA, Friday, August 21, 2026 through Friday, September 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6962 2026-08-21 15:00Z – 2026-08-31 04:00Z SFC–8,000 ft

  12NM N KETTLE FALLS, WA, Friday, August 21, 2026 through Monday, August 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7007 2026-08-21 16:30Z – 2026-08-28 04:00Z SFC–13,500 ft

  28NM W TWISP, WA, Friday, August 21, 2026 through Friday, August 28, 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/7120 2026-08-23 04:00Z – 2026-09-04 04:00Z SFC–10,500 ft

  22NM N OMAK, WA, Sunday, August 23, 2026 through Friday, September 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8104 2026-08-26 14:00Z – 2026-09-09 05:00Z SFC–12,000 ft

  14NM SW BONNERS FERRY, ID, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8673 2026-08-27 22:55Z – 2026-08-29 04:00Z SFC–4,500 ft

  9NM W KINGSTON, WA, Thursday, August 27, 2026 through Saturday, August 29, 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