Go-around — QFA30

YMML · 34

2026-02-03 21:12 UTC· VHHH YMML· QANTAS AIRWAYS LIMITED· A333

QFA30 (Qantas Airways) was operating from VHHH to YMML on 2026-02-03. SkyMeter detected a go-around at Melbourne International Airport (YMML) on runway 34 at 21:12 UTC. Trace data at the event: 650 ft AGL, 136 kt GS. METAR at the time reported 21 kt wind, 7 kt crosswind component. 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/2787 2025-05-22 00:01Z – 2026-05-22 00:01Z SFC–6,000 ft

    S. FINEGAYAN, GU, Thursday, May 22, 2025 through Friday, May 22, 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 34
  • 650 ft AGL at event
  • 136 kt ground speed
  • 0 fpm vertical
  • 21 kt wind
  • 7 kt crosswind component

Flight context

  • QFA30
  • Qantas Airways
  • A333
  • VHHH → YMML
  • 2026-02-03 21:12 UTC
  • YMML runway 34

All events on this flight

Go-around 21:12:55 UTC · YMML runway 34 · 650 ft AGL · 136 kt GS
Go-around 21:12:51 UTC · YMML runway 34 · 653 ft AGL · 136 kt GS
Go-around 21:12:55 UTC · YMML runway 34 · 650 ft AGL · 136 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· YMML