Unstable approach — AAL2396

AAL2396 (American Airlines) was operating from KLAX to KRDU on 2026-07-30. SkyMeter detected a low approach-stability score at Raleigh Durham International Airport (KRDU) on runway 14 at 02:10 UTC. Trace data at the event: 1540 ft AGL, 159 kt GS. METAR at the time reported 3 kt wind, 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.

• HAZARDS6/6360 2026-07-17 04:00Z – 2026-07-30 04:00Z SFC–15,000 ft

  9NM SW PUEBLO, CO, Friday, July 17, 2026 through Thursday, July 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6395 2026-07-17 12:00Z – 2026-07-30 04:00Z SFC–13,000 ft

  14NM N CORTEZ, CO, Friday, July 17, 2026 through Thursday, July 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6567 2026-07-18 13:00Z – 2026-08-01 04:00Z SFC–16,000 ft

  16NM W MONTICELLO, UT, Saturday, July 18, 2026 through Saturday, August 1, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6736 2026-07-19 12:00Z – 2026-08-01 03:00Z SFC–16,000 ft

  16NM W MONTICELLO, UT, Sunday, July 19, 2026 through Saturday, August 1, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6876 2026-07-20 13:00Z – 2026-08-03 04:00Z SFC–16,000 ft

  7NM SW DEL NORTE, CO, Monday, July 20, 2026 through Monday, August 3, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7246 2026-07-21 05:00Z – 2026-08-21 03:00Z SFC–10,500 ft

  20NM N INDEPENDENCE, CA, Tuesday, July 21, 2026 through Friday, August 21, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7372 2026-07-21 13:38Z – 2026-08-22 03:00Z SFC–10,500 ft

  20NM N INDEPENDENCE, CA, Tuesday, July 21, 2026 through Saturday, August 22, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7909 2026-07-22 18:11Z – 2026-08-08 04:00Z SFC–12,500 ft

  20NM N INDEPENDENCE, CA, Wednesday, July 22, 2026 through Saturday, August 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8008 2026-07-23 12:00Z – 2026-08-01 03:00Z SFC–12,000 ft

  16NM W MONTICELLO, UT, Thursday, July 23, 2026 through Saturday, August 1, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8554 2026-07-26 12:00Z – 2026-08-10 03:00Z SFC–12,000 ft

  16NM W MONTICELLO, UT, Sunday, July 26, 2026 through Monday, August 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9111 2026-07-28 14:00Z – 2026-08-10 03:00Z SFC–14,500 ft

  14NM N LOS ALAMOS, NM, Tuesday, July 28, 2026 through Monday, August 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9567 2026-07-28 16:27Z – 2026-08-02 04:00Z SFC–8,500 ft

  YUCAIPA, CA, Tuesday, July 28, 2026 through Sunday, August 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9853 2026-07-29 00:30Z – 2026-08-01 04:00Z SFC–15,000 ft

  8NM S PAGOSA SPRINGS, CO, Wednesday, July 29, 2026 through Saturday, August 1, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9881 2026-07-29 02:10Z – 2026-08-12 04:00Z SFC–13,500 ft

  25NM S BISHOP, CA, Wednesday, July 29, 2026 through Wednesday, August 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9885 2026-07-29 12:00Z – 2026-08-12 04:00Z SFC–15,000 ft

  8NM S PAGOSA SPRINGS, CO, Wednesday, July 29, 2026 through Wednesday, August 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9841 2026-07-29 14:00Z – 2026-08-11 03:00Z SFC–11,500 ft

  11NM S CIMARRON, NM, Wednesday, July 29, 2026 through Tuesday, August 11, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0151 2026-07-29 19:34Z – 2026-07-29 22:00Z SFC–2,000 ft

  CONYERS, GA, Wednesday, July 29, 2026 UTC

  View FAA NOTAM →
• SECURITY6/8903 2026-07-29 22:30Z – 2026-07-30 02:30Z SFC–400 ft

  Charlotte, NC, Wednesday, July 29, 2026 through Wednesday, July 29, 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.

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