Investigation number
AO-2017-015
Occurrence date
Location
Newcastle (Williamtown) Airport
State
New South Wales
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
Serious Incident
Highest injury level
None

What happened

On 25 January 2017, a Jetstar Airways Airbus A320-232, registered VH-VGJ (VGJ), taxied for a scheduled passenger transport flight from Newcastle (Williamtown) Airport, New South Wales, to Brisbane Airport, Queensland. There were six crewmembers and 165 passengers on board the aircraft. The captain was the pilot monitoring and the first officer was the pilot flying.[1]

The aircraft parked at bay 4 at the Newcastle Airport terminal for passenger disembarkation and boarding (Figure 1). Bay 4 was a ‘pushback’ bay, which means that when the aircraft is ready for departure, the aircraft is pushed backwards from the parking bay by a tug under the supervision of a dispatcher. Another operator’s aircraft was parked on bay 5, to the left of VGJ. Bay 5 was a ‘power-out’ bay which means that on departure, aircraft taxi from the bay under their own power by turning sharply away from the terminal.

At about 1836 Eastern Daylight-savings Time (EDT), the crew of VGJ received a clearance from the surface movement controller to pushback, which placed VGJ to the right rear quarter of the aircraft parked on bay 5, and facing towards taxiway H (Figure 1). The dispatcher was walking beside the aircraft and was connected to the nose of VGJ by a headset for communications with the flight crew. The flight crew started the engines during the pushback in accordance with standard procedures. After the pushback was completed, the flight crew set the brakes, the tug disconnected and the dispatcher removed the nose wheel steering pin. [2] The flight crew then started their ‘after start flows’ (see: After start flows). After the tug disconnected from VGJ, the tug driver moved it to a position adjacent to the left wingtip of VGJ, facing towards the aircraft on bay 5.

At about 1838, the crew of the aircraft on bay 5 requested a clearance to taxi for departure. The surface movement controller questioned whether the aircraft could taxi to taxiway J and avoid VGJ.[3] The flight crew responded that they could. At this stage, the flight crew on board VGJ interrupted their ‘after start flows’ to monitor the other aircraft. The captain, seated in the left seat of VGJ, did not believe there was sufficient clearance for the other aircraft to turn around for taxiway J without a collision. The aircraft started to taxi from bay 5 in a right power-out turn, but stopped within a few metres.

When the tug driver observed the aircraft on bay 5 move towards them,[4] they moved the tug away from VGJ over to the terminal side of the apron, near bay 4, to remain clear of the other aircraft. Meanwhile the dispatcher assisting the aircraft on bay 5, had also moved from bay 5 towards bay 4 in order to monitor and signal wingtip clearance for the left wing of the aircraft conducting the power-out from bay 5.

Figure 1: Newcastle Airport apron

Figure 1: Newcastle Airport apron

Source: Google earth, annotated by ATSB

Radio communications continued between air traffic control and the aircraft departing from bay 5, until it was confirmed that the aircraft would wait for VGJ before taxiing any further. The captain of VGJ, who was looking out the left window of the flight deck towards the bay 5 aircraft and the terminal, sighted their tug and a dispatcher near bay 4. They assumed that the dispatcher near bay 4 was their dispatcher, who had disconnected from their aircraft while they were monitoring the bay 5 aircraft movements and radio communications. At about 1840, the flight crew on board VGJ requested and received a clearance to taxi for runway 12 via taxiway H. The flight crew selected their taxi lights on, released the brakes and increased power.

The dispatcher for VGJ was still connected to the aircraft nose with their headset and waiting for their clearance from the flight crew to disconnect. They observed the taxi lights for VGJ illuminate, then they heard the engine noise increase, and then the aircraft started to taxi. They immediately disconnected their headset from the aircraft and moved clear to the left of the aircraft towards the terminal with the headset and the nose wheel steering pin. Once the dispatcher was clear of the aircraft, they turned around to display the nose wheel steering pin to the flight crew, but the captain was not looking towards them.

After start flows

On completion of starting both engines, the flight crew conduct their ‘after start flows’, which are memory item checks split between the pilot flying and pilot monitoring (Figure 2). The second-to-last item for the pilot flying is the announcement to the dispatcher that they are clear to disconnect. After the dispatcher disconnects their headset from the aircraft, they walk clear of the aircraft and provide a ‘thumbs-up’ signal to the flight crew while holding up the nose wheel steering pin for the flight crew to sight. During the ‘after start flows’, the attention of the flight crew on board VGJ was diverted to the radio communications between the aircraft parked on bay 5 and the surface movement controller.

Figure 2: After start flows

Figure 2: After start flows

Source: Operator

The last item on the ‘after start flows’ is for the flight crew to complete the challenge and response ‘after start checklist’, which is as follows:

ANTI ICE…AS RQRD

ECAM STATUS…CHECKED

PITCH TRIM…SET

RUDDER TRIM…ZERO

DISP CLRNCE…SIGHTED

The last item on the ‘after start checklist’ is confirmation that the dispatcher was sighted clear of the aircraft. The left seat or right seat pilot reports to the other pilot ‘dispatch clearance sighted’. In this serious incident, the terminal was on the left side of VGJ and therefore it was expected that the captain, in the left seat, would sight the dispatcher. The captain reported remembering sighting a dispatcher, but could not recall what was communicated on the flight deck between the flight crewmembers.

On completion of the ‘after start checklist’, the flight crew request taxi clearance and turn on the taxi light.

Tug movements

After the tug disconnected from the aircraft, the tug driver moved the tug clear of the aircraft and initially waited for the dispatcher near the left wingtip. The tug normally waited beside the aircraft to offer the dispatcher a lift and because the nose wheel steering pin is stowed in the tug when removed from the aircraft. However, when the bay 5 aircraft started to move, the tug moved from the left wingtip to the terminal building near parking bay 4.

Safety analysis

After VGJ was pushed-back from bay 4 and the flight crew had started their ‘after start flows’, their attention was diverted to a potential risk of collision associated with the taxi instructions and movement of an aircraft parked on bay 5. Following confirmation between the conflict aircraft and surface movement control that they would wait for VGJ, the captain of VGJ misidentified the dispatcher for the bay 5 aircraft as their own dispatcher. At this time, the tug, which would normally wait beside the departing aircraft for the dispatcher, had moved away from VGJ towards the terminal to avoid a conflict with the bay 5 aircraft. Therefore, the dispatcher sighted by the captain, was next to the tug used for the pushback of VGJ. This potentially provided an association between the tug and the dispatcher in the mind of the captain, who assumed the dispatcher had removed the nose wheel steering pin and moved away from the aircraft. The diversion of the flight crew’s attention away from their ‘after start flows’ probably resulted in the pilot flying not completing their memory items. This was not detected in the ‘after start checklist’ because the captain had misidentified the dispatcher for the bay 5 aircraft as the dispatcher for VGJ. Consequently, the dispatcher connected to VGJ was not cleared to disconnect prior to VGJ starting to taxi.

Findings

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

  • The flight crew on board VGJ were distracted during their ‘after start flows’ by the radio communications between an aircraft parked on bay 5 and surface movement control, and the subsequent movement of that aircraft which had a potential risk of collision with VGJ.
  • The captain on board VGJ misidentified the dispatcher for the bay 5 aircraft as their own dispatcher, which resulted in VGJ starting to taxi without clearing the dispatcher to disconnect.

Safety message

Following this serious incident the captain reported that their most important lesson was distraction management. They considered either slowing down the ‘after start flows’ or re-starting the ‘flows’, before the ‘after start checklist’, as the most practical risk mitigation strategies.

Part of Aviation Short Investigations Bulletin - Issue 60

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.

__________

  1. Pilot Flying (PF) and Pilot Monitoring (PM): procedurally assigned roles with specifically assigned duties at specific stages of a flight. The PF does most of the flying, except in defined circumstances; such as planning for descent, approach and landing. The PM carries out support duties and monitors the PF’s actions and the aircraft’s flight path.
  2. The nose wheel steering pin is inserted in the nose gear to enable the tug to steer the nose wheel.
  3. The air traffic control tower is located on the opposite side of the runway to the civil terminal apron.
  4. Gender-free plural pronouns: may be used throughout the report to refer to an individual (i.e. they, them and their).

 

Aircraft Details
Manufacturer
Airbus
Model
A320-232
Registration
VH-VGJ
Aircraft Operator
Jetstar Airways
Serial number
4460
Operation type
Air Transport High Capacity
Sector
Jet
Departure point
Williamtown, NSW
Destination
Brisbane, Qld
Damage
Nil