SYDNEY AIRPORT: Qantas aircraft involved in near miss

Two Qantas aircraft were placed in conflict on intersecting runways at Sydney Airport last month (July 2026). This prompted an Australian Transport Safety Bureau (ATSB) investigation into what it describes as a “breakdown of coordination”.

The incident

The serious incident occurred at about 08.14 on 27 July 2026. A Qantas Boeing 737-800, registration VH-XZG, had arrived as QF124 from Queenstown , New Zealand and was taxiing along the airport’s east–west Runway 25.

Air traffic control cleared the 737 to cross Runway 34L . That’s Sydney’s main north–south runway. But a QantasLink Dash 8 Q400, registration VH-QOC, was still completing its landing roll after arriving from Canberra, according to the ATSB.

Conflict detected before a collision

Controllers detected the conflict and alerted both flight crews. The Boeing 737 stopped after passing the runway holding point, while the Dash 8 continued its landing. Nobody was injured and neither aircraft was damaged.

Qantas statements have stressed that both crews were following air traffic control instructions.

Sydney’s runway arrangement adds complexity. The 2,530-metre east–west Runway 07/25 intersects the 3,962-metre main Runway 16R/34L, meaning aircraft taxiing between the international terminal and other parts of the airport may need permission to cross an active runway according to information from Sydney Airport.

Staffing questions

The ATSB has not identified fatigue, staffing levels or any particular controller as the cause. Its investigation will examine recordings, operational data and interviews before reaching any conclusions.

The incident does come after repeated disruption at Sydney Airport blamed on shortages and absences of air traffic controllers. Airservices Australia has previously acknowledged that rostering and staffing constraints have affected Sydney operations. The controllers’ union has accused Airservices of failing to provide sufficient staff.

2PAXfly Takeout

The reassuring part of this incident is that it was detected and action taken to avoid a potential disaster. It means the overlapping layers of protection designed into the airport systems worked.

The downside is that it looks like the initial layer of protection failed, with both aircraft cleared to ‘use’ the same piece of the runway.

The event is classified as a ‘serious incident’ and runway incursion. That’s reassuring. However, we will need to wait until the final report in the last quarter of 2026. I know these reports take time and need to be thorough, but it does seem that weeks, not months, would be a more appropriate and modern timeline. Especially because this appears to be a fairly simple incident, and we live in a world of instant communication.