Long landing rollout — AFRQ31

PAED · 24

2026-06-04 07:17 UTC· PAFA PAED· C30J

AFRQ31 was operating from PAFA to PAED on 2026-06-04. SkyMeter detected a long landing rollout at Elmendorf Air Force Base (PAED) on runway 24 at 07:17 UTC. Trace data at the event: 0 ft AGL, 3 kt GS, 0 fpm vertical. METAR at the time reported 2 kt wind, 2 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)
  • 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 24
  • 0 ft AGL at event
  • 3 kt ground speed
  • 0 fpm vertical
  • 2 kt wind
  • 2 kt crosswind component
  • 16,093 m visibility
  • PAED 200155Z 36006KT 10SM SCT018 BKN040 OVC050 10/08 A2938 RMK AO2A SLP946 T01040083 $

Flight context

  • AFRQ31
  • C30J
  • PAFA → PAED
  • 2026-06-04 07:17 UTC
  • PAED runway 24

All events on this flight

Long landing rollout 07:17:52 UTC · PAED runway 24 · 0 ft AGL · 3 kt GS
Long landing rollout 07:17:52 UTC · PAED runway 24 · 0 ft AGL · 3 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· PAED