Long landing rollout — RCH171

PAED · 24

2026-07-29 00:50 UTC· KSUU PAED· C17

RCH171 was operating from KSUU to PAED on 2026-07-29. SkyMeter detected a long landing rollout at Elmendorf Air Force Base (PAED) on runway 24 at 00:50 UTC. Trace data at the event: 0 ft AGL, 4 kt GS, 0 fpm vertical. METAR at the time reported 11 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)
  • HAZARDS6/6363 2026-07-17 01:54Z – 2026-07-31 04:00Z SFC–8,000 ft

    20NM NW MEDFORD, OR, Friday, July 17, 2026 through Friday, July 31, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/6409 2026-07-17 04:39Z – 2026-07-30 07:00Z SFC–11,000 ft

    10NM SW MOUNT SHASTA, CA, Friday, July 17, 2026 through Thursday, July 30, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/6741 2026-07-19 12:00Z – 2026-08-02 04:00Z SFC–6,500 ft

    7NM NE REDDING, CA, Sunday, July 19, 2026 through Sunday, August 2, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/7914 2026-07-22 18:44Z – 2026-08-05 04:00Z SFC–7,000 ft

    20NM NW MEDFORD, OR, Wednesday, July 22, 2026 through Wednesday, August 5, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/8326 2026-07-24 00:00Z – 2026-08-05 05:00Z SFC–10,000 ft

    35NM E ROSEBURG, OR, Friday, July 24, 2026 through Wednesday, August 5, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/8423 2026-07-24 16:00Z – 2026-08-07 04:00Z SFC–9,500 ft

    35NM SE ROSEBURG, OR, Friday, July 24, 2026 through Friday, August 7, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/9403 2026-07-28 13:00Z – 2026-08-10 03:00Z SFC–7,000 ft

    20NM NW MEDFORD, OR, Tuesday, July 28, 2026 through Monday, August 10, 2026 UTC

    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
  • 4 kt ground speed
  • 0 fpm vertical
  • 11 kt wind
  • 2 kt crosswind component
  • 16,093 m visibility
  • PAED 161155Z 19018G25KT 10SM FEW034 11/04 A2980 RMK AO2A PK WND 20036/15 SLP088 60000 70070 T01130043 10135 20111 52012 $

Flight context

  • RCH171
  • C17
  • KSUU → PAED
  • 2026-07-29 00:50 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

SkyMeter · trace data observed via ADS-B· PAED