Unstable approach — AAL2531

KMCO · 18L

2026-06-04 00:16 UTC· KPHL → KMCO· US BANK NA TRUSTEE· A319

AAL2531 (US Bank NA) was operating from KPHL to KMCO on 2026-06-04. SkyMeter detected a low approach-stability score at Orlando International Airport (KMCO) on runway 18L at 00:16 UTC. Trace data at the event: 1197 ft AGL, 131 kt GS. METAR at the time reported 9 kt wind, 7 kt crosswind component, 16,093 m visibility. The approach-stability score rates the final approach against stabilized-approach gates (glideslope, lateral deviation, descent rate, and IAS) at defined altitudes. A low score means one or more of those were outside the normal envelope for how the approach was flown. The score is graded by guidance type, so instrument approaches (ILS or an aligned straight-in) are held to the full gate set, while visual and pattern arrivals are surfaced only when the score is clearly low. The score is advisory and observational, a deviation measure, not an assertion of an accident. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • 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/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/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/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/4380 2026-06-01 13:00Z – 2026-06-06 06:00Z SFC–2,500 ft

    MAYPORT, FL, Monday, June 1, 2026 through Saturday, June 6, 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

  • Runway 18L
  • 1197 ft AGL at event
  • 131 kt ground speed
  • 0 fpm vertical
  • 9 kt wind
  • 7 kt crosswind component
  • 16,093 m visibility
  • KMCO 151753Z 10006KT 10SM SCT043 32/21 A3007

Flight context

  • AAL2531
  • US Bank NA
  • A319
  • KPHL → KMCO
  • 2026-06-04 00:16 UTC
  • KMCO runway 18L

All events on this flight

Unstable approach 00:16:38 UTC · KMCO runway 18L · 1,197 ft AGL · 131 kt GS
Unstable approach 00:16:38 UTC · KMCO runway 18L · 1,197 ft AGL · 131 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· KMCO