Unstable approach — UAE9393

KORD · 36

2026-08-30 06:36 UTC· EBLG KORD· B77L

UAE9393 was operating from EBLG to KORD on 2026-08-30. SkyMeter detected a low approach-stability score at Chicago O'Hare International Airport (KORD) on runway 36 at 06:36 UTC. Trace data at the event: 1790 ft AGL, 148 kt GS. METAR at the time reported 11 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/2790 2026-07-02 22:30Z – 2026-09-15 03:59Z SFC–400 ft

    St. George, ME, Thursday, July 2, 2026 through Monday, September 14, 2026 Local

    View FAA NOTAM →
  • UAS PUBLIC GATHERING6/6427 2026-08-26 13:00Z – 2026-09-08 03:59Z SFC–400 ft

    Syracuse, NY, Wednesday, August 26, 2026 through Tuesday, September 8, 2026 UTC

    View FAA NOTAM →
  • SECURITY6/6997 2026-08-27 15:00Z – 2026-08-31 03:00Z SFC–400 ft

    Plymouth, MI, Thursday, August 27, 2026 through Sunday, August 30, 2026 Local

    View FAA NOTAM →
  • SECURITY6/6995 2026-08-28 10:00Z – 2026-08-30 23:59Z SFC–400 ft

    Grand Blanc, MI, Friday, August 28, 2026 through Sunday, August 30, 2026 Local

    View FAA NOTAM →
  • UAS PUBLIC GATHERING6/7354 2026-08-28 22:00Z – 2026-08-30 03:59Z SFC–400 ft

    Foxborough, MA, Friday, August 28, 2026 through Sunday, August 30, 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

  • Runway 36
  • 1790 ft AGL at event
  • 148 kt ground speed
  • 0 fpm vertical
  • 11 kt wind
  • 2 kt crosswind component
  • 16,093 m visibility
  • KORD 042051Z 20008KT 10SM FEW080 FEW180 SCT250 33/22 A2988 RMK AO2 SLP110 T03330217 58030

Flight context

  • UAE9393
  • B77L
  • EBLG → KORD
  • 2026-08-30 06:36 UTC
  • KORD runway 36

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