Sydney Airport near-miss: why planes stopped 120 metres apart, and what remains unresolved

Sydney Airport’s July runway near-miss returned to the news on 30 September 2026 when the Australian Transport Safety Bureau released preliminary reports into four incidents at the airport. They document a severe runway conflict and put staffing and fatigue safeguards under scrutiny, without establishing whether those factors contributed.

In the 27 July incident, a Qantas Boeing 737 and a landing QantasLink Dash 8 stopped approximately 120 metres apart. The ATSB classified it as Category A, the highest runway-incursion severity level: Sydney’s first and only the third recorded at a major Australian airport since severity recording began in 2003.

What happened in the Sydney Airport near-miss?

According to the ATSB’s preliminary report, QF124 had arrived from Queenstown with 147 passengers and seven crew. QantasLink flight QLK424D, arriving from Canberra, carried 51 passengers and four crew. The two aircraft were approaching intersecting runways when a crossing clearance created the conflict.

After a 25-second handover, the controller taking over assumed the landing Dash 8 would leave the runway at an earlier exit. The 737 received permission to cross its runway. Controllers then ordered both aircraft to stop.

The July event is one of six occurrences under investigation from July and August. The new development is the publication of preliminary accounts, rather than another near-miss. The ATSB says these reports describe events and operational context; analysis and final findings will come later.

Did staffing or fatigue cause the conflict?

That remains unresolved. ABC News reports that four of the seven tower controllers had high predicted fatigue risk at the time of the July incident. ATSB Commissioner Angus Mitchell cautioned that a modelled risk is not proof that a controller was actually fatigued or that their performance suffered.

The July preliminary report records that all seven tower positions were separately occupied and no controller training was underway. The outgoing controller and the surface movement controller reported feeling alert despite their high predicted fatigue risk.

Across the investigations, the ATSB is examining combined operational roles, reliance on overtime, concurrent training or supervision, and fatigue-risk controls. It has not determined whether staffing contributed to any occurrence. Those questions remain part of the investigation, rather than settled explanations.

The July report also records that Airservices was operating under a CASA exemption while awaiting approval of its fatigue risk management system. Existing arrangements and additional reporting conditions applied; the current exemption expires on 28 February 2027.

What the other runway reports cover

The other preliminary reports concern two incidents on 9 August and one on 18 August. They include a Jetstar aircraft braking for a towed Qatar aircraft, a Qantas runway crossing conflicting with a Virgin take-off clearance, and a Qantas taxiing conflict.

A flight attendant suffered a fractured wrist in the Jetstar braking event on 9 August. Separately, Mitchell told ABC that controllers, pilots or ground crews intervened in all six incidents to prevent more serious outcomes.

How Sydney compares with other major airports

The ATSB also released a statistical study covering Adelaide, Brisbane, Melbourne, Perth and Sydney from January 2016 to August 2026. It recorded 599 ground-conflict occurrences, almost half involving runway incursions.

Sydney recorded 11 occurrences in July and August, compared with roughly three expected from its historical two-month average. Excluding those two months, its overall occurrence numbers were relatively consistent across the study period.

National occurrence rates were broadly steady after allowing for a Perth spike associated with stop bars. Sydney had the highest post-COVID rate among the five airports, although its runway configuration and traffic complexity complicate comparisons.

The study describes patterns rather than proving causes. Aircraft movements for June to August 2026 were projected because published movement data ended in May. Attribution of an occurrence does not itself assign fault or establish a procedural breach.

What Sydney Airport and the safety regulator said

In its 30 September statement, Sydney Airport said: “Safety is Sydney Airport’s highest priority.” It said it would support the minister and Airservices as they considered the preliminary material, and awaited final reports and recommendations.

The airport cited Transport Minister Catherine King’s account of CASA chief Pip Spence’s assessment that Sydney Airport and Australia’s aviation system remained safe. Separately, a CASA spokesperson told ABC that the airport and national network remained safe after reviewing the preliminary reports. CASA is also conducting a safety assurance review into possible underlying operational or system issues.

Airservices told ABC that “safety remains our number one priority” and pledged to review the reports and work with the ATSB and CASA on improvements. Qantas operational safety head Captain Mark Cameron said the airline remained confident in Australia’s safety controls and was working with the industry to improve Sydney air traffic control operations.

What happens next in the ATSB investigations?

King said addressing operational and workforce challenges was critical to safe, reliable air traffic control. She pointed to the Sydney Airport Air Traffic Control Working Group, which brings together government, industry, workforce and regulatory participants. Airservices is implementing a Sydney Service Resilience Plan.

The ATSB says it will notify relevant parties immediately if critical safety issues emerge and publish final reports after each investigation. ABC reports that some investigations could take up to 12 months. That is an estimate, not a fixed release date; final causes and recommendations remain outstanding.