No fatalities

Melbourne Airport: Unsafe Proximity and Missed Approach Below Minimum Vector Altitude (A6-EBU)

Melbourne Airport, Victoria

On July 5, 2015, a The Boeing Company 777-31HER (registration A6-EBU) operated by Emirates was involved in an aviation accident near Melbourne Airport, Victoria. No fatalities were reported. Investigators recorded the probable cause as: These findings should not be read as apportioning blame or liability to any particular organisation or individual. Safety issues, or system problems, are highlighted in bold to emphasise their importance. This summary draws on records from the Australian Transport Safety Bureau (ATSB); 15 related events involving the same aircraft type or operator are linked below.

Sourcesthe Australian Transport Safety Bureau (ATSB)Primary reportUpdated 2026-05-26Data APIEditorial standards
Aircraft registered A6-EBU
Aircraft registered A6-EBU. Photo: Aero Icarus from Zürich, Switzerland / CC BY-SA 2.0, via Wikimedia Commons

On 5 July 2015, three aircraft came into unsafe proximity during take-off and landing at Melbourne Airport. One aircraft was later radar vectored in a missed approach below the minimum vector altitude.

Incident Overview and Context On the night of 5 July 2015, an operational safety event occurred at Melbourne Airport in Victoria. During the period, three aircraft came into unsafe proximity while conducting take-off and landing operations. The event involved multiple aircraft in close proximity during critical phases of flight, highlighting potential risks in air traffic management during nighttime operations. The specific aircraft types, registrations, operators, and exact locations within the airport were not provided in the source material. ## Controller Actions and Missed Approach Shortly after the unsafe proximity event, one of the aircraft was radar vectored during a missed approach. This maneuver was conducted while the aircraft was below the minimum vector altitude (MVA). The minimum vector altitude is a critical safety parameter designed to ensure adequate terrain clearance during radar vectoring. The fact that the aircraft was vectored below this altitude indicates a deviation from standard safety procedures, which may have increased the risk of controlled flight into terrain or other hazards. ## Organisational Issues and Investigation Focus The investigation into this event focused on two primary areas: the actions taken by air traffic controllers and the organisational issues identified during the process. The analysis examined how controller decisions contributed to the unsafe proximity and the subsequent missed approach below MVA. Additionally, the investigation looked at broader organisational factors that may have influenced the event, such as training, procedures, communication, or resource management. The source does not specify the exact nature of these organisational issues or the final conclusions of the investigation. ## Safety Implications The event underscores the importance of maintaining safe separation between aircraft during take-off and landing, as well as adhering to minimum vector altitude requirements during missed approaches. It highlights the need for robust air traffic management practices, particularly during nighttime operations when visual references are limited. The investigation's focus on both controller actions and organisational issues suggests a comprehensive approach to identifying and addressing potential safety risks in aviation operations.