Go-around — AAL2167

KRDU · 32

2026-08-20 00:48 UTC· KORD → KRDU· U S BANK NA TRUSTEE· A319

▶ Replay 📊 Analyse

AAL2167 (U S Bank NA) was operating from KORD to KRDU on 2026-08-20. SkyMeter detected a go-around at Raleigh Durham International Airport (KRDU) on runway 32 at 00:48 UTC. Trace data at the event: 1416 ft AGL, 154 kt GS. METAR at the time reported 3 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)
  • SECURITY6/0708 2026-08-01 00:01Z – 2027-08-01 23:59Z SFC–400 ft

    Goodlettsville, TN, Saturday, August 1, 2026 through Sunday, August 1, 2027 UTC

    View FAA NOTAM →
  • UAS PUBLIC GATHERING6/3173 2026-08-13 21:00Z – 2026-08-23 07:00Z SFC–400 ft

    Lebanon, TN, Thursday, August 13, 2026 through Sunday, August 23, 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.

Pilot review data

  • Runway 32
  • 1416 ft AGL at event
  • 154 kt ground speed
  • 0 fpm vertical
  • 3 kt wind
  • 1 kt crosswind component
  • 16,093 m visibility
  • KRDU 162051Z 08006KT 10SM FEW050 FEW250 30/16 A3032 RMK AO2 SLP262 T03000156 56016

Flight context

  • AAL2167
  • U S Bank NA
  • A319
  • KORD → KRDU
  • 2026-08-20 00:48 UTC
  • KRDU runway 32

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