Unstable approach — VXP726
KBNA · 312026-08-07 19:40 UTC· KHVN → KBNA· UMB BANK NA TRUSTEE· B738
VXP726 (UMB Bank NA) was operating from KHVN to KBNA on 2026-08-07. SkyMeter detected a low approach-stability score at Nashville International Airport (KBNA) on runway 31 at 19:40 UTC. Trace data at the event: 1693 ft AGL, 179 kt GS. Approach stability score: 41/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 8 kt wind, 7 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.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- 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/0879 2026-08-06 12:00Z – 2026-08-14 20:00Z SFC–2,000 ft
Laurel, MD, Thursday, August 6, 2026 through Friday, August 14, 2026 Local
View FAA NOTAM → - SECURITY6/1710 2026-08-06 21:00Z – 2026-08-10 02:00Z SFC–400 ft
West Chester, OH, Thursday, August 6, 2026 through Sunday, August 9, 2026 Local
View FAA NOTAM → - AIR SHOWS/SPORTS6/0676 2026-08-07 14:00Z – 2026-08-09 22:00Z SFC–16,000 ft
Rochester, NY, Friday, August 7, 2026 through Sunday, August 9, 2026 UTC
View FAA NOTAM → - AIR SHOWS/SPORTS6/0958 2026-08-07 17:00Z – 2026-08-09 20:00Z SFC–5,000 ft
Toughkenamon, PA, Friday, August 7, 2026 through Sunday, August 9, 2026 UTC
View FAA NOTAM → - AIR SHOWS/SPORTS6/0960 2026-08-07 17:00Z – 2026-08-09 20:00Z SFC–5,000 ft
Toughkenamon, PA, Friday, August 7, 2026 through Sunday, August 9, 2026 UTC
View FAA NOTAM → - AIR SHOWS/SPORTS6/1036 2026-08-07 17:00Z – 2026-08-09 20:00Z SFC–5,000 ft
Toughkenamon, PA, Friday, August 7, 2026 through Sunday, August 9, 2026 UTC
View FAA NOTAM → - AIR SHOWS/SPORTS6/1037 2026-08-07 17:00Z – 2026-08-09 20:00Z SFC–5,000 ft
Toughkenamon, PA, Friday, August 7, 2026 through Sunday, August 9, 2026 UTC
View FAA NOTAM → - SECURITY6/2686 2026-08-07 18:00Z – 2026-08-09 03:59Z SFC–400 ft
East Rutherford, NJ, Friday, August 7, 2026 through Saturday, August 8, 2026 Local
View FAA NOTAM → - UAS PUBLIC GATHERING6/2104 2026-08-07 19:30Z – 2026-08-08 00:30Z SFC–400 ft
cincinnati, OH, Friday, August 7, 2026 through Saturday, August 8, 2026 UTC
View FAA NOTAM → - SECURITY6/2198 2026-08-07 19:30Z – 2026-08-07 23:30Z SFC–2,000 ft
Morristown, NJ, Friday, August 7, 2026 Local
View FAA NOTAM → - SECURITY6/2862 2026-08-07 19:30Z – 2026-08-07 22:30Z SFC–2,000 ft
Newark, NJ, Friday, August 7, 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.
Pilot review data
- Runway 31
- 1693 ft AGL at event
- 179 kt ground speed
- 0 fpm vertical
- Approach stability 41/100
- 8 kt wind
- 7 kt crosswind component
- 16,093 m visibility
- KBNA 160425Z AUTO 16005KT 10SM CLR 28/18 A3020 RMK T02800180 MADISHF
Flight context
- VXP726
- UMB Bank NA
- B738
- KHVN → KBNA
- 2026-08-07 19:40 UTC
- KBNA runway 31
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