Unstable approach — N71VM

KSTS · 20

2026-06-13 20:59 UTC· KVGT → KSTS· VIMARK INC, TRIONE MARK, TRIONE VICTOR· C25B

▶ Replay 📊 Analyse

N71VM (Vimark) was operating from KVGT to KSTS on 2026-06-13. SkyMeter detected a low approach-stability score at Charles M. Schulz Sonoma County Airport (KSTS) on runway 20 at 20:59 UTC. Trace data at the event: 1223 ft AGL, 172 kt GS. Approach stability score: 27/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 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.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • 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/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 →
  • HAZARDS6/7765 2026-06-11 22:46Z – 2026-06-13 23:59Z SFC–400 ft

    3.8NM NW TRACY, CA, Thursday, June 11, 2026 through Saturday, June 13, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/7800 2026-06-12 00:56Z – 2026-06-13 23:59Z SFC–400 ft

    3.8NM NW TRACY, CA, Friday, June 12, 2026 through Saturday, June 13, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/7890 2026-06-12 14:46Z – 2026-06-13 23:59Z SFC–400 ft

    3.8NM NW TRACY, CA, Friday, June 12, 2026 through Saturday, June 13, 2026 UTC

    View FAA NOTAM →
  • SECURITY6/7618 2026-06-13 16:00Z – 2026-06-14 01:00Z SFC–3,000 ft

    San Francisco, CA, Saturday, June 13, 2026 through Saturday, June 13, 2026 Local

    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.

Pilot review data

  • Runway 20
  • 1223 ft AGL at event
  • 172 kt ground speed
  • 0 fpm vertical
  • Approach stability 27/100
  • 6 kt wind
  • 1 kt crosswind component
  • 16,093 m visibility
  • KSTS 120653Z AUTO 26006KT 10SM CLR 09/07 A2977 RMK AO2 SLP074 T00890067

Flight context

  • N71VM
  • Vimark
  • C25B
  • KVGT → KSTS
  • 2026-06-13 20:59 UTC
  • KSTS runway 20

All events on this flight

Unstable approach 20:59:35 UTC · KSTS runway 20 · 1,223 ft AGL · 172 kt GS
Unstable approach 20:59:35 UTC · KSTS runway 20 · 1,223 ft AGL · 172 kt GS

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

SkyMeter · trace data observed via ADS-B· KSTS