Long landing rollout — WAV4WA

PAFA · 20

2026-05-18 23:33 UTC· WRIGHT AIR SERVICE INC· PA31

▶ Replay 📊 Analyse

WAV4WA (Wright AIR Service) was inbound to PAFA on 2026-05-18. SkyMeter detected a long landing rollout at Fairbanks International Airport (PAFA) on runway 20 at 23:33 UTC. Trace data at the event: 0 ft AGL, 9 kt GS, 0 fpm vertical. METAR at the time reported 6 kt wind, 3 kt crosswind component, 6,437 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/4925 2026-03-08 10:00Z – 2026-11-01 09:59Z SFC–360 ft

    CLEAR, AK, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4926 2026-03-08 10:00Z – 2026-11-01 12:00Z SFC–2,600 ft

    CLEAR, AK, Sunday, March 8, 2026 through Sunday, November 1, 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
  • 0 ft AGL at event
  • 9 kt ground speed
  • 0 fpm vertical
  • 6 kt wind
  • 3 kt crosswind component
  • 6,437 m visibility
  • PAFA 161953Z 21004KT 4SM -RA BR BKN008 BKN026 OVC040 08/07 A2975 RMK AO2 SLP079 P0005 T00830072 $

Flight context

  • WAV4WA
  • Wright AIR Service
  • PA31
  • 2026-05-18 23:33 UTC
  • PAFA runway 20

All events on this flight

Long landing rollout 23:33:37 UTC · PAFA runway 20 · 0 ft AGL · 9 kt GS
Long landing rollout 23:33:37 UTC · PAFA runway 20 · 0 ft AGL · 9 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· PAFA