Unstable approach — SWA2091

SWA2091 (Southwest Airlines) was inbound to KMCO on 2026-06-13. SkyMeter detected a low approach-stability score at Orlando International Airport (KMCO) on runway 36R at 02:09 UTC. Trace data at the event: 1193 ft AGL, 126 kt GS. Approach stability score: 45/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, 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.

• 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/4153 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  Tampa, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  TAMPA, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  HOUSTON, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  HOUSTON, TX, 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/5787 2026-06-08 13:00Z – 2026-06-13 06:00Z SFC–2,500 ft

  MAYPORT, FL, Monday, June 8, 2026 through Saturday, June 13, 2026 Local

  View FAA NOTAM →
• SECURITY6/6447 2026-06-09 05:01Z – 2026-07-20 04:59Z SFC–1,000 ft

  Houston, TX, Tuesday, June 9, 2026 through Sunday, July 19, 2026 Local

  View FAA NOTAM →
• SECURITY6/6446 2026-06-11 04:01Z – 2026-06-14 03:59Z SFC–1,000 ft

  Atlanta, GA, Thursday, June 11, 2026 through Saturday, June 13, 2026 Local

  View FAA NOTAM →
• SECURITY6/6582 2026-06-11 05:00Z – 2026-06-13 09:30Z SFC–17,999 ft

  Macon, GA, Thursday, June 11, 2026 through Saturday, June 13, 2026 Local

  View FAA NOTAM →
• UAS PUBLIC GATHERING6/5785 2026-06-11 18:00Z – 2026-06-15 04:00Z SFC–400 ft

  Manchester, TN, Thursday, June 11, 2026 through Monday, June 15, 2026 UTC

  View FAA NOTAM →
• AIR SHOWS/SPORTS6/6635 2026-06-12 23:30Z – 2026-06-14 01:50Z SFC–5,500 ft

  SUNSET, LA, Friday, June 12, 2026 through Sunday, June 14, 2026 UTC

  View FAA NOTAM →
• AIR SHOWS/SPORTS6/6636 2026-06-12 23:30Z – 2026-06-14 01:50Z SFC–5,500 ft

  Sunset, LA, Friday, June 12, 2026 through Sunday, June 14, 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.

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