EmergencyDescent — AAL1069
2026-06-18 01:59 UTC· UMB BANK NA TRUSTEE· A319
AAL1069 (UMB Bank NA) was inbound to KMIA on 2026-06-18. SkyMeter detected a emergencydescent at 01:59 UTC. Trace data at the event: 28028 ft AGL, 449 kt GS. Approach stability score: 91/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 7 kt wind, 3 kt crosswind component. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY5/2809 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–2,000 ft
Palm Beach, FL, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local
View FAA NOTAM → - SECURITY5/2858 2025-12-26 04:59Z – 2026-07-02 03:59Z SFC–1,000 ft
OCHOPPEE, FL, Thursday, December 25, 2025 through Wednesday, July 1, 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/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/4129 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
BOCA RATON, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4130 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
MIAMI, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4133 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
PALM BEACH GARDENS, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4142 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Miami, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4144 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
FORT LAUDERDALE, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4150 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Palm Beach Gardens, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/7228 2026-06-13 04:01Z – 2026-07-06 03:59Z SFC–1,000 ft
Miami, FL, Saturday, June 13, 2026 through Sunday, July 5, 2026 Local
View FAA NOTAM → - HAZARDS6/8803 2026-06-17 13:00Z – 2026-06-22 01:00Z SFC–500 ft
7NM W MIAMI, FL, Wednesday, June 17, 2026 through Monday, June 22, 2026 UTC
View FAA NOTAM → - HAZARDS6/9110 2026-06-17 22:24Z – 2026-06-25 04:00Z SFC–500 ft
6NM W MIAMI, FL, Wednesday, June 17, 2026 through Thursday, June 25, 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
- 28028 ft AGL at event
- 449 kt ground speed
- 0 fpm vertical
- Approach stability 91/100
- 7 kt wind
- 3 kt crosswind component
Flight context
- AAL1069
- UMB Bank NA
- A319
- 2026-06-18 01:59 UTC
All events on this flight
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