Long landing rollout — FDX1249

KMEM · 36R

2026-07-30 03:09 UTC· KRDU → KMEM· FEDERAL EXPRESS CORP· B763

▶ Replay 📊 Analyse

FDX1249 (Federal Express) was operating from KRDU to KMEM on 2026-07-30. SkyMeter detected a long landing rollout at Memphis International Airport (KMEM) on runway 36R at 03:09 UTC. Trace data at the event: 255 ft AGL, 15 kt GS, 0 fpm vertical. Approach stability score: 84/100. Scores in this band are observed on roughly 25% of approaches at this runway: one or more gates outside the per-runway tightest envelope, but still inside the typical operating range. METAR at the time reported 7 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)
  • SECURITY6/8903 2026-07-29 22:30Z – 2026-07-30 02:30Z SFC–400 ft

    Charlotte, NC, Wednesday, July 29, 2026 through Wednesday, July 29, 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 36R
  • 255 ft AGL at event
  • 15 kt ground speed
  • 0 fpm vertical
  • Approach stability 84/100
  • 7 kt wind
  • 4 kt crosswind component
  • 16,093 m visibility
  • KMEM 050754Z 03008KT 10SM FEW250 18/10 A3013 RMK AO2 SLP199 T01830100 $

Flight context

  • FDX1249
  • Federal Express
  • B763
  • KRDU → KMEM
  • 2026-07-30 03:09 UTC
  • KMEM runway 36R

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· KMEM