Go-around — AAL2963
KMCO · 36L2026-01-31 22:14 UTC· KMIA → KMCO· AMERICAN AIRLINES INC· B738
AAL2963 (American Airlines) was operating from KMIA to KMCO on 2026-01-31. SkyMeter detected a go-around at Orlando International Airport (KMCO) on runway 36L at 22:14 UTC. Trace data at the event: 272 ft AGL, 154 kt GS, 0 fpm vertical. Approach stability score: 71/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 17 kt wind, 17 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/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
- 272 ft AGL at event
- 154 kt ground speed
- 0 fpm vertical
- Approach stability 71/100
- 17 kt wind
- 17 kt crosswind component
- 16,093 m visibility
- METAR KMCO 231253Z 36004KT 10SM FEW055 FEW080 SCT130 SCT300 27/24 A2999
Flight context
- AAL2963
- American Airlines
- B738
- KMIA → KMCO
- 2026-01-31 22:14 UTC
- KMCO runway 36L
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