Unstable approach — AAL3073

AAL3073 (American Airlines) was operating from AZ42 to KBNA on 2026-07-18. SkyMeter detected a low approach-stability score at Nashville International Airport (KBNA) on runway 13 at 18:52 UTC. Trace data at the event: 1697 ft AGL, 159 kt GS. Approach stability score: 42/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, 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.

• SECURITY6/3954 2026-06-01 00:00Z – 2026-07-20 23:59Z

  STILLWATER, OK, Monday, June 1, 2026 through Monday, July 20, 2026 UTC

  View FAA NOTAM →
• SECURITY6/3996 2026-06-01 00:00Z – 2026-07-20 23:59Z

  OKLAHOMA CITY, OK, Monday, June 1, 2026 through Monday, July 20, 2026 UTC

  View FAA NOTAM →
• SECURITY6/4134 2026-06-01 00:00Z – 2026-07-20 23:59Z

  TULSA, OK, Monday, June 1, 2026 through Monday, July 20, 2026 UTC

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

  Stillwater, OK, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  NORMAN, OK, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

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

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

  OKLAHOMA CITY, OK, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  DENTON, TX, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC

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

  Tulsa, OK, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/3948 2026-06-01 07:00Z – 2026-07-21 06:59Z

  MESA, AZ, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC

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

  Mesa, AZ, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/7079 2026-06-27 01:07Z – 2026-07-21 06:59Z SFC–400 ft

  Mesa, AZ

  View FAA NOTAM →
• SECURITY6/7078 2026-06-27 01:07Z – 2026-07-21 06:59Z SFC–400 ft

  Mesa, AZ

  View FAA NOTAM →
• SECURITY6/6844 2026-07-01 16:07Z – 2026-07-21 04:59Z SFC–400 ft

  Frisco, TX

  View FAA NOTAM →
• HAZARDS6/3016 2026-07-06 14:00Z – 2026-07-20 04:00Z SFC–11,000 ft

  7NM SW FLAGSTAFF, AZ, Monday, July 6, 2026 through Monday, July 20, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3339 2026-07-07 14:00Z – 2026-07-21 04:00Z SFC–11,000 ft

  7NM SW FLAGSTAFF, AZ, Tuesday, July 7, 2026 through Tuesday, July 21, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3341 2026-07-07 14:00Z – 2026-07-21 04:00Z SFC–8,500 ft

  9NM S FLAGSTAFF, AZ, Tuesday, July 7, 2026 through Tuesday, July 21, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3393 2026-07-07 14:00Z – 2026-07-21 04:00Z SFC–11,000 ft

  7NM SW FLAGSTAFF, AZ, Tuesday, July 7, 2026 through Tuesday, July 21, 2026 UTC

  View FAA NOTAM →
• SECURITY6/6784 2026-07-15 13:07Z – 2026-07-21 04:59Z SFC–400 ft

  Denton, TX

  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