Investigation number
AO-2016-117
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 type
Taxiing collision/near collision
Occurrence category
Incident
Highest injury level
None

What happened

On 9 September 2016, at about 0005 Eastern Standard Time (EST), an AirAsia X Airbus A330-343X, registered 9M-XXK (XXK) pushed back[1] from gate D12 to disconnect point S7 (Figure 1) at Melbourne Airport, Victoria, to operate scheduled passenger flight D7213 to Kuala Lumpur, Malaysia. Although it was night-time, the apron was well lit by flood lights.

The aircraft maintenance engineer (AME) conducting the pushback was provided by a contracted company, the tug and tug driver were provided by a third company. Prior to commencing the pushback, the AME installed the nose gear steering bypass pin,[2] connected the tow bar to both the aircraft nose landing gear and the tug. During the pushback, as the tug moved the aircraft, the AME was seated in the tug. The AME was in continuous communication with the flight crew using a headset connected directly through a headset jack to the cockpit. During the pushback, the flight crew started one engine. After reaching disconnect point S7, the flight crew applied the park brake and started the second engine.

Figure 1: Melbourne Airport apron section overview

Figure 1: Melbourne Airport apron section overview

Source: Airservices Australia, modified by ATSB

At 0008, after both engines were started, the AME disconnected the headset and tow bar from both the aircraft and the tug, the AME also removed the bypass pin. The tug driver turned the tug around to allow the AME to attach the tow bar to the rear of the tug. The tug driver then moved the tug and tow bar to a position forward of the aircraft’s right engine and visible to the first officer (Figure 2). The AME then walked to a position in front of the tug, and displayed the bypass pin to the first officer. The AME received a hand signal from the first officer confirming the first officer had sighted the bypass pin. Sighting the bypass pin was the final item on the flight crew’s after start checklist. The flight crew then contacted ATC and obtained a taxi clearance.

At 0009, the first officer confirmed to the captain that the AME and tug were clear, the captain then began to taxi. At this time, the AME was walking towards the left side of the tug, which remained parked forward of the aircraft’s right engine and wing. As the AME walked, they detected the aircraft’s taxi light illuminate and the aircraft begin to move. The AME then ran toward the tug door and alerted the tug driver to the aircraft movement.

Video footage of the incident shows the tug driver taking action to avoid a collision with the taxiing aircraft.

The flight departed without further incident.

Figure 2: Positions at commencement of aircraft taxi

Figure 2: Positions at commencement of aircraft taxi

Source: Melbourne Airport, modified by ATSB

Flight crew procedures

The flight crew procedures included the following steps:

  • After the pushback and engine start sequence is complete, the bypass pin must be sighted.
  • Once taxi clearance is obtained, the flight crew shall ensure both sides of the aircraft are clear prior to taxi.

Flight crew comments

The flight crew of XXK provided the following comments:

  • Both flight crew interpreted the AME displaying the bypass pin as meaning the tug and AME were clear, and it was safe to commence taxi.
  • The flight crew assumed that ATC providing the taxi clearance meant that ATC had confirmed the tug was clear of the aircraft.
  • The first officer observed the tug and AME to the right of the aircraft and assessed that they were clear of the right engine.

Aircraft maintenance provider procedures

The ground handling procedures include the following steps:

  • Once the tow bar is connected to the tow vehicle (after being disconnected from the aircraft), the tow vehicle must move away to an area that is visible to the flight crew.
  • At a suitable and safe distance from the aircraft, (the AME must) hold up the bypass pin to provide visual confirmation that it has been removed to the flight crew and give a ‘thumbs up’ signal indicating ‘clearance to proceed’. Once acknowledged by the flight crew, move away from the aircraft to a safe distance for the aircraft to taxi.

AME and tug driver comments

  • The tug driver and AME both commented that they expected the aircraft to remain stationary until they had moved clear of the S7 disconnect point boundary.

Airservices Australia safety bulletin

The AME and captain commented that they expected air traffic control (ATC) to confirm that the tug was clear of the aircraft and disconnect point S7 prior to providing a taxi clearance.

In 2015, ATC provider, Airservices Australia, identified some misinterpretation among pilots, airside drivers and ground crew regarding the responsibilities for collision avoidance on aerodrome movement areas and the services ATC provide to aircraft and/or vehicles operating on these areas. In response, on 12 November 2015, Airservices Australia released an Aeronautical Information Circular AIC (H32/15) and subsequently in 15 March 2016, this information was released as a safety bulletin, Safety of ground movement on a controlled aerodrome. The bulletin had been provided to the operators involved in this incident.

The bulletin contains the following information regarding operations on the apron and push-back approvals:

The pilot in command (with any assisting ground personnel) is responsible for avoiding collision on the apron. ATC push-back approvals and taxi clearances are only to regulate entrance to, and movement on, the taxiways and do not relate to movement on the apron areas.

When ATC issue approval for push-back or taxi clearance, they will only provide information about relevant known aircraft moving on the same apron. This information may be incomplete as ATC has limited knowledge (or visibility) of movements on the apron. Pilots must also obtain traffic information from assisting ground personnel and, where available, the apron service which may be established as a discrete service at some locations.

Safety analysis

The flight crew interpreted the AME showing the bypass pin at the end of the pushback sequence as notification that all vehicles and equipment were clear of the aircraft and it was safe to commence taxi. The ground crew expected that the flight crew would commence taxi only after all personnel and equipment had crossed the line demarcating the boundary of the S7 disconnect point. Both the flight crew and AME expected that the aircraft would not receive a clearance to taxi until ATC had confirmed that the tug and AME were clear. The misunderstandings by the parties involved during this sequence likely led to incorrect expectations of when the aircraft would begin taxi and the aircraft beginning to taxi prior to the tug moving clear.

The flight crew procedures required the flight crew to visually confirm that all ground equipment was clear of the aircraft prior to taxi. The first officer assessed that the tug and tow bar were clear of the right engine when they were not, although their perception may have been influenced by an expectation of them being clear given the communications with the AME and ATC providing taxi clearance.

Findings

This finding should not be read as apportioning blame or liability to any particular organisation or individual.

  • The flight crew and ground crew had differing understandings of procedures. These differing understandings led to different expectations of when the aircraft would commence taxi which resulted in the near collision.
  • The first officer incorrectly assessed the distance of the tug from the aircraft.

Safety message

Ground handling of large aircraft presents many safety risks and requires many separate operators to work closely together. Effective teamwork ensures safe and efficient ground operations.

This incident highlights the importance of separate operators working closely together and having procedures which are well harmonised. It is also important that these procedures are well understood and practiced by all individuals involved from the different operators to ensure all parties understand their role but also how their role interacts with other parties.

Also highlighted, is the importance of understanding the services provided by ATC. ATC provide separation between aircraft, personnel and equipment operating on manoeuvring areas. ATC do not separate aircraft from tugs and other ground personnel on apron areas such as disconnect point S7.

__________

  1. Pushback is a procedure during which an aircraft is pushed back, away from an airport gate or bay, by an external tug.
  2. The nose gear bypass pin is installed during the pushback sequence to bypass the normal aircraft steering, allowing the tug to control aircraft steering.

Aviation Short Investigations Bulletin - Issue 57

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.

Aircraft Details
Manufacturer
Airbus
Model
A330-343X
Registration
9M-XXK
Aircraft Operator
AirAsia X
Serial number
1433
Operation type
Air Transport High Capacity
Sector
Jet
Departure point
Melbourne, Vic.
Destination
Kuala Lumpur, Malaysia
Damage
Nil