Long landing rollout — AJO142

KAPC · 19L

2026-08-28 00:34 UTC· A346

AJO142 was inbound to KAPC on 2026-08-28. SkyMeter detected a long landing rollout at Napa County Airport (KAPC) on runway 19L at 00:34 UTC. Trace data at the event: 3 ft AGL, 3 kt GS, 0 fpm vertical. Approach stability score: 47/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, 3 kt crosswind component, 16,093 m visibility. A long landing rollout is detected when ground deceleration after touchdown is below the per-runway P10 envelope. It is an observational measure of rollout efficiency, not a runway-exit incident. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • SECURITY6/3475 2026-03-08 09:00Z – 2026-11-01 09:59Z SFC–180 ft

    BEALE AFB, CA, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local

    View FAA NOTAM →
  • 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 →

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 19L
  • 3 ft AGL at event
  • 3 kt ground speed
  • 0 fpm vertical
  • Approach stability 47/100
  • 6 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

  • AJO142
  • A346
  • 2026-08-28 00:34 UTC
  • KAPC runway 19L

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