Go-around — AVA028

KMCO · 35R

2026-05-03 17:07 UTC· A320

AVA028 was inbound to KMCO on 2026-05-03. SkyMeter detected a go-around at Orlando International Airport (KMCO) on runway 35R at 17:07 UTC. Trace data at the event: 1661 ft AGL, 193 kt GS. METAR at the time reported 12 kt wind, 4 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 →

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 35R
  • 1661 ft AGL at event
  • 193 kt ground speed
  • 0 fpm vertical
  • 12 kt wind
  • 4 kt crosswind component
  • 16,093 m visibility
  • KMCO 201253Z 36005KT 10SM FEW030 SCT110 BKN250 27/23 A2996

Flight context

  • AVA028
  • A320
  • 2026-05-03 17:07 UTC
  • KMCO runway 35R

All events on this flight

Go-around 17:07:11 UTC · KMCO runway 35R · 1,661 ft AGL · 193 kt GS
Go-around 17:07:11 UTC · KMCO runway 35R · 1,661 ft AGL · 193 kt GS

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