Go-around — UAL605

UAL605 (United Airlines) was operating from KDEN to KBNA on 2026-07-15. SkyMeter detected a go-around at Nashville International Airport (KBNA) on runway 20R at 16:30 UTC. Trace data at the event: 947 ft AGL, 156 kt GS. METAR at the time reported 2 kt wind, 2 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.

• 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/4135 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

  CLAYTON, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Lawrence, KS, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Lawrence, KS, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Kansas City, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Kansas City, KS, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Riverside, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  PRAIRIE VILLAGE, KS, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  St, Louis, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Kansas City, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Kansas City, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Nashville, TN

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

  Riverside, MO

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

  Kansas City, MO

  View FAA NOTAM →
• HAZARDS6/2597 2026-07-02 04:41Z – 2026-07-16 04:00Z SFC–15,000 ft

  4NM SW PUEBLO, CO, Thursday, July 2, 2026 through Thursday, July 16, 2026 UTC

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

  Lawrence, KS

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

  Lawrence, KS

  View FAA NOTAM →
• HAZARDS6/3801 2026-07-08 01:49Z – 2026-07-23 04:00Z SFC–15,000 ft

  1NM W PUEBLO, CO, Wednesday, July 8, 2026 through Thursday, July 23, 2026 UTC

  View FAA NOTAM →
• SECURITY6/7651 2026-07-09 11:07Z – 2026-07-21 04:59Z SFC–400 ft

  Prairie Village, KS

  View FAA NOTAM →
• SECURITY6/7817 2026-07-09 11:07Z – 2026-07-21 04:59Z SFC–400 ft

  St Louis, MO

  View FAA NOTAM →
• HAZARDS6/5184 2026-07-15 12:00Z – 2026-07-15 15:00Z SFC–2,000 ft

  ARLINGTON, KS, Wednesday, July 15, 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.

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