Unstable approach — N560CX

N560CX (Spudaire) was operating from KSLE to KPSC on 2026-07-29. SkyMeter detected a low approach-stability score at Tri Cities Airport (KPSC) on runway 21R at 01:25 UTC. Trace data at the event: 1476 ft AGL, 162 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 11 kt wind, 5 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/6756 2026-07-19 15:45Z – 2026-08-02 04:00Z SFC–8,000 ft

  39NM NW JOHN DAY, OR, Sunday, July 19, 2026 through Sunday, August 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6778 2026-07-19 19:09Z – 2026-08-03 03:00Z SFC–8,000 ft

  1NM S FOSSIL, OR, Sunday, July 19, 2026 through Monday, August 3, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7177 2026-07-20 22:03Z – 2026-08-04 04:00Z SFC–8,000 ft

  1NM W CONDON, OR, Monday, July 20, 2026 through Tuesday, August 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7611 2026-07-22 03:41Z – 2026-08-05 04:00Z SFC–8,000 ft

  1NM S FOSSIL, OR, Wednesday, July 22, 2026 through Wednesday, August 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8322 2026-07-23 22:15Z – 2026-07-30 05:00Z SFC–8,000 ft

  8NM NE MADRAS, OR, Thursday, July 23, 2026 through Thursday, July 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8339 2026-07-24 00:45Z – 2026-08-07 05:00Z SFC–8,000 ft

  4NM S FOSSIL, OR, Friday, July 24, 2026 through Friday, August 7, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8438 2026-07-24 18:30Z – 2026-08-08 04:00Z SFC–9,500 ft

  25NM SW THE DALLES, OR, Friday, July 24, 2026 through Saturday, August 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8479 2026-07-24 20:30Z – 2026-08-08 04:00Z SFC–8,000 ft

  34NM SE THE DALLES, OR, Friday, July 24, 2026 through Saturday, August 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8488 2026-07-25 01:30Z – 2026-08-08 05:00Z SFC–8,000 ft

  32NM NE MADRAS, OR, Saturday, July 25, 2026 through Saturday, August 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8545 2026-07-25 17:00Z – 2026-08-09 04:00Z SFC–7,000 ft

  8NM SW THE DALLES, OR, Saturday, July 25, 2026 through Sunday, August 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8550 2026-07-25 18:00Z – 2026-08-09 05:00Z SFC–8,000 ft

  32NM NE MADRAS, OR, Saturday, July 25, 2026 through Sunday, August 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8566 2026-07-25 22:15Z – 2026-08-09 05:00Z SFC–8,000 ft

  4NM S FOSSIL, OR, Saturday, July 25, 2026 through Sunday, August 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8585 2026-07-26 14:00Z – 2026-08-09 05:00Z SFC–9,500 ft

  25NM SW THE DALLES, OR, Sunday, July 26, 2026 through Sunday, August 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8861 2026-07-26 22:45Z – 2026-08-10 05:00Z SFC–8,000 ft

  32NM NE MADRAS, OR, Sunday, July 26, 2026 through Monday, August 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9351 2026-07-27 22:00Z – 2026-08-11 22:00Z SFC–8,000 ft

  4NM S FOSSIL, OR, Monday, July 27, 2026 through Tuesday, August 11, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9561 2026-07-28 16:45Z – 2026-08-11 04:00Z SFC–8,000 ft

  32NM NE MADRAS, OR, Tuesday, July 28, 2026 through Tuesday, August 11, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9804 2026-07-28 22:00Z – 2026-08-11 04:00Z SFC–8,000 ft

  4NM S FOSSIL, OR, Tuesday, July 28, 2026 through Tuesday, August 11, 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