Go-around — AAL1050
KCLT · 18L2026-02-19 14:35 UTC· KALB → KCLT· UMB BANK NA TRUSTEE· A319
AAL1050 (UMB Bank NA) was operating from KALB to KCLT on 2026-02-19. SkyMeter detected a go-around at Charlotte Douglas International Airport (KCLT) on runway 18L at 14:35 UTC. Trace data at the event: 1639 ft AGL, 132 kt GS. Approach stability score: 85/100. Scores in this band are observed on roughly 25% of approaches at this runway: one or more gates outside the per-runway tightest envelope, but still inside the typical operating range. METAR at the time reported 10 kt wind, 8 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/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 18L
- 1639 ft AGL at event
- 132 kt ground speed
- 0 fpm vertical
- Approach stability 85/100
- 10 kt wind
- 8 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
- AAL1050
- UMB Bank NA
- A319
- KALB → KCLT
- 2026-02-19 14:35 UTC
- KCLT runway 18L
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