Unstable approach — AAL125

AAL125 (Wilmington Trust) was operating from LEMD to KORD on 2026-07-01. SkyMeter detected a low approach-stability score at Chicago O'Hare International Airport (KORD) on runway 14L at 20:57 UTC. Trace data at the event: 1785 ft AGL, 144 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 15 kt wind, 15 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.

• SECURITY5/2811 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–1,000 ft

  NEW YORK, NY, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local

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

  Smithfield, RI, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Boston, MA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  FOXBOROUGH, MA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Waltham, MA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  BASKING RIDGE, NJ, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Warren, NJ, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Providence, RI, Monday, June 1, 2026 through Tuesday, July 21, 2026 Local

  View FAA NOTAM →
• SECURITY6/6851 2026-06-13 04:01Z – 2026-07-12 03:59Z SFC–1,000 ft

  Harrison, NJ, Saturday, June 13, 2026 through Saturday, July 11, 2026 Local

  View FAA NOTAM →
• SECURITY6/7801 2026-06-15 04:00Z – 2026-07-07 03:29Z SFC–400 ft

  Whippany, NJ, Monday, June 15, 2026 through Monday, July 6, 2026 Local

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

  Jersey City, NJ, Sunday, June 21, 2026 through Wednesday, July 1, 2026 Local

  View FAA NOTAM →
• SECURITY6/9462 2026-06-24 04:00Z – 2026-07-21 03:29Z SFC–400 ft

  Montclair, NJ, Wednesday, June 24, 2026 through Monday, July 20, 2026 Local

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

  New York, NY, Friday, June 26, 2026 through Friday, July 3, 2026 Local

  View FAA NOTAM →
• SECURITY6/9464 2026-06-28 04:00Z – 2026-07-02 03:29Z SFC–400 ft

  Parsippany-Troy Hills, NJ, Sunday, June 28, 2026 through Wednesday, July 1, 2026 Local

  View FAA NOTAM →
• SECURITY6/1081 2026-07-01 12:00Z – 2026-07-09 16:00Z SFC–2,000 ft

  New York, NY, Wednesday, July 1, 2026 through Thursday, July 9, 2026 Local

  View FAA NOTAM →
• SECURITY6/1240 2026-07-01 12:00Z – 2026-07-09 16:00Z SFC–2,000 ft

  New York, NY, Wednesday, July 1, 2026 through Thursday, July 9, 2026 Local

  View FAA NOTAM →
• AIR SHOWS/SPORTS6/1384 2026-07-01 13:30Z – 2026-07-05 22:00Z SFC–16,000 ft

  battle Creek, MI, Wednesday, July 1, 2026 through Sunday, July 5, 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.

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