No fatalities

2017-01-25: Airbus A320-232 (VH-VGJ) — Jetstar Airways — Newcastle (Williamtown) Airport, New South Wales

Newcastle (Williamtown) Airport, New South Wales

On January 25, 2017, an Airbus A320-232 (registration VH-VGJ) operated by Jetstar Airways was involved in an aviation accident near Newcastle (Williamtown) Airport, New South Wales. No fatalities were reported. Investigators recorded the probable cause as: The diversion of the flight crew's attention from after-start flows and the captain's misidentification of the dispatcher led to incomplete memory items and failure to detect the error during the after-start checklist. This summary draws on records from the Australian Transport Safety Bureau (ATSB); 8 related events involving the same aircraft type or operator are linked below.

Sourcesthe Australian Transport Safety Bureau (ATSB)Primary reportUpdated 1779789482Data APIEditorial standards
Aircraft registered VH-VGJ
Aircraft registered VH-VGJ. Photo: Simon_sees from Australia / CC BY 2.0, via Wikimedia Commons

During pushback from bay 4, the crew of VGJ was distracted by a potential collision with another aircraft. The captain misidentified a dispatcher, leading to incomplete after-start flows and undetected checklist errors.

Incident Overview

Aircraft VGJ was pushed back from bay 4. As the flight crew began their after-start flows, their attention was diverted by a potential risk of collision associated with taxi instructions and the movement of an aircraft parked on bay 5. Following confirmation between the conflicting 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.

Sequence of Events

During this time, the tug, which would normally wait beside the departing aircraft for the dispatcher, had moved away from VGJ toward the terminal to avoid a conflict with the bay 5 aircraft. Consequently, the dispatcher sighted by the captain was next to the tug used for the pushback of VGJ. This proximity potentially created an association in the captain's mind between the tug and the dispatcher, leading the captain to assume that the dispatcher had removed the nose wheel steering pin and moved away from the aircraft.

After Start Checks

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 omission was not detected during the after-start checklist because the captain had misidentified the dispatcher for the bay 5 aircraft as the dispatcher for VGJ.

Outcome

As a result, the dispatcher connected to VGJ was not cleared to disconnect prior to VGJ starting to taxi.

Probable cause

The diversion of the flight crew's attention from after-start flows and the captain's misidentification of the dispatcher led to incomplete memory items and failure to detect the error during the after-start checklist.