Long landing rollout — ASA229

PAFA · 20L

2026-05-03 18:56 UTC· PANC PAFA· ALASKA AIRLINES INC· B737

ASA229 (Alaska Airlines) was operating from PANC to PAFA on 2026-05-03. SkyMeter detected a long landing rollout at Fairbanks International Airport (PAFA) on runway 20L at 18:56 UTC. Trace data at the event: 0 ft AGL, 4 kt GS, 0 fpm vertical. METAR at the time reported 3 kt wind, 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/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 20L
  • 0 ft AGL at event
  • 4 kt ground speed
  • 0 fpm vertical
  • 3 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • PAFA 210453Z 00000KT 10SM BKN048 BKN065 BKN100 09/07 A2925 RMK AO2 SLP910 T00890067 $

Flight context

  • ASA229
  • Alaska Airlines
  • B737
  • PANC → PAFA
  • 2026-05-03 18:56 UTC
  • PAFA runway 20L

All events on this flight

Long landing rollout 18:56:14 UTC · PAFA runway 20L · 0 ft AGL · 4 kt GS
Long landing rollout 18:56:14 UTC · PAFA runway 20L · 0 ft AGL · 4 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