Unstable approach — N595P
KTYS · 05L2026-07-16 00:48 UTC· KCGF → KTYS· PILOT 1958 LLC· F2TH
N595P (Pilot 1958) was operating from KCGF to KTYS on 2026-07-16. SkyMeter detected a low approach-stability score at McGhee Tyson Airport (KTYS) on runway 05L at 00:48 UTC. Trace data at the event: 2059 ft AGL, 164 kt GS. METAR at the time reported 3 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)- SECURITY6/7194 2026-07-03 16:07Z – 2026-07-21 03:59Z SFC–400 ft
Columbus, OH
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 05L
- 2059 ft AGL at event
- 164 kt ground speed
- 0 fpm vertical
- 3 kt wind
- 1 kt crosswind component
- 16,093 m visibility
- METAR KTYS 272053Z 34004KT 10SM CLR 24/09 A2992 RMK AO2 SLP124 T02440089 56019
Flight context
- N595P
- Pilot 1958
- F2TH
- KCGF → KTYS
- 2026-07-16 00:48 UTC
- KTYS runway 05L
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