Go-around — AAY1401
KTYS · 05L2026-06-15 15:46 UTC· KEWR → KTYS· BANK OF UTAH TRUSTEE· A320
AAY1401 (Bank of Utah) was operating from KEWR to KTYS on 2026-06-15. SkyMeter detected a go-around at McGhee Tyson Airport (KTYS) on runway 05L at 15:46 UTC. Trace data at the event: 2448 ft AGL, 170 kt GS. METAR at the time reported 5 kt wind, 5 kt crosswind component, 16,093 m visibility. A go-around is a discontinued landing approach in which the pilot adds power and climbs back to a safe altitude before re-attempting the approach or proceeding to an alternate. It is a routine safety response, not an emergency, and is taught as the standard reaction to any unstable approach. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY6/3956 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Atlantic City, NJ, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3961 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Chester, PA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3965 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Galloway, NJ, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3967 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
PHILADELPHIA, PA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3968 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Winston Salem, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3970 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
White Sulphur Springs, WV, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3971 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Winston Salem, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3973 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
WILMINGTON, DE, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4001 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
GREENSBORO, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4005 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Greensboro, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4106 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
New Brunswick, NJ, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4115 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
BASKING RIDGE, NJ, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4117 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Warren, NJ, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/6442 2026-06-10 04:01Z – 2026-07-20 03:59Z SFC–1,000 ft
Philadelphia, PA, Wednesday, June 10, 2026 through Sunday, July 19, 2026 Local
View FAA NOTAM → - SECURITY6/6851 2026-06-13 04:01Z – 2026-07-12 03:59Z SFC–1,000 ft
Harrison, NJ, Saturday, June 13, 2026 through Saturday, July 11, 2026 Local
View FAA NOTAM → - SECURITY6/7801 2026-06-15 04:00Z – 2026-07-07 03:29Z SFC–400 ft
Whippany, NJ, Monday, June 15, 2026 through Monday, July 6, 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 05L
- 2448 ft AGL at event
- 170 kt ground speed
- 0 fpm vertical
- 5 kt wind
- 5 kt crosswind component
- 16,093 m visibility
- KTYS 180753Z 00000KT 10SM CLR 23/21 A3019 RMK AO2 SLP209 T02280206
Flight context
- AAY1401
- Bank of Utah
- A320
- KEWR → KTYS
- 2026-06-15 15:46 UTC
- KTYS runway 05L
All events on this flight
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