Go-around — NKS2183

KCLT · 36L

2026-03-03 16:55 UTC· KMIA KCLT· WELLS FARGO TRUST CO NA TRUSTEE· A320

NKS2183 (Wells Fargo Trust Co NA) was operating from KMIA to KCLT on 2026-03-03. SkyMeter detected a go-around at Charlotte Douglas International Airport (KCLT) on runway 36L at 16:55 UTC. Trace data at the event: 2286 ft AGL, 178 kt GS. METAR at the time reported 2 kt wind, 2 kt crosswind component, 11,265 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/2809 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–2,000 ft

    Palm Beach, FL, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local

    View FAA NOTAM →
  • SECURITY5/2858 2025-12-26 04:59Z – 2026-07-02 03:59Z SFC–1,000 ft

    OCHOPPEE, FL, Thursday, December 25, 2025 through Wednesday, July 1, 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 36L
  • 2286 ft AGL at event
  • 178 kt ground speed
  • 0 fpm vertical
  • 2 kt wind
  • 2 kt crosswind component
  • 11,265 m visibility
  • METAR KCLT 231252Z 05014G21KT 7SM -RA BKN011 OVC017 17/14 A3022 RMK AO2 RAB49 SLP244 P0000 T01670144

Flight context

  • NKS2183
  • Wells Fargo Trust Co NA
  • A320
  • KMIA → KCLT
  • 2026-03-03 16:55 UTC
  • KCLT runway 36L

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