Unstable approach — UAL1382

KORL · 07

2026-06-16 01:35 UTC· UNITED AIRLINES INC· A21N

UAL1382 (United Airlines) was inbound to KORL on 2026-06-16. SkyMeter detected a low approach-stability score at Orlando Executive Airport (KORL) on runway 07 at 01:35 UTC. Trace data at the event: 1201 ft AGL, 148 kt GS. Approach stability score: 37/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 6 kt wind, 1 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/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/3980 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    CHATTANOOGA, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/3990 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    CHATTANOOGA, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/3991 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    MARIETTA, GA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4114 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    LOUISVILLE, KY, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4116 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    LOUISVILLE, KY, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4121 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

    Nashville, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • HAZARDS6/5656 2026-06-04 16:19Z – 2026-06-18 00:15Z SFC–2,000 ft

    22NM SW TALLAHASSEE, FL, Thursday, June 4, 2026 through Thursday, June 18, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/5771 2026-06-04 21:47Z – 2026-06-18 00:15Z SFC–3,500 ft

    22NM SW TALLAHASSEE, FL, Thursday, June 4, 2026 through Thursday, June 18, 2026 UTC

    View FAA NOTAM →
  • SECURITY6/7933 2026-06-15 13:00Z – 2026-06-16 01:00Z SFC–3,000 ft

    Atlanta, GA, Monday, June 15, 2026 through Monday, June 15, 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 07
  • 1201 ft AGL at event
  • 148 kt ground speed
  • 0 fpm vertical
  • Approach stability 37/100
  • 6 kt wind
  • 1 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

  • UAL1382
  • United Airlines
  • A21N
  • 2026-06-16 01:35 UTC
  • KORL runway 07

All events on this flight

Unstable approach 01:35:36 UTC · KORL runway 07 · 1,201 ft AGL · 148 kt GS
Unstable approach 01:35:36 UTC · KORL runway 07 · 1,201 ft AGL · 148 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· KORL