The Australian Transport Safety Bureau has released preliminary reports on two low-speed taxiing conflicts at Sydney Airport in August 2026. The October 26 releases describe how flight crews and ground personnel stopped aircraft as conflicts developed; they do not establish final causes.
Two August events, rather than new incidents
| Date | Aircraft involved | Sequence described by the ATSB |
|---|---|---|
| August 17, 2026 | Virgin Australia and Qantas Boeing 737s | The Qantas crew stopped as the Virgin aircraft passed in front while taxiing |
| August 25, 2026 | Jetstar Airbus A320 and QantasLink Dash 8 | The Dash 8 crew and the A320’s pushback team stopped when their movements conflicted |
The August 17 preliminary report, AO-2026-093, describes Qantas flight QF420 stopping with normal braking at about 9:41 a.m. local time as Virgin flight VA1589 crossed ahead.
The ATSB says the Virgin crew’s readback had omitted the instruction to follow the Qantas aircraft, and the controller had not recognised the incomplete readback. Both aircraft subsequently taxied to their terminals without further incident.
The August 25 report, AO-2026-092, describes a Jetstar A320 cleared to push back, followed about 30 seconds later by a taxi clearance for the QantasLink Dash 8 along the adjacent taxiway. The Dash 8 crew stopped after observing the A320 moving backwards. The pushback driver and dispatcher also stopped the A320 and alerted its crew.
The controller then instructed the A320 to return to its bay so the Dash 8 could pass behind it.
A documented readback change is planned for November 26
In the August 17 report, the ATSB records Airservices Australia’s response to an earlier safety issue, AO-2025-033-SI-01. That issue concerned guidance which did not explicitly require pilots to read back sequencing instructions.
Airservices advised the ATSB on September 17 that it had decided to add the instruction “follow” to the required-readback list in the relevant manuals and aeronautical publication. The report gives November 26, 2026 as the planned implementation date. This is a documented safety response, rather than a final finding about the causes of the August events.
What investigators have yet to determine
In the October 26 release, ATSB Chief Commissioner Angus Mitchell said “an important safety defence acted appropriately” when crews and ground personnel identified conflicts and acted.
The bureau is examining six Sydney coordination and conflict events separately while looking for common factors. It has not determined whether staffing resources contributed. The August 25 investigation will also consider tower visibility and the systems available to controllers.
A preliminary report sets out evidence collected so far. Findings and analysis belong in the final reports; the October releases should not be treated as proof of a staffing-related cause or a new airport closure.
See our Australia aviation coverage for related reporting. The ATSB’s linked reports contain the original incident illustrations and further investigation details.
Archive photograph: Sydney Airport control tower, December 23, 2015; not the August 2026 conflicts or evidence of tower conditions during them. Photo: Elisfkc / Wikimedia Commons, CC BY-SA 4.0. Resized and compressed to WebP; derivative retains the same licence.
