Investigation number
AO-2016-154
Occurrence date
Location
Melbourne Airport
State
Victoria
Report release date
Report status
Final
Investigation level
Short
Investigation type
Occurrence Investigation
Investigation status
Completed
Aviation occurrence category
Interference from the ground
Occurrence class
Incident
Highest injury level
None

What happened

During the period from 30 September 2016 to 3 November 2016, a series of unlawful communications occurred on multiple air traffic control (ATC) frequencies and the aircraft emergency frequency around the Melbourne area, Victoria.

On 30 September, the flight crew of an aircraft approaching Melbourne Airport, reported hearing two instructions on the Melbourne tower (Figure 1) ATC frequency. The Melbourne tower controller did not make or hear the instructions, and there was no impact on operations.

On 25 October, on three occasions, flight crew of aircraft landing on runway 34 at Melbourne Airport received instructions, via unlawful broadcasts from an individual impersonating a Melbourne tower controller, on the Melbourne tower frequency. The Melbourne tower controller heard the broadcasts and immediately provided clarifying instructions to the flight crew. There was no impact on aircraft operations.

Figure 1: Melbourne airport ATC tower

Figure 1: Melbourne airport ATC tower

Source: Airservices Australia

On 27 October, at about 1429 eastern daylight time, ATC received reports from flight crew of emergency broadcasts on the aircraft emergency frequency, apparently being transmitted by multiple aircraft. The broadcasts indicated an inflight emergency to the north of Melbourne. In response to these reports, ATC declared a distress phase[1] and, in accordance with emergency procedures, contacted the Australian Maritime Safety Authority (AMSA). At 1502, AMSA confirmed that the broadcasts were false and cancelled the distress phase.

At 1539, ATC received two further reports of emergency broadcasts on the aircraft emergency frequency. The broadcasts used the registration of an aircraft which was operating to the north of Melbourne at that time. The broadcasts indicated an inflight emergency overhead the Melbourne metropolitan area. ATC immediately declared a distress phase. Air traffic control then contacted the aircraft, the flight crew confirmed that they had not made the broadcasts and that operations were normal. At 1542, having confirmed that the emergency broadcasts on the aircraft emergency frequency were false, ATC cancelled the distress phase.

At 1721, a Boeing 737-800 aircraft approached runway 16 at Melbourne airport. As the aircraft descended through about 200 ft above ground level, the flight crew received the instruction ‘go around’.[2] The flight crew could not determine a reason for the instruction, however, recognising that questioning the instruction at that time could create further confusion, elected to conduct the go around. As the flight crew commenced the go around, the controller confirmed that the instruction had not been broadcast by the controller and that the aircraft remained cleared to land. As the flight crew had already commenced the go around, they elected to continue the procedure. The aircraft returned to land without further incident.

At 1724, ATC personnel updated the Melbourne Airport automatic traffic information service (ATIS)[3] used by arriving and departing aircraft crew for airport information to include notification of the unlawful broadcasts.

At 1739, the ATIS was further updated to include the information that ATC would use light signals to confirm aircraft clearances in the event of further unlawful broadcasts.

At 1929, the Avalon approach controller received an emergency broadcast using the registration of an aircraft which was operating to the north-west of Melbourne at that time. Air traffic control contacted the aircraft, the flight crew confirmed that they had not made the broadcasts and that operations were normal. No distress phase was raised and there was no impact on operations.

On 31 October, ATC received a report from the flight crew of an aircraft departing Melbourne Airport of unlawful broadcasts on the aircraft emergency frequency. The broadcasts simulated aircraft ground proximity and warning system aural alarms. There was no impact on operations.

On 3 November, ATC received multiple reports from flight crew of unlawful broadcasts occurring on the aircraft emergency frequency. The broadcasts indicated an inflight emergency, the flight crew receiving the broadcast responded, however no reply was received. There was no impact on operations.

Air Traffic Control procedures

The provider of civil ATC services in Australia, Airservices Australia, had the following procedures in place to manage unlawful broadcasts on ATC frequencies:

Manual of air traffic services (MATS)

The Airservices Australia MATS contained the following procedure for managing malicious radio transmissions:

  • Report unauthorised (malicious) transmissions to aircraft as detailed in local instructions.

MATS also contained the following instructions to assist controllers in managing unforeseen situations which have not been documented:

Best judgement

Do not allow anything in these instructions to preclude you from exercising your best

judgement and initiative when:

a) the safety of an aircraft may be considered to be in doubt; or

b) a situation is not covered specifically by these instructions.

Local Instructions

Melbourne tower local instructions did not provide procedures or guidance to controllers on the handling of unlawful communications.

ATC personnel response

In the absence of detailed procedures, ATC personnel used the following to manage the impact of the unlawful communications:

  • Shift managers briefed controllers about the activity.
  • Shift managers also provided controllers with recordings of previous events to familiarise the controllers with the individual’s voice.
  • Controllers contacted individual aircraft directly to advise that unlawful broadcasts were occurring. When controllers heard unlawful broadcasts, they immediately clarified clearance details with the affected aircraft.
  • The no-radio procedure of using light signals to provide aircraft clearance details was determined to be a suitable method to confirm clearances.
  • Included a warning on the Melbourne Airport ATIS.
  • Recorded all available information.

Airservices Australia Comment

The provider of civil air traffic services within Australia, Airservices Australia, provided the following comments:

  • Airservices considers that the established organisational resilience/crisis management practices proved effective to handle each unlawful communication event. Given it is not possible to document all elements of scenarios that a controller may face, Airservices training and risk management practices are designed to enable controllers to manage a range of unusual situations which are not documented.
  • Controllers will always assume that an ATC broadcast is real, as was prevalent in these occurrences. The In-Flight Emergency Response checklist was utilised and followed until it was determined that the broadcasts were hoax calls and the aircraft were not in distress. Having an established procedure to manage hoax calls may lead to ambiguity with regards to the validity of a broadcast.
  • The development of detailed procedures may not achieve a safety outcome as it would be impracticable to cater for all situations. Furthermore, it may restrict initiative required by ATC to safely manage each scenario on a case-by-case basis.

Safety analysis

Despite an absence of local instructions, ATC personnel were able to use best judgement to implement effective methods to manage the unlawful communications.

The false emergencies scenarios were handled quickly and effectively within existing emergency procedures. Air traffic control and AMSA personnel were able to quickly confirm the non-existence of the emergency situations and cancel the distress phases.

The unlawful communications resulted in minimal impact on aircraft, ATC and AMSA operations.

Findings

These findings should not be read as apportioning blame or liability to any particular organisation.

  • There were minimal documented local instructions in place for managing unlawful communications.
  • Despite an absence of documented local instructions, training and crisis management practices enabled ATC personnel to effectively manage the unlawful communications to minimise the impact on aircraft and AMSA operations.

ATSB comment

The unlawful communications were broadcast by one individual. The Australian Federal Police arrested and charged this individual with five offences relating to the communications.

Safety message

Unlawful communications transmitted with malicious intent, while rare, have the potential to impact the safe operation of aircraft and, as demonstrated by this series of events, divert AMSA away from their core tasks.

Despite an absence of local instructions, ATC personnel were able to use best judgement to implement effective methods to quickly and effectively manage the unlawful communications to minimise the risk to flight safety.

__________

  1. Distress phase is an emergency phase declared by the air traffic services when there is reasonable certainty that an aircraft and its occupants are threatened by grave and imminent danger or require immediate assistance.
  2. Go around, the procedure for discontinuing an approach to land, is a standard manoeuvre performed when a pilot is not completely satisfied that the requirements for a safe landing have been met. This involves the pilot discontinuing the approach to land and may involve gaining altitude before conducting another approach to land.
  3. ATIS is a continuous broadcast of recorded information relevant to airport operations. Flight crew operating at a controlled aerodrome will listen to the information provided by the ATIS prior to arrival, or departure.

Aviation Short Investigations Bulletin - Issue 58

Purpose of safety investigations

The objective of a safety investigation is to enhance transport safety. This is done through:

  • identifying safety issues and facilitating safety action to address those issues
  • providing information about occurrences and their associated safety factors to facilitate learning within the transport industry.

It is not a function of the ATSB to apportion blame or provide a means for determining liability. At the same time, an investigation report must include factual material of sufficient weight to support the analysis and findings. At all times the ATSB endeavours to balance the use of material that could imply adverse comment with the need to properly explain what happened, and why, in a fair and unbiased manner. The ATSB does not investigate for the purpose of taking administrative, regulatory or criminal action.

Terminology

An explanation of terminology used in ATSB investigation reports is available here. This includes terms such as occurrence, contributing factor, other factor that increased risk, and safety issue.

Publishing information 

Released in accordance with section 25 of the Transport Safety Investigation Act 2003

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2017

Ownership of intellectual property rights in this publication

Unless otherwise noted, copyright (and any other intellectual property rights, if any) in this report publication is owned by the Commonwealth of Australia.

Creative Commons licence

With the exception of the Coat of Arms, ATSB logo, and photos and graphics in which a third party holds copyright, this publication is licensed under a Creative Commons Attribution 3.0 Australia licence.

Creative Commons Attribution 3.0 Australia Licence is a standard form licence agreement that allows you to copy, distribute, transmit and adapt this publication provided that you attribute the work.

The ATSB’s preference is that you attribute this publication (and any material sourced from it) using the following wording: Source: Australian Transport Safety Bureau

Copyright in material obtained from other agencies, private individuals or organisations, belongs to those agencies, individuals or organisations. Where you wish to use their material, you will need to contact them directly.