Connect with us

NEWS

Sydney Airport Close Calls Follow a Cleared Airspace Overhaul

After CASA cleared training for the 9 July airspace switch, ATSB opened six Sydney Airport ground-conflict files in 30 days, including one accident.

Published

on

The Australian Transport Safety Bureau opened two more Sydney Airport taxiing probes on 26 August, taking the ground-conflict files since 27 July to six. Investigators classed both new events as incidents, saying flight and ground crews reacted in time and that key safety defences stayed in place.

The cluster began 18 days after a basin-wide airspace switch for Western Sydney International. CASA had already told the ATSB that Airservices Australia’s training for that switch was appropriate.

Six Ground Conflicts in 30 Days at Kingsford Smith

The ATSB’s 26 August notice added two new taxiing conflict investigations to four files already open at Australia’s busiest airport. The bureau said it has not treated the latest pair as near collisions. Crews and tug crews stopped the aircraft.

On 16 August a Virgin 737 that had landed on runway 16 Left was taxiing north on taxiway B when a Qantas 737 vacating 16 Right at B8 came into the same sequence. Air traffic control told the Virgin crew to give way. That instruction was not read back, and the tower did not catch the miss. The Qantas crew saw the Virgin jet from the right, used normal braking, and sorted the order by radio.

On the morning of 25 August, incomplete traffic information went to a Jetstar Airbus A320 before pushback. A Bombardier Dash 8 was taxiing behind it. The pushback crew spotted the conflict, stopped, and took the A320 back to the gate.

Date Flights What ATSB recorded File
27 July, 08:14 QantasLink Dash 8 QLK424D (Canberra) and Qantas 737 QF124 (Queenstown) 737 cleared to cross runway 34 Left during the Dash 8 landing roll; 737 stopped after the holding point AO-2026-086
9 August, 07:20 Jetstar A320 JQ402 (Gold Coast) and Qatar 777 A7-BEU under tow Both stopped abruptly on crossing taxiways; one Jetstar cabin crew member seriously hurt AO-2026-087, classed as an accident
9 August, about 10:00 Virgin 737 VA555 (Perth) and Qantas 737 QF728 (Ayers Rock) Virgin rejected take-off on 34 Left after the Qantas jet, also reporting an ATC clearance, began to cross from taxiway Lima AO-2026-090
16 August Virgin 737 and Qantas 737 Give-way call not read back; Qantas crew stopped with normal braking AO-2026-093
18 August, 08:09 Qantas A321 QF405 (Melbourne) and Qantas 737 QF589 (from Gold Coast) Conflicting turn clearances onto taxiway Lima; A321 crew stopped and let the 737 pass AO-2026-091
25 August Jetstar A320 and a Dash 8 Incomplete traffic information before pushback; tug crew stopped and returned to the gate AO-2026-092

The 18 August Qantas pair is the event that first went out as a “fourth close call.” A Qantas A321, VH-OGA, was taxiing south on taxiway Charlie toward 34 Left with a clearance to turn right onto Lima. A Qantas 737, VH-VXL, was westbound on Lima with a clearance to turn right at Bravo. The A321 crew saw the 737 from the left and stopped while it went ahead. The ATSB said there was no immediate risk of collision and that the A321 braked normally.

Some early write-ups swapped the destinations. The investigation page lists QF405 to Melbourne and QF589 in from the Gold Coast. Qantas said both aircraft had been cleared by air traffic control and that it would support the inquiry.

CASA Cleared Training Before the July 9 Switch

The timing sits against a redesign that went live on 9 July so Western Sydney International (Nancy-Bird Walton) could plug into the same basin as Kingsford Smith, Bankstown and Richmond. CASA’s public briefing now states that the Sydney Basin airspace changes now in effect create four neighbouring control zones, including new Class C airspace around the western airport from the surface to 1,500 ft.

Infrastructure Minister Catherine King had already authorised preliminary paths in June 2025 after more than 50 in-person sessions and more than 8,400 submissions. Her department later pointed to new flight paths for Sydney taking effect on 9 July, with Kingsford Smith’s tower joined by a Digital Aerodrome Service: 25 cameras feeding a remote centre at Eastern Creek, the first of its kind in Australia.

Airservices told a pre-implementation webinar the western project alone was delivering 73 new or amended instrument arrivals and departures, plus about 45 low-level routes and about 24 high-level routes. The AIRAC date itself slipped from 11 June to 9 July after extra safety work with CASA.

What went live on 9 July:

  • Western Sydney Class C: A control zone from the surface to 1,500 ft, then stepped controlled airspace up to 18,000 ft, with no brick tower on the field.
  • Kingsford Smith boundaries: The Class C control zone around the existing airport changed shape so the two major fields could be separated.
  • Remote cameras: Twenty-five high-definition cameras send the western airfield picture to controllers at Eastern Creek.
  • A delayed chart date: The industry chart cycle moved from 11 June to 9 July after CASA-supported testing.
  • A staged airport: Cargo was scheduled from late July; passenger services are due in October.

CASA approved the Airspace Change Proposal in late November 2025, with post-implementation monitoring written into the conditions. That monitoring is now running in the same weeks as the Kingsford Smith ground files.

Thirty Minutes on the Simulator, Then Go-Live

On 20 August the ATSB published a confidential report, RA2026-00087, from an experienced controller. It had been lodged on 29 May, six weeks before the switch. Airservices answered on 18 June. CASA added its own reply. The Independent and Insurance Journal, working from a related ATSB disclosure, also reported a Civil Air survey of more than 50 Sydney controllers in which most voiced “grave concerns” about the volume of material to learn before 9 July, and a comparison with controller warnings in Washington before the January 2025 midair collision at Reagan National.

The published REPCON is blunt about the training model.

ATC training is rushed and inconsistent, with minimal simulation and reliance on home learning. This is the biggest and most complex airspace change the Sydney Basin has ever seen and some controllers are receiving only 30 minutes simulator time on particular runway modes.

Experienced air traffic controller, ATSB confidential report RA2026-00087

The same reporter said procedures were still being designed with only weeks to go, that sign-off used “dot point” competencies rather than full endorsements, and that training covered “ops normal” work, not bad weather or aircraft that could not meet STAR requirements. Experienced staff, the report said, would be asked to train new people within six weeks of go-live, and some shifts would have a combined experience of no more than three months. Floor walkers were acknowledged. They were not treated as a substitute for the missing hours.

Airservices answered the rushed and inconsistent ATC training claim by pointing at a split inside the Sydney operation. A review, it said, found only minor change for some groups. The heavy lift sat with Departures West, the sector that would own the new airport’s airspace, and that group received the most targeted training. A pause on training new controllers after 9 July was planned so current staff could consolidate before on-the-job instructors took pupils. Extra senior staff would watch from a non-controlling seat.

CASA’s paragraph was shorter. “CASA is satisfied that Airservices Australia has implemented an appropriate training program to support the introduction of Western Sydney International Airport airspace and associated air traffic services,” the regulator wrote. It said procedures had been amended, the design process and SME engagement were adequate, and Manual of Air Traffic Services arrangements complied. Oversight would continue through the post-implementation review.

That sign-off is the decision now meeting a month of Kingsford Smith taxiway and runway files. ATSB has not said the warning and the files share a cause. It has said it will look for common factors.

How the August 9 Pair Became an Accident File

The event that does not fit the “no immediate risk” language is the 07:20 taxiway clash on 9 August. Jetstar A320 VH-VQJ, operating JQ402 to the Gold Coast, was taxiing for departure. Qatar Airways Boeing 777-300ER A7-BEU was on a tug, empty of passengers. The A320 crew saw the 777 close on a crossing taxiway. Both aircraft stopped hard. A cabin crew member on the A320 was seriously injured. ATSB classed the occurrence as an accident, investigation AO-2026-087, with completion aimed at the first quarter of 2027.

That file is already past first interviews. Investigators have spoken to flight crew, ground crew and engineers, pulled flight-recorder and surveillance data, and started on tug procedures and training records. Still to come are CCTV, more crew interviews, air traffic control interviews, and a look at how safety-critical decisions were made that morning.

About two and a half hours later, Virgin Australia VA555, 737 VH-IJQ bound for Perth, was cleared for a full-length take-off on 34 Left. As the crew added thrust they saw Qantas QF728, 737 VH-XZH bound for Ayers Rock, start to cross ahead from taxiway Lima. The Qantas crew said they too had an ATC clearance to cross. Virgin reduced thrust and stopped on the runway. The tower cancelled the take-off clearance. Once the Qantas jet was clear, Virgin was sent again. Independent reporting put the stop about 1 km short of the other aircraft. ATSB’s own summary does not give that distance. It does classify the event as a runway incursion and rejected take-off, file AO-2026-090.

Early posts about the Jetstar morning described a restricted tower window between 6am and 8am. ATSB has not put that restriction in the accident summary. What the bureau has put on the record is a serious injury, an empty widebody on a tug, and a narrowbody that had to stop so sharply a crew member was hurt. That is the one file in the cluster already labelled an accident.

The Tower Was Already Short of Controllers

Civil Air president Scott Nugent has spent the Australian winter saying the roster, not the new western procedures on their own, is the daily problem in the Kingsford Smith tower. He has been careful, in at least one interview, to separate staffing comments from the open ATSB files.

Sydney tower supply:

  • New endorsements: Airservices has said eight new Sydney tower controllers were certified in 18 months, with six more in training and 15 expected to start training by the end of 2027.
  • National pipeline: The provider said it certified 91 controller trainees in 2025, while 39 others withdrew or failed, and that it had hired 91 controllers over a year against a target of 85.
  • Overtime: Records obtained by The Australian, covering 17 Sydney-based controllers, showed eight with more than 200 hours of overtime in 12 months and only two with none.
  • Time to qualify: Training a controller takes about 18 months to two years. Nugent has said roughly 2,000 applicants can yield about 15 hires, and Airservices has said about 2 per cent pass the first online hurdle.

“There’s just not enough air traffic controllers at Sydney Airport,” Nugent told the Sydney Morning Herald. He has described rosters that lean on overtime, including stretches of 10 shifts on and one day off, and has accused Airservices of blaming sick leave when vacant lines were already on the sheet. In early July, after a disrupted day, he said two unplanned absences were “the straw that broke the camel’s back” because the tower had started nine people short.

Airservices has said it is recruiting, including internationally qualified controllers who still have to pass Sydney’s checks, and that it has put a new simulator in the city. A rostering change due in early September is meant to put people on call so a sick line does not require a scramble. Minister King said she had made her expectations clear that Airservices “must carefully manage the situation at Sydney for the rest of August.”

A short tower and a basin-wide procedure change can sit in the same month without being the same failure. The REPCON’s own split, Departures West versus the Kingsford Smith tower, is the distinction ATSB now has to test against radio tapes and ground radar.

Investigators Are Still Treating Each File Alone

The 26 August statement is the closest thing to a doctrine for the cluster. Each incident is a separate investigation. The teams are working together. Any decision to widen a file, or to combine files, waits on the evidence. Preliminary reports on the 16 August and 25 August events are due in about six to eight weeks, the same window given for the 18 August Qantas taxiway file. If a critical safety issue appears, ATSB said it will tell the parties at once.

That posture matches the language on the earlier notices. The 18 August probe exists “to understand the potential conflicting instructions to the flight crews and whether there are any contributing factors common across the other Sydney Airport incidents currently under investigation.” The 27 July runway-crossing file is still in evidence collection, with a finish aimed at the fourth quarter of 2026. The Jetstar accident is further along, in examination and analysis.

The public argument has been simpler than the files. Coverage of the Jetstar stop treated it as the scare because someone was hurt and a Gold Coast flight never left. Later ATSB notices keep returning to the same clause: no immediate risk of collision, crews reacted, defences stayed in place. Both things can be true in one month. A cabin crew member can be seriously injured on a Tuesday morning, and a Qantas A321 can brake normally at an intersection nine days later, and investigators can still be asking whether the clearances that put metal in the same place have a common source.

Airservices reported the 18 August taxiway event itself. Virgin and Qantas, which also owns Jetstar, have all said they will support the inquiries. No airline has been named as the cause. No controller has been named. ATSB does not assign blame in these reports; it looks for factors that can be fixed.

Western Sydney Passenger Flights Are Due in October

Cargo was meant to start at the western airport in late July. Passenger flights are still marked for October. The 9 July airspace change was the enabling step, not the opening day, and CASA’s post-implementation review is the formal place where design complaints, including the general-aviation pocket between Bankstown and Camden described in the REPCON, are supposed to be reopened.

Until those passenger banks arrive, the pressure that can be measured is at Kingsford Smith: six ATSB ground files since 27 July, one already an accident, a confidential training warning that CASA answered in June, and a tower that the controllers’ union says cannot fill its base roster without overtime. Preliminary reports on the newest taxiway files are due in about six to eight weeks, which puts them in October, in the same window as the first scheduled passengers at the airport the airspace was rebuilt to serve.

Continue Reading
Click to comment

Leave a Reply

Your email address will not be published. Required fields are marked *

Trending