Four Ground Conflicts, One Panel: What the ATSB's Sydney Airport Preliminary Reports Say and What They Leave Open

Rajkumar Agarwal5 October 20267 min read0 viewsSafety & Regulation
Four Ground Conflicts, One Panel: What the ATSB's Sydney Airport Preliminary Reports Say and What They Leave Open

The Australian Transport Safety Bureau (ATSB) released preliminary reports on 30 September 2026 into four of its six open investigations into aircraft conflicts at Sydney Kingsford Smith Airport. The occurrences took place between 27 July and 18 August. On the same day it published a statistical report comparing ground-conflict rates at Australia's major airports. The federal government also announced an independent panel to oversee how Airservices Australia, the air navigation service provider, responds to air traffic control problems at the airport.

The preliminary reports contain no findings or analysis. Per the ATSB, they set out the sequence of events in each occurrence and the operational context. Findings come only in the final reports.

The four events

The ATSB's release lists the four occurrences:

  • 27 July: a runway incursion in which a Qantas Boeing 737 was cleared to cross in front of a QantasLink Dash 8 in its landing roll.
  • 9 August: a taxiing proximity event in which a Jetstar Airbus A320 braked abruptly to avoid a Qatar Airways Boeing 777 under tow. A flight attendant on the A320 fell during the braking and fractured a wrist.
  • 9 August: a runway incursion and rejected take-off in which a Qantas 737 was cleared to cross the runway in front of a Virgin Australia 737 that had just been cleared for take-off.
  • 18 August: a taxiing conflict in which a Qantas Airbus A321 had to brake to let a Qantas 737 pass in front of it.

The remaining two of the six investigations have no preliminary report yet. The ATSB says the six occurrences are among 11 ground incidents reported at Sydney in July and August, according to ABC News' account of the commissioner's briefing.

The 27 July incursion

The most serious event was the first. ABC News reported that a "breakdown of coordination" led a controller to clear a Boeing 737 on flight QF124, carrying 157 people, to cross a runway while a QantasLink Bombardier Dash 8 on flight QLK424D, carrying 55, was landing.

According to the preliminary report as quoted by ABC, the 737 stopped before the intersection of runways 34L and 25 but within the runway surface area past the runway stop bars, which made it a runway incursion. The Dash 8 stopped before the same intersection. When both aircraft had stopped, they were about 120 metres apart.

ATSB Commissioner Angus Mitchell said the event was classed as a Category A runway incursion. ABC reported him saying it was the most severe such event at Sydney and only the third of its kind in Australia since the ATSB's records began in 2003.

The report records that the controller who issued the clearance had a "high predicted fatigue risk level" when giving a brief handover to another controller who was going on a break. ABC also reported the report's finding that four of the seven controllers in the tower at that time had a high predicted fatigue risk level. That is a prediction from Airservices' rostering model. It is not a measurement of how any controller was actually functioning.

Mitchell also said that in all six incidents safety defences operated in some form, and that controllers, pilots or ground crew acted to prevent more serious outcomes.

What the ATSB is examining

The ATSB's release says staffing in the Sydney tower during many of the occurrences "has emerged as a recurring area of enquiry". It identified three practices the investigations will look at: combining operational roles, routine reliance on overtime to fill shifts, and training or supervision being carried out alongside operational duties.

The bureau stressed that it has not determined whether staffing factors directly contributed to any occurrence. It said they could instead be underlying conditions that Airservices recognised and was managing effectively. The preliminary reports also note that Airservices' roster modelling predicted elevated fatigue risk for staff on many of the days when the conflicts occurred, which ABC reported as running from 27 July to 25 August.

Mitchell cautioned that an elevated fatigue risk does not in itself mean a controller was fatigued or that fatigue affected performance. The ATSB said it is examining whether the measures in place to manage that identified risk were effective. The bureau also noted that it does not investigate to apportion blame or liability. Its role, it said, is to identify systemic safety issues and make them public early.

If a critical safety issue emerges before the investigations finish, the ATSB says it will notify the relevant parties so they can act. The final reports on the 27 July, 9 August and 18 August events could take up to 12 months, ABC reported.

The statistical report

The accompanying report covers ground conflictions at Australia's five busiest airports from 2016 to August 2026. It was designed to test whether the cluster of Sydney events reflected a post-COVID trend or a local pattern.

According to Mitchell, reported ground-confliction rates nationally have remained broadly steady over the decade. Sydney, however, recorded the highest confliction rate per aircraft movement after COVID among the major airports, at around 20 per cent above the national average. He added that this should be viewed in the context of Sydney being the most complex airport in the country.

The analysis also found increases specific to Sydney in potentially high-consequence occurrences: runway incursions, taxiway near collisions and losses of separation attributed to air traffic control actions. ABC separately reported Mitchell saying Sydney recorded double the annual average of "information and procedural errors" compared with other major airports. That second figure appeared in ABC's account and not in the ATSB's written release, so the two should be read as separate statements.

The measure is broad. It groups several kinds of occurrence, and a rate above average does not mean aircraft nearly collided at that frequency.

The government's response

On 30 September the Minister for Infrastructure, Transport, Regional Development and Local Government, Catherine King, announced the Sydney Airport Air Traffic Control Independent Assurance Panel. Australian Flying reported the details of the announcement.

Retired Air Vice Marshal Ken Robinson AM chairs the panel. Peter Wilson and David Oliver are members. It has an initial term of six months. Its job is to give the government independent assurance that Airservices is putting in place timely and lasting measures to improve service stability, reliability and resilience, and its remit covers air traffic control workforce planning, recruitment, training, roster resilience and system improvements.

The panel sits alongside the existing Sydney Airport Air Traffic Control Working Group, which is led by the Department of Infrastructure and includes Airservices, the Civil Aviation Safety Authority (CASA), airlines, unions and Sydney Airport. Airservices is also running its own Service Resilience Plan for the airport. The panel monitors the response, and does not investigate the events.

King said the preliminary reports show every opportunity should be taken to improve aviation safety, and that the government expects Airservices to cooperate fully with the investigations and act promptly on issues identified.

What the agencies and airlines said

An Airservices spokesperson told ABC the organisation would review the interim reports, and the findings once the investigations concluded. The spokesperson said safety remains its number one priority and that it would work closely with the ATSB and CASA on any improvements.

A CASA spokesperson said that, having reviewed the preliminary reports, the regulator remains of the view that none of the incidents indicates an immediate safety risk. CASA said it is also undertaking a safety assurance review of whether underlying operational or system issues could affect safety.

Qantas, through its head of operational safety, Captain Mark Cameron, said it remains confident in Australia's network of safety controls and is working with Airservices, the ATSB and the wider industry on air traffic control operations at Sydney.

What the reports do not settle

Several points remain open. The ATSB has not said what caused any of the four events, and it has not said whether staffing contributed to any of them. Two of the six Sydney investigations have no published preliminary report. The final reports are some months away. Until then, the preliminary reports establish what happened and the conditions that applied at the time. They do not establish why it happened.

For travellers the practical effect so far has been indirect. Mitchell told reporters that the lingering effects of the pandemic recovery have shown up at times as delays and other stressors in the system, according to ABC. Whether any operating restriction follows depends on the final reports, the CASA review and the panel's work.

Sources

  • Australian Transport Safety Bureau, "ATSB releases Sydney Airport preliminary reports", 30 September 2026
  • ABC News, "Sydney Airport runway conflict in July one of Australia's most severe, safety investigator says", 30 September 2026
  • Australian Flying, "Independent panel to oversee Sydney air traffic control", 30 September 2026
Share:

Comments

Leave a comment