Go-around — AAY1051

KBGR · 33

2026-03-27 22:23 UTC· KPIE → KBGR· ALLEGIANT AIR LLC· A320

▶ Replay 📊 Analyse

AAY1051 (Allegiant AIR) was operating from KPIE to KBGR on 2026-03-27. SkyMeter detected a go-around at Bangor International Airport (KBGR) on runway 33 at 22:23 UTC. Trace data at the event: 527 ft AGL, 122 kt GS. METAR at the time reported 11 kt wind, 1 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)
  • SECURITY5/2811 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–1,000 ft

    NEW YORK, NY, Monday, October 20, 2025 through Tuesday, October 20, 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 33
  • 527 ft AGL at event
  • 122 kt ground speed
  • 0 fpm vertical
  • 11 kt wind
  • 1 kt crosswind component
  • 16,093 m visibility
  • KBGR 211753Z 06005KT 10SM FEW046 BKN065 18/08 A3011 RMK AO2 SLP196 T01780078 10189 20111 56005

Flight context

  • AAY1051
  • Allegiant AIR
  • A320
  • KPIE → KBGR
  • 2026-03-27 22:23 UTC
  • KBGR runway 33

All events on this flight

Go-around 22:23:00 UTC · KBGR runway 33 · 527 ft AGL · 122 kt GS
Go-around 22:23:00 UTC · KBGR runway 33 · 527 ft AGL · 122 kt GS

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· KBGR