Go-around — UAL297

UAL297 (United Airlines) was operating from KEWR to KBZN on 2026-09-04. SkyMeter detected a go-around at Gallatin Field (KBZN) on runway 12 at 16:36 UTC. Trace data at the event: 6153 ft AGL, 198 kt GS. METAR at the time reported 8 kt wind, 8 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.

• UAS PUBLIC GATHERING6/6427 2026-08-26 13:00Z – 2026-09-08 03:59Z SFC–400 ft

  Syracuse, NY, Wednesday, August 26, 2026 through Tuesday, September 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8109 2026-08-26 14:00Z – 2026-09-09 03:30Z SFC–11,000 ft

  32NM SE BILLINGS, MT, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC

  View FAA NOTAM →
• SECURITY6/6998 2026-08-27 11:00Z – 2026-09-08 03:00Z SFC–400 ft

  St. Paul, MN, Thursday, August 27, 2026 through Monday, September 7, 2026 Local

  View FAA NOTAM →
• HAZARDS6/8524 2026-08-27 14:00Z – 2026-09-10 03:30Z SFC–12,500 ft

  18NM SE ENNIS, MT, Thursday, August 27, 2026 through Thursday, September 10, 2026 UTC

  View FAA NOTAM →
• UAS PUBLIC GATHERING6/8809 2026-09-03 21:00Z – 2026-09-05 04:30Z SFC–400 ft

  Chicago, IL, Thursday, September 3, 2026 through Saturday, September 5, 2026 UTC

  View FAA NOTAM →
• AIR SHOWS/SPORTS6/8827 2026-09-04 14:00Z – 2026-09-04 21:00Z SFC–16,000 ft

  Cleveland, OH, Friday, September 4, 2026 UTC

  View FAA NOTAM →
• UAS PUBLIC GATHERING6/9767 2026-09-04 14:00Z – 2026-09-08 05:00Z SFC–400 ft

  royal oak, MI, Friday, September 4, 2026 through Tuesday, September 8, 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