Unstable approach — SKW3115

SKW3115 (Skywest Airlines) was operating from KPDX to KSTS on 2026-07-25. SkyMeter detected a low approach-stability score at Charles M. Schulz Sonoma County Airport (KSTS) on runway 14 at 06:28 UTC. Trace data at the event: 1241 ft AGL, 145 kt GS. Approach stability score: 58/100. Scores in this band occur on roughly 10-15% of approaches at this runway, with multiple gates outside the per-runway envelope. METAR at the time reported 3 kt wind, 1 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/6363 2026-07-17 01:54Z – 2026-07-31 04:00Z SFC–8,000 ft

  20NM NW MEDFORD, OR, Friday, July 17, 2026 through Friday, July 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6409 2026-07-17 04:39Z – 2026-07-30 07:00Z SFC–11,000 ft

  10NM SW MOUNT SHASTA, CA, Friday, July 17, 2026 through Thursday, July 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7914 2026-07-22 18:44Z – 2026-08-05 04:00Z SFC–7,000 ft

  20NM NW MEDFORD, OR, Wednesday, July 22, 2026 through Wednesday, August 5, 2026 UTC

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

  35NM E ROSEBURG, OR, Friday, July 24, 2026 through Wednesday, August 5, 2026 UTC

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

  35NM SE ROSEBURG, OR, Friday, July 24, 2026 through Friday, August 7, 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