Unstable approach — N595DC

KTYS · 23R

2026-08-29 16:27 UTC· KSAT KTYS· CHOICE AVIATION LLC· C650

N595DC (Choice Aviation) was operating from KSAT to KTYS on 2026-08-29. SkyMeter detected a low approach-stability score at McGhee Tyson Airport (KTYS) on runway 23R at 16:27 UTC. Trace data at the event: 2084 ft AGL, 163 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 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.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • HAZARDS6/7630 2026-08-25 12:00Z – 2026-09-01 02:00Z SFC–5,500 ft

    1NM W PALO PINTO, TX, Tuesday, August 25, 2026 through Tuesday, September 1, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/7885 2026-08-25 19:02Z – 2026-09-02 23:45Z SFC–5,500 ft

    PALO PINTO, TX, Tuesday, August 25, 2026 through Wednesday, September 2, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/8092 2026-08-26 00:25Z – 2026-09-09 23:45Z SFC–6,200 ft

    1NM NE EVANT, TX, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/8102 2026-08-26 02:25Z – 2026-09-09 02:00Z SFC–5,500 ft

    1NM NW PALO PINTO, TX, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/8103 2026-08-26 12:00Z – 2026-09-09 02:00Z SFC–4,000 ft

    21NM NW BROKEN BOW, OK, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/8445 2026-08-26 20:55Z – 2026-09-09 02:00Z SFC–5,500 ft

    1NM NW PALO PINTO, TX, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/8453 2026-08-26 21:02Z – 2026-09-08 00:45Z SFC–6,200 ft

    1NM NE EVANT, TX, Wednesday, August 26, 2026 through Tuesday, September 8, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/8829 2026-08-28 15:45Z – 2026-09-11 02:00Z SFC–5,500 ft

    4NM NW MINERAL WELLS, TX, Friday, August 28, 2026 through Friday, September 11, 2026 UTC

    View FAA NOTAM →
  • AIR SHOWS/SPORTS6/7028 2026-08-28 18:00Z – 2026-08-30 22:00Z SFC–15,000 ft

    Lake Charles, LA, Friday, August 28, 2026 through Sunday, August 30, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/9129 2026-08-29 15:15Z – 2026-09-12 02:00Z SFC–5,500 ft

    4NM NW MINERAL WELLS, TX, Saturday, August 29, 2026 through Saturday, September 12, 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.

Pilot review data

  • Runway 23R
  • 2084 ft AGL at event
  • 163 kt ground speed
  • 0 fpm vertical
  • Approach stability 42/100
  • 2 kt wind
  • 1 kt crosswind component
  • 16,093 m visibility
  • KTYS 112253Z 08004KT 10SM FEW070 BKN250 32/18 A2990 RMK AO2 SLP112 T03170183

Flight context

  • N595DC
  • Choice Aviation
  • C650
  • KSAT → KTYS
  • 2026-08-29 16:27 UTC
  • KTYS runway 23R

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

SkyMeter · trace data observed via ADS-B· KTYS