KING98 was inbound to PAED on 2026-08-09. SkyMeter detected a long landing rollout at Elmendorf Air Force Base (PAED) on runway 24 at 19:05 UTC. Trace data at the event: 0 ft AGL, 0 kt GS, 0 fpm vertical. Approach stability score: 50/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 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)- 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 24
- 0 ft AGL at event
- 0 kt ground speed
- 0 fpm vertical
- Approach stability 50/100
- 3 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- PAED 151355Z COR 06003KT 10SM SCT030 SCT130 BKN160 14/11 A3004 RMK AO2A SLP168 T01350110 $ COR 1358
Flight context
- KING98
- C30J
- 2026-08-09 19:05 UTC
- PAED runway 24
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