Go-around — AAL2478
KCLT · 18L2026-06-13 22:25 UTC· AMERICAN AIRLINES INC· B38M
AAL2478 (American Airlines) was inbound to KCLT on 2026-06-13. SkyMeter detected a go-around at Charlotte Douglas International Airport (KCLT) on runway 18L at 22:25 UTC. Trace data at the event: 1575 ft AGL, 178 kt GS. METAR at the time reported 5 kt wind, 5 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/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 → - SECURITY6/4004 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
CHARLOTTE, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4007 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Charlotte, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4129 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
BOCA RATON, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4130 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
MIAMI, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4131 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
MYRTLE BEACH, SC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4132 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Conway, SC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4133 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
PALM BEACH GARDENS, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4142 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Miami, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4144 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
FORT LAUDERDALE, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4150 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Palm Beach Gardens, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/7122 2026-06-11 13:00Z – 2026-06-13 21:00Z SFC–1,000 ft
Miami, FL, Thursday, June 11, 2026 through Saturday, June 13, 2026 Local
View FAA NOTAM → - SECURITY6/7228 2026-06-13 04:01Z – 2026-07-06 03:59Z SFC–1,000 ft
Miami, FL, Saturday, June 13, 2026 through Sunday, July 5, 2026 Local
View FAA NOTAM → - SPACE OPERATIONS6/7126 2026-06-13 11:54Z – 2026-06-13 16:46Z SFC–180 ft
Cape Canaveral, FL, Saturday, June 13, 2026 Local
View FAA NOTAM → - SPACE OPERATIONS6/7127 2026-06-13 11:54Z – 2026-06-13 16:46Z SFC–180 ft
Cape Canaveral, FL, Saturday, June 13, 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
- 1575 ft AGL at event
- 178 kt ground speed
- 0 fpm vertical
- 5 kt wind
- 5 kt crosswind component
- 16,093 m visibility
- KCLT 131152Z 23003KT 10SM FEW180 OVC250 24/22 A3000 RMK SLP161 T02440222 10244 20228 53020
Flight context
- AAL2478
- American Airlines
- B38M
- 2026-06-13 22:25 UTC
- KCLT runway 18L
All events on this flight
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