Long landing rollout — N695AK
PAFA · 20L2026-08-17 17:01 UTC· PANC → PAFA· ALASCOM INC· C560
N695AK (Alascom) was operating from PANC to PAFA on 2026-08-17. SkyMeter detected a long landing rollout at Fairbanks International Airport (PAFA) on runway 20L at 17:01 UTC. Trace data at the event: 0 ft AGL, 4 kt GS, 0 fpm vertical. METAR at the time reported 12 kt wind, 1 kt crosswind component, 9,656 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 → - SECURITY6/2117 2026-07-01 00:01Z – 2026-11-01 10:00Z SFC–430 ft
Clear, AK, Tuesday, June 30, 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
- 12 kt wind
- 1 kt crosswind component
- 9,656 m visibility
- PAFA 161053Z 00000KT 6SM -RA BR SCT019 BKN045 OVC060 08/08 A2965 RMK AO2 SLP044 P0005 T00830083 $
Flight context
- N695AK
- Alascom
- C560
- PANC → PAFA
- 2026-08-17 17:01 UTC
- PAFA runway 20L
All events on this flight
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