EmergencyDescent — FDX1231
2026-07-17 03:36 UTC· KFAR → KMEM· FEDERAL EXPRESS CORP· B752
FDX1231 (Federal Express) was operating from KFAR to KMEM on 2026-07-17. SkyMeter detected a emergencydescent at 03:36 UTC. Trace data at the event: 34070 ft AGL, 478 kt GS. Approach stability score: 89/100. Scores in this band are observed on roughly 50% of approaches at this runway and represent the centerline of normal operations. METAR at the time reported 5 kt wind, 5 kt crosswind component. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY6/4134 2026-06-01 00:00Z – 2026-07-20 23:59Z
TULSA, OK, Monday, June 1, 2026 through Monday, July 20, 2026 UTC
View FAA NOTAM → - SECURITY6/4135 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
CLAYTON, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4141 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Tulsa, OK, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4146 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Lawrence, KS, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4149 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Lawrence, KS, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4151 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Kansas City, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4154 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Kansas City, KS, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4155 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Riverside, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4157 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
PRAIRIE VILLAGE, KS, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4161 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
St, Louis, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4162 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Kansas City, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4206 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Kansas City, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/7652 2026-07-01 16:07Z – 2026-07-21 04:59Z SFC–400 ft
Riverside, MO
View FAA NOTAM → - SECURITY6/7650 2026-07-01 16:07Z – 2026-07-21 04:59Z SFC–400 ft
Kansas City, MO
View FAA NOTAM → - SECURITY6/7646 2026-07-03 16:07Z – 2026-07-21 04:59Z SFC–400 ft
Lawrence, KS
View FAA NOTAM → - SECURITY6/7647 2026-07-03 16:07Z – 2026-07-21 04:59Z SFC–400 ft
Lawrence, KS
View FAA NOTAM → - SECURITY6/7651 2026-07-09 11:07Z – 2026-07-21 04:59Z SFC–400 ft
Prairie Village, KS
View FAA NOTAM → - SECURITY6/7817 2026-07-09 11:07Z – 2026-07-21 04:59Z SFC–400 ft
St Louis, MO
View FAA NOTAM → - AIR SHOWS/SPORTS6/4377 2026-07-16 18:30Z – 2026-07-17 21:30Z
SIOUX FALLS, SD, Thursday, July 16, 2026 through Friday, July 17, 2026 UTC
View FAA NOTAM → - AIR SHOWS/SPORTS6/4378 2026-07-16 18:30Z – 2026-07-17 21:30Z SFC–16,000 ft
Sioux Falls, SD, Thursday, July 16, 2026 through Friday, July 17, 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
- 34070 ft AGL at event
- 478 kt ground speed
- 0 fpm vertical
- Approach stability 89/100
- 5 kt wind
- 5 kt crosswind component
Flight context
- FDX1231
- Federal Express
- B752
- KFAR → KMEM
- 2026-07-17 03:36 UTC
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