Sydney Airport under investigation after two more near-miss incidents 

The Australian Transport Safety Bureau (ATSB) is examining separate events involving Virgin Australia and Qantas aircraft on August 16, and a Jetstar Airbus A320 on August 25. 

Qantas Boeing 737-800
Qantas Boeing 737-800 Photo: © Kurt Ams | Qantas

Australia’s air safety investigator has opened two further investigations into aircraft incidents at Sydney Airport, adding to a growing number of recent events involving potential conflicts between aircraft on the ground.

The Australian Transport Safety Bureau (ATSB) is examining separate events involving Virgin Australia and Qantas aircraft on August 16, and a Jetstar Airbus A320 on August 25. 

Neither incident resulted in injuries or aircraft damage, and the regulator has classified both as incidents rather than serious incidents.

The latest investigations come as the ATSB is already examining four other incidents at Sydney Airport, including a recent event in which a flight attendant was injured.

Virgin and Qantas aircraft come into conflict

The first incident to be newly investigated occurred on August 16 after Virgin Australia Boeing 737 VH-IXJ diverted to Sydney while operating flight VA1589 from Melbourne to Newcastle.

After landing on runway 16L, the aircraft began taxiing north on taxiway B. At the same time, Qantas Boeing 737 VH-VZV, operating QF420 from Melbourne, was leaving runway 16R via taxiway B8.

Air traffic control instructed the Virgin crew to give way to the Qantas aircraft. However, according to the ATSB investigation report, the instruction was not correctly read back by the Virgin crew and the incorrect readback was not identified by the controller.

Virgin Australia 737-800
Photo: Ryan / stock.adobe.com

As the Qantas aircraft vacated the runway, its crew saw the Virgin 737 approaching from the right. The Qantas aircraft stopped and the crews clarified the taxiing sequence.

The ATSB said its investigation will examine the actions of the flight crews and controllers, alongside recorded data and other evidence.

Jetstar A320 stopped during pushback

A separate incident occurred nine days later involving Jetstar Airbus A320 VH-VFX, which was preparing to depart from Sydney to Launceston.

The aircraft was being prepared for pushback from its parking stand when the controller allegedly failed to provide the crew with complete traffic information, which the pilots would need to pass on to the tug team carrying out the push back. 

Specifically, the pilots were not told about another aircraft taxiing behind the A320.

The conflict was identified by the pushback crew, who stopped the manoeuvre and returned the aircraft to its stand.

Jetstar Airbus A320
Photo: FiledIMAGE / stock.adobe.com

The ATSB has described the event as a “failure to pass traffic”, and is now examining how the relevant traffic information was handled before the pushback commenced.

The regulator’s report does not identify the other aircraft involved.

As with the August 16 incident, investigators are likely to want to interview air traffic controllers and flight crew, review available recorded data and collect other relevant evidence.

Sydney airport already under scrutiny

The two new investigations add to a series of recent occurrences at Sydney Airport that have prompted scrutiny of ground movements and air traffic information at Australia’s busiest hub.

The ATSB said the investigations are being conducted separately, although teams will coordinate their work.

Depending on the evidence collected, the investigations could subsequently be expanded or combined.

The regulator is expected to publish preliminary reports on the latest investigations within six to eight weeks, although the ATSB’s investigation is not likely to conclude until next year.

Runway incursion earlier in August 

It comes as the ATSB is investigating a runway incursion at Sydney Airport after a Virgin Australia Boeing 737 rejected its take-off when another 737 crossed the runway ahead of it.

The incident occurred on August 9, when Virgin Australia flight VA555 was cleared for a full-length departure from runway 34L to Perth. 

As the crew applied take-off thrust, they saw a Qantas 737 crossing the runway from taxiway Lima.

Qantas Boeing 737 taxiing on tarmac

The Virgin crew stopped the aircraft on the runway, while air traffic control cancelled its take-off clearance. The Qantas aircraft then cleared the runway, allowing the Virgin 737 to be re-cleared for departure.

The Qantas crew reported that they had received clearance from ATC to cross the runway.

An ATSB investigation is underway. 

Cabin crew injured in ‘taxiing proximity event’

The ATSB is also investigating what it has classed as an accident at Sydney Airport on the same day – August 9 – involving a Jetstar Airbus A320 and a Qatar Airways Boeing 777 being towed by a tug.

The A320, operating as flight JQ402 to the Gold Coast, was taxiing for departure when its crew saw the 777 in close proximity on a crossing taxiway. 

Qatar Airways 777-200
Photo: Colin Cooke Photo / Wikimedia Commons

Both aircraft stopped abruptly, with a cabin crew member on the A320 seriously injured. Neither aircraft was damaged.

The ATSB has interviewed flight, ground and engineering personnel and reviewed flight recorder and air traffic surveillance data. I

Investigators are also examining procedures and training relating to aircraft towing.

Further work will include reviewing CCTV footage and interviewing air traffic controllers, the ATSB said. 

The investigation remains active, with the body expecting to complete its report in the first quarter of 2027.

Add a button.

Sign up for our newsletter and get our latest content in your inbox.

More from