Unstable approach — TWY295

TWY295 (GG 295) was operating from KSAN to KPUW on 2026-07-05. SkyMeter detected a low approach-stability score at Pullman Moscow Regional Airport (KPUW) on runway 05 at 20:49 UTC. Trace data at the event: 3645 ft AGL, 138 kt GS. Approach stability score: 36/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 7 kt wind, 6 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.

• SECURITY6/4182 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

  Irvine, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  San Diego, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Los Angeles, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  IRVINE, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Dana Point, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  San Diego, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  San Diego, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/7265 2026-06-12 21:07Z – 2026-07-16 06:29Z SFC–400 ft

  Manhattan Beach, CA

  View FAA NOTAM →
• SECURITY6/7820 2026-06-29 15:07Z – 2026-07-21 06:59Z SFC–400 ft

  San Diego, CA

  View FAA NOTAM →
• SECURITY6/7821 2026-06-29 15:07Z – 2026-07-21 06:59Z SFC–400 ft

  San Diego, CA

  View FAA NOTAM →
• HAZARDS6/1675 2026-06-29 21:09Z – 2026-07-13 04:00Z SFC–6,000 ft

  75 ZSE AIRSPACE 13NM SE PASCO, WA, Monday, June 29, 2026 through Monday, July 13, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1787 2026-06-30 15:00Z – 2026-07-14 04:00Z SFC–6,000 ft

  13NM SE PASCO, WA, Tuesday, June 30, 2026 through Tuesday, July 14, 2026 UTC

  View FAA NOTAM →
• UAS PUBLIC GATHERING6/0753 2026-07-02 14:00Z – 2026-07-06 04:00Z SFC–400 ft

  Los Angeles, CA, Thursday, July 2, 2026 through Monday, July 6, 2026 UTC

  View FAA NOTAM →
• UAS PUBLIC GATHERING6/1486 2026-07-04 14:00Z – 2026-07-06 04:00Z SFC–400 ft

  Los Angeles, CA, Saturday, July 4, 2026 through Monday, July 6, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2989 2026-07-05 17:35Z – 2026-07-20 05:00Z SFC–7,000 ft

  15NM E PENDLETON, OR, Sunday, July 5, 2026 through Monday, July 20, 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