Unstable approach — PCJ14

KAPC · 18R

2026-09-01 21:51 UTC· KCMA KAPC· MEDIUM PLANE LLC· LJ60

PCJ14 (Medium Plane) was operating from KCMA to KAPC on 2026-09-01. SkyMeter detected a low approach-stability score at Napa County Airport (KAPC) on runway 18R at 21:51 UTC. Trace data at the event: 1043 ft AGL, 133 kt GS. Approach stability score: 41/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 8 kt wind, 2 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/6491 2026-07-20 07:01Z – 2026-09-16 06:59Z SFC–1,499 ft

    Concord, CA, Monday, July 20, 2026 through Tuesday, September 15, 2026 Local

    View FAA NOTAM →
  • HAZARDS6/8070 2026-08-26 03:00Z – 2026-09-10 03:00Z SFC–8,500 ft

    8NM SE BIG SUR, CA, Wednesday, August 26, 2026 through Thursday, September 10, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/8454 2026-08-26 21:15Z – 2026-09-09 03:00Z SFC–7,500 ft

    20NM SW KING CITY, CA, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/8493 2026-08-27 13:00Z – 2026-09-10 03:00Z SFC–8,000 ft

    20NM SW KING CITY, CA, Thursday, August 27, 2026 through Thursday, September 10, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/8735 2026-08-28 13:00Z – 2026-09-13 03:00Z SFC–8,000 ft

    20NM SW KING CITY, CA, Friday, August 28, 2026 through Sunday, September 13, 2026 UTC

    View FAA NOTAM →
  • UAS PUBLIC GATHERING6/7555 2026-08-29 01:00Z – 2026-09-02 06:59Z SFC–400 ft

    Santa Clara, CA, Saturday, August 29, 2026 through Wednesday, September 2, 2026 UTC

    View FAA NOTAM →
  • UAS PUBLIC GATHERING6/7569 2026-08-29 01:00Z – 2026-09-02 06:59Z SFC–400 ft

    Santa Clara, CA, Saturday, August 29, 2026 through Wednesday, September 2, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/8902 2026-08-29 13:00Z – 2026-09-13 03:00Z SFC–8,500 ft

    20NM SW KING CITY, CA, Saturday, August 29, 2026 through Sunday, September 13, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/9187 2026-08-30 13:00Z – 2026-09-13 03:00Z SFC–8,500 ft

    20NM SW KING CITY, CA, Sunday, August 30, 2026 through Sunday, September 13, 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 18R
  • 1043 ft AGL at event
  • 133 kt ground speed
  • 0 fpm vertical
  • Approach stability 41/100
  • 8 kt wind
  • 2 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

  • PCJ14
  • Medium Plane
  • LJ60
  • KCMA → KAPC
  • 2026-09-01 21:51 UTC
  • KAPC runway 18R

All events on this flight

Unstable approach 21:51:53 UTC · KAPC runway 18R · 1,043 ft AGL · 133 kt GS
Long landing rollout 20:18:49 UTC · KVNY runway 16R · 774 ft AGL · 0 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· KAPC