EmergencyDescent — DAL2131
2026-07-07 21:46 UTC· KPHL → KATL· BANK OF UTAH TRUSTEE· A321
DAL2131 (Bank of Utah) was operating from KPHL to KATL on 2026-07-07. SkyMeter detected a emergencydescent at 21:46 UTC. Trace data at the event: 32860 ft AGL, 415 kt GS. Approach stability score: 93/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/3961 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Chester, PA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3968 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Winston Salem, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3970 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
White Sulphur Springs, WV, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3971 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Winston Salem, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3973 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
WILMINGTON, DE, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3979 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
ATLANTA, GA, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC
View FAA NOTAM → - SECURITY6/3998 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Atlanta, GA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4001 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
GREENSBORO, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4004 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
CHARLOTTE, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4005 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Greensboro, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4007 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Charlotte, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4131 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
MYRTLE BEACH, SC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4132 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Conway, SC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/7169 2026-06-29 15:07Z – 2026-07-21 03:59Z SFC–400 ft
White Sulphur Springs, WV
View FAA NOTAM → - HAZARDS6/3232 2026-07-06 21:53Z – 2026-07-07 23:45Z SFC–1,000 ft
PARKERSBURG, WV, Monday, July 6, 2026 through Tuesday, July 7, 2026 UTC
View FAA NOTAM → - SECURITY6/2396 2026-07-07 13:00Z – 2026-07-08 01:00Z SFC–3,000 ft
Atlanta, GA, Tuesday, July 7, 2026 through Tuesday, July 7, 2026 Local
View FAA NOTAM → - VIP6/3354 2026-07-07 14:00Z – 2026-07-08 17:00Z SFC–4,999 ft
Middleburg, VA, Tuesday, July 7, 2026 through Wednesday, July 8, 2026 Local
View FAA NOTAM → - HAZARDS6/3460 2026-07-07 14:25Z – 2026-07-09 03:59Z SFC–1,000 ft
PARKERSBURG, WV, Tuesday, July 7, 2026 through Thursday, July 9, 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
- 32860 ft AGL at event
- 415 kt ground speed
- 0 fpm vertical
- Approach stability 93/100
- 5 kt wind
- 5 kt crosswind component
Flight context
- DAL2131
- Bank of Utah
- A321
- KPHL → KATL
- 2026-07-07 21:46 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