Unstable approach — AAL2139

KORL · 25

2026-07-08 23:34 UTC· KDCA → KORL· WILMINGTON TRUST CO TRUSTEE· B738

AAL2139 (Wilmington Trust) was operating from KDCA to KORL on 2026-07-08. SkyMeter detected a low approach-stability score at Orlando Executive Airport (KORL) on runway 25 at 23:34 UTC. Trace data at the event: 1207 ft AGL, 174 kt GS. Approach stability score: 43/100. Scores below 50 occur on under 10% of approaches at this runway and indicate the v2 scorer flagged the approach as highly anomalous (three or more gates exceeded the runway's P90 envelope simultaneously). METAR at the time reported 5 kt wind, 2 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/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/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/7169 2026-06-29 15:07Z – 2026-07-21 03:59Z SFC–400 ft

    White Sulphur Springs, WV

    View FAA NOTAM →
  • SECURITY6/2665 2026-07-07 12:30Z – 2026-07-11 06:00Z SFC–2,500 ft

    MAYPORT, FL, Tuesday, July 7, 2026 through Saturday, July 11, 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 25
  • 1207 ft AGL at event
  • 174 kt ground speed
  • 0 fpm vertical
  • Approach stability 43/100
  • 5 kt wind
  • 2 kt crosswind component
  • 16,093 m visibility
  • METAR KORL 302353Z 15010G16KT 10SM CLR 26/22 A3004 RMK AO2 SLP174 60000 T02560217 10306 20250 51012

Flight context

  • AAL2139
  • Wilmington Trust
  • B738
  • KDCA → KORL
  • 2026-07-08 23:34 UTC
  • KORL runway 25

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· KORL