Long landing rollout — FDX1366
KMEM · 092026-08-06 05:33 UTC· KSNA → KMEM· FEDERAL EXPRESS CORP· A306
FDX1366 (Federal Express) was operating from KSNA to KMEM on 2026-08-06. SkyMeter detected a long landing rollout at Memphis International Airport (KMEM) on runway 09 at 05:33 UTC. Trace data at the event: 291 ft AGL, 11 kt GS, 0 fpm vertical. METAR at the time reported 3 kt wind, 3 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/0715 2026-08-01 02:12Z – 2026-08-08 04:00Z SFC–7,000 ft
YUCAIPA, CA, Saturday, August 1, 2026 through Saturday, August 8, 2026 UTC
View FAA NOTAM → - HAZARDS6/0876 2026-08-02 14:00Z – 2026-08-09 02:00Z SFC–13,000 ft
30NM NW ALBUQUERQUE, NM, Sunday, August 2, 2026 through Sunday, August 9, 2026 UTC
View FAA NOTAM → - HAZARDS6/2205 2026-08-05 17:05Z – 2026-08-06 03:00Z SFC–16,500 ft
13NM N SANTA FE, NM, Wednesday, August 5, 2026 through Thursday, August 6, 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 09
- 291 ft AGL at event
- 11 kt ground speed
- 0 fpm vertical
- 3 kt wind
- 3 kt crosswind component
- 16,093 m visibility
- METAR KMEM 271954Z 03004KT 10SM FEW100 SCT150 29/05 A2996 RMK AO2 SLP142 T02890050 $
Flight context
- FDX1366
- Federal Express
- A306
- KSNA → KMEM
- 2026-08-06 05:33 UTC
- KMEM 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