Unstable approach — WSN2

WSN2 (Healdsburg RED CAR Partners) was operating from KHHR to KSTS on 2026-07-17. SkyMeter detected a low approach-stability score at Charles M. Schulz Sonoma County Airport (KSTS) on runway 14 at 18:52 UTC. Trace data at the event: 1234 ft AGL, 121 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 6 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.

• SECURITY6/5797 2026-04-03 00:01Z – 2026-09-28 23:59Z SFC–400 ft

  SACRAMENTO, CA, Thursday, April 2, 2026 through Monday, September 28, 2026 Local

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

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

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

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

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

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

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

  BERKLEY, CA, Monday, June 1, 2026 through Tuesday, July 21, 2026 Local

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

  Santa Barbara, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

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

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

  Santa Clara, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Montecito, CA

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

  Goleta, CA

  View FAA NOTAM →
• SECURITY6/7843 2026-07-03 16:07Z – 2026-07-21 06:59Z SFC–400 ft

  Santa Barbara, CA

  View FAA NOTAM →
• SECURITY6/7847 2026-07-03 16:07Z – 2026-07-21 06:59Z SFC–400 ft

  Santa Barbara, CA

  View FAA NOTAM →
• SECURITY6/7983 2026-07-05 14:07Z – 2026-07-21 06:59Z SFC–400 ft

  San Jose, CA

  View FAA NOTAM →
• SECURITY6/7984 2026-07-05 14:07Z – 2026-07-21 06:59Z SFC–400 ft

  Oakland, CA

  View FAA NOTAM →
• SECURITY6/7985 2026-07-05 14:07Z – 2026-07-21 06:59Z SFC–400 ft

  San Jose, CA

  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