Unstable approach — N11VH

KAPC · 19R

2026-08-05 23:14 UTC· KUAO KAPC· C25B

N11VH was operating from KUAO to KAPC on 2026-08-05. SkyMeter detected a low approach-stability score at Napa County Airport (KAPC) on runway 19R at 23:14 UTC. Trace data at the event: 1141 ft AGL, 120 kt GS. Approach stability score: 53/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 5 kt wind, 3 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)
  • 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 →
  • HAZARDS6/9403 2026-07-28 13:00Z – 2026-08-10 03:00Z SFC–7,000 ft

    20NM NW MEDFORD, OR, Tuesday, July 28, 2026 through Monday, August 10, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/9888 2026-07-29 13:00Z – 2026-08-12 03:00Z SFC–6,000 ft

    20NM NW MEDFORD, OR, Wednesday, July 29, 2026 through Wednesday, August 12, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/0890 2026-08-02 13:00Z – 2026-08-15 03:00Z SFC–5,000 ft

    20NM NW MEDFORD, OR, Sunday, August 2, 2026 through Saturday, August 15, 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.

Pilot review data

  • Runway 19R
  • 1141 ft AGL at event
  • 120 kt ground speed
  • 0 fpm vertical
  • Approach stability 53/100
  • 5 kt wind
  • 3 kt crosswind component
  • 16,093 m visibility
  • METAR KAPC 312354Z 25017G24KT 10SM CLR 21/12 A2989 RMK AO2 SLP112 T02110122 10228 20167 56013

Flight context

  • N11VH
  • C25B
  • KUAO → KAPC
  • 2026-08-05 23:14 UTC
  • KAPC runway 19R

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· KAPC