Unstable approach — N20TQ

N20TQ (ONB Aviation) was operating from KHHR to KPUW on 2026-09-02. SkyMeter detected a low approach-stability score at Pullman Moscow Regional Airport (KPUW) on runway 05 at 06:08 UTC. Trace data at the event: 3687 ft AGL, 142 kt GS. Approach stability score: 41/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 2 kt wind, 2 kt crosswind component, 14,484 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/6726 2026-08-20 03:15Z – 2026-09-03 04:00Z SFC–9,000 ft

  25NM E PENDLETON, OR, Thursday, August 20, 2026 through Thursday, September 3, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7123 2026-08-23 14:00Z – 2026-09-05 04:00Z SFC–12,500 ft

  18NM W BAKER CITY, OR, Sunday, August 23, 2026 through Saturday, September 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7124 2026-08-23 14:00Z – 2026-09-05 04:00Z SFC–12,500 ft

  18NM W BAKER CITY, OR, Sunday, August 23, 2026 through Saturday, September 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8094 2026-08-26 03:00Z – 2026-09-09 04:00Z SFC–9,000 ft

  15NM E WALLA WALLA, WA, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8093 2026-08-26 03:30Z – 2026-09-09 04:00Z SFC–9,000 ft

  25NM E PENDLETON, OR, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8095 2026-08-26 14:00Z – 2026-09-09 04:00Z SFC–12,500 ft

  17NM W BAKER CITY, OR, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8110 2026-08-26 14:00Z – 2026-09-09 04:00Z SFC–12,500 ft

  17NM W BAKER CITY, OR, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8332 2026-08-26 17:45Z – 2026-09-05 04:00Z SFC–11,000 ft

  51NM NE FALLON, NV, Wednesday, August 26, 2026 through Saturday, September 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8474 2026-08-27 00:30Z – 2026-09-04 03:00Z SFC–13,000 ft

  37NM N WINNEMUCCA, NV, Thursday, August 27, 2026 through Friday, September 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8507 2026-08-27 03:15Z – 2026-09-05 03:00Z SFC–11,000 ft

  51NM NE FALLON, NV, Thursday, August 27, 2026 through Saturday, September 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8501 2026-08-27 14:00Z – 2026-09-04 06:00Z SFC–11,000 ft

  104NM SE BURNS, OR, Thursday, August 27, 2026 through Friday, September 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8588 2026-08-27 18:00Z – 2026-09-09 03:00Z SFC–10,500 ft

  62NM NE WINNEMUCCA, NV, Thursday, August 27, 2026 through Wednesday, September 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8676 2026-08-27 23:15Z – 2026-09-10 03:00Z SFC–13,000 ft

  37NM N WINNEMUCCA, NV, Thursday, August 27, 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/9180 2026-08-30 14:00Z – 2026-09-14 09:00Z SFC–12,500 ft

  17NM W BAKER CITY, OR, 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