Unstable approach — SWA4698

SWA4698 (Southwest Airlines) was operating from KLAS to KBNA on 2026-07-02. SkyMeter detected a low approach-stability score at Nashville International Airport (KBNA) on runway 31 at 05:47 UTC. Trace data at the event: 1698 ft AGL, 154 kt GS. Approach stability score: 43/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 2 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/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/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/4119 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

  NASHVILLE, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Nashville, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  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 →
• HAZARDS6/9356 2026-06-20 13:00Z – 2026-07-03 04:00Z SFC–11,000 ft

  46 NM NW MESQUITE, NV, Saturday, June 20, 2026 through Friday, July 3, 2026 UTC

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

  39 NM NW MESQUITE, NV, Saturday, June 20, 2026 through Friday, July 3, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9457 2026-06-21 13:00Z – 2026-07-04 04:00Z SFC–12,000 ft

  39 NM NW MESQUITE, NV, Sunday, June 21, 2026 through Saturday, July 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9458 2026-06-21 13:00Z – 2026-07-04 04:00Z SFC–12,000 ft

  37NM NW MESQUITE, NV, Sunday, June 21, 2026 through Saturday, July 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0608 2026-06-25 13:00Z – 2026-07-09 03:00Z SFC–14,000 ft

  15NM W LOS ALAMOS, NM, Thursday, June 25, 2026 through Thursday, July 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1156 2026-06-28 14:00Z – 2026-07-12 03:00Z SFC–12,500 ft

  32NM NW TAOS, NM, Sunday, June 28, 2026 through Sunday, July 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1169 2026-06-28 14:00Z – 2026-07-12 03:00Z SFC–12,500 ft

  32NM NW TAOS, NM, Sunday, June 28, 2026 through Sunday, July 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1324 2026-06-29 12:00Z – 2026-07-13 05:00Z SFC–13,000 ft

  18NM N CORTEZ, CO, Monday, June 29, 2026 through Monday, July 13, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1584 2026-06-29 18:38Z – 2026-07-13 04:00Z SFC–12,500 ft

  32NM NW TAOS, NM, Monday, June 29, 2026 through Monday, July 13, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1594 2026-06-29 18:49Z – 2026-07-13 03:00Z SFC–12,500 ft

  32NM NW TAOS, NM, Monday, June 29, 2026 through Monday, July 13, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2312 2026-07-01 04:00Z – 2026-07-15 04:00Z SFC–14,000 ft

  20NM W WALSENBURG, CO, Wednesday, July 1, 2026 through Wednesday, July 15, 2026 UTC

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

  Nashville, TN

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

  Nashville, TN

  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