EmergencyDescent — DAL2694

2026-05-18 13:03 UTC· KLGA KMCO· BANK OF UTAH TRUSTEE· A321

DAL2694 (Bank of Utah) was operating from KLGA to KMCO on 2026-05-18. SkyMeter detected a emergencydescent at 13:03 UTC. Trace data at the event: 36905 ft AGL, 475 kt GS. Approach stability score: 80/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 9 kt wind, 9 kt crosswind component. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • SECURITY5/2811 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–1,000 ft

    NEW YORK, NY, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/9784 2026-05-16 12:00Z – 2026-06-12 22:00Z SFC–400 ft

    Moyock, NC, Saturday, May 16, 2026 through Friday, June 12, 2026 Local

    View FAA NOTAM →
  • SECURITY6/0907 2026-05-18 13:00Z – 2026-05-19 20:00Z SFC–1,000 ft

    Morristown, NJ, Monday, May 18, 2026 through Tuesday, May 19, 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

  • 36905 ft AGL at event
  • 475 kt ground speed
  • 0 fpm vertical
  • Approach stability 80/100
  • 9 kt wind
  • 9 kt crosswind component

Flight context

  • DAL2694
  • Bank of Utah
  • A321
  • KLGA → KMCO
  • 2026-05-18 13:03 UTC

All events on this flight

EmergencyDescent 13:03:30 UTC · · 36,905 ft AGL · 475 kt GS
EmergencyDescent 13:03:30 UTC · · 36,905 ft AGL · 475 kt GS

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