Long landing rollout — ASA66
PACV · 092026-08-07 22:05 UTC· PANC → PACV· ALASKA AIRLINES INC· B737
ASA66 (Alaska Airlines) was operating from PANC to PACV on 2026-08-07. SkyMeter detected a long landing rollout at Merle K (Mudhole) Smith Airport (PACV) on runway 09 at 22:05 UTC. Trace data at the event: 0 ft AGL, 8 kt GS, 0 fpm vertical. METAR at the time reported 6 kt wind, 4 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)- AIR SHOWS/SPORTS6/0705 2026-08-06 20:00Z – 2026-08-10 00:30Z SFC–15,000 ft
ANCHORAGE, AK, Thursday, August 6, 2026 through Sunday, August 9, 2026 Local
View FAA NOTAM → - AIR SHOWS/SPORTS6/1712 2026-08-06 20:00Z – 2026-08-10 00:30Z SFC–15,000 ft
ANCHORAGE, AK, Thursday, August 6, 2026 through Sunday, August 9, 2026 Local
View FAA NOTAM → - AIR SHOWS/SPORTS6/1748 2026-08-07 19:30Z – 2026-08-09 21:00Z SFC–15,000 ft
ANCHORAGE, AK, Friday, August 7, 2026 through Sunday, August 9, 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 09
- 0 ft AGL at event
- 8 kt ground speed
- 0 fpm vertical
- 6 kt wind
- 4 kt crosswind component
- 16,093 m visibility
- PACV 162053Z 08003KT 10SM FEW027 OVC034 13/08 A3000 RMK AO2 SLP159 BINOVC T01280078 51018
Flight context
- ASA66
- Alaska Airlines
- B737
- PANC → PACV
- 2026-08-07 22:05 UTC
- PACV runway 09
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