Taxiing aircraft departs without dispatcher disconnection

No fatalities • Newcastle (Williamtown) Airport, New South Wales

A flight crew on aircraft **VGJ** failed to ensure the ground dispatcher had disconnected before taxiing due to a distraction involving a nearby aircraft.

What happened

During the departure process for aircraft VGJ, the flight crew began their after-start procedures following a pushback from bay 4. During this period, the crew's attention was diverted by radio communications and the movement of another aircraft parked at bay 5, which presented a potential collision risk.

While managing this potential conflict, the captain misidentified a dispatcher working with the aircraft at bay 5 as the dispatcher assigned to VGJ. At the same time, the tug used for the pushback of VGJ had moved toward the terminal to avoid the nearby aircraft. Because the captain saw a dispatcher near the departing tug, they incorrectly assumed their own dispatcher had already removed the nose wheel steering pin and moved away. This led to the aircraft beginning its taxi sequence without the crew confirming that the ground crew had actually disconnected.

The investigation

The investigation focused on why the after-start checklist failed to identify that the dispatcher was still connected. It was determined that the crew's attention was split by the taxi instructions and movements of the aircraft at bay 5. The investigation found that the captain's misidentification of the ground personnel, combined with the visual association of the dispatcher with the moving tug, created a false sense of security regarding the status of the steering pin and the disconnection process.

Findings

  • The flight crew's attention was diverted from their standard after-start flows by the risk of collision with an aircraft at bay 5.
  • The captain misidentified the dispatcher for the aircraft at bay 5 as the dispatcher for VGJ.
  • The movement of the tug toward the terminal contributed to the captain's incorrect assumption that the dispatcher had completed their tasks and moved away.

Probable cause

The flight crew's attention was diverted by a potential collision risk with another aircraft, leading the captain to misidentify a ground dispatcher and fail to verify that the aircraft had been disconnected prior to taxiing.

Frequently asked questions

What happened in the 2017-01-25 Airbus A320-232 accident near Newcastle (Williamtown) Airport, New South Wales?

A flight crew on aircraft **VGJ** failed to ensure the ground dispatcher had disconnected before taxiing due to a distraction involving a nearby aircraft.

Were there any fatalities in the 2017-01-25 Airbus A320-232 accident?

No fatalities were recorded in this accident.

What aircraft was involved and where did it happen?

The accident on 2017-01-25 involved a Airbus A320-232, registration VH-VGJ, operated by Jetstar Airways, at Newcastle (Williamtown) Airport, New South Wales.

What was the probable cause of the accident?

The flight crew's attention was diverted by a potential collision risk with another aircraft, leading the captain to misidentify a ground dispatcher and fail to verify that the aircraft had been disconnected prior to taxiing.

Loading the flight search…