EmergencyDescent — FDX830

2026-07-29 12:45 UTC· KMCO KMEM· FEDERAL EXPRESS CORP· B763

FDX830 (Federal Express) was operating from KMCO to KMEM on 2026-07-29. SkyMeter detected a emergencydescent at 12:45 UTC. Trace data at the event: 36780 ft AGL, 437 kt GS. Approach stability score: 85/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 3 kt wind, 1 kt crosswind component. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • HAZARDS6/8779 2026-07-26 18:03Z – 2026-08-02 01:30Z SFC–1,300 ft

    16NM NE LAKE CITY, FL, Sunday, July 26, 2026 through Sunday, August 2, 2026 UTC

    View FAA NOTAM →
  • SECURITY6/8418 2026-07-27 12:30Z – 2026-08-01 06:00Z SFC–2,500 ft

    MAYPORT, FL, Monday, July 27, 2026 through Saturday, August 1, 2026 Local

    View FAA NOTAM →
  • SECURITY6/9807 2026-07-29 12:00Z – 2026-08-01 23:59Z SFC–400 ft

    Pell City, AL, Wednesday, July 29, 2026 through Saturday, August 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

  • 36780 ft AGL at event
  • 437 kt ground speed
  • 0 fpm vertical
  • Approach stability 85/100
  • 3 kt wind
  • 1 kt crosswind component

Flight context

  • FDX830
  • Federal Express
  • B763
  • KMCO → KMEM
  • 2026-07-29 12:45 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

SkyMeter · trace data observed via ADS-B