REPCON number
RA2023-00137
Date reported
Published date
Mode
Affected operation/industry
Concern subject type
Reporter's deidentified concern

Multiple reporters have approached the ATSB with a safety concern regarding the proposal to split the Sydney Traffic Control Unit (TCU). Airservices Australia (AsA) plan to move the Sydney TCU services from Sydney to Melbourne in 2026. The reporters advise that the current proposal is for the Sydney TCU to be split as an interim measure with Departures being controlled from Melbourne and Approach, Flow and Director Control remaining in Sydney.

One reporter queries how a split of the Sydney TCU unit can be effectively and safely managed in times of high traffic, weather events and abnormal situations (engine failures, minimum fuel, medivac upgrades, airspace infringements and go-arounds) when the Traffic Manager only has half of the operational picture, and with extended communication times between Sydney and Melbourne coordinating. If the controller cannot hear what the other half of the room is doing, then they cannot respond instantly to help resolve the problem, therefore compromising safety.

An experienced controller states, 'The airspace over the largest city in Australia and busiest primary airport in the southern hemisphere will be unmanageable. The segregated airspace is reliant on many airspace releases and non-voice coordination practices. Standard Instrument Departure (SIDs) and Standard Instrument Arrivals (STARs) are specifically designed to cross and transit these corridors and are only possible because of the enhanced situational awareness provided by having all controllers seated adjacent to each other. It is a key component, and with half the unit removed, situational awareness will be lost'.

Another reporter provided an example of a previous proposal, whereby the seating plan was being revised at Melbourne Centre and an Approach console was to be moved nine metres away from the group. This proposal was met with outrage so much so, it had to be rearranged so they were all together. In the current proposal with the Sydney TCU split, the consoles are 900 kilometres distant.

Sydney TCU is incredibly complex and with the introduction of Western Sydney Airport at the same time, will only increase the complexity. The safe management of multiple airports in close proximity with dynamic airspace volumes depending on runway/s in use, often changing to achieve noise sharing objectives, in a location subject to frequent severe weather and abnormal operations, has only been possible with a physically cohesive unit. In addition, one reporter notes that AsA is about to completely rearrange the entire airspace and SIDs and STARs because of the Western Sydney Airport, adding to the complexity.

More than one reporter advises that Sydney TCU staff are reluctant to report their feedback to senior AsA management that the plan is highly risky, most probably unachievable and will require a significant reduction in service delivery to the Sydney basin airspace users until the TCU is reintegrated in order to manage a geographically split arrangement with any measure of risk assurance. It has been reported that the unit's technical experts are being excluded from the planning and safety management processes as they are perceived as being an adversary to the senior management's goal. The reporters collectively advise that they believe this is one of the biggest threats to aviation safety in the Sydney basin and that the proposal is not just unsafe but is dangerous. Controllers have been given 12 days to provide feedback on the proposal to split the Sydney TCU. Some reporters advise this is not sufficient time for a considered response, while others advise that feedback for previous proposals has not been considered and therefore, they are reluctant to provide feedback at all.

The reporters question the amount of consideration for this proposal and what risk management plan has been undertaken, including in the event of poor weather and abnormal situations.

Named party's response

Airservices appreciates the opportunity to respond to the concern raised in the REPCON.

We are currently early in the change process and are consulting with staff to inform our approach and considerations. The feedback in the REPCON is similar to that received through the initial consultation and will be considered as part of the change process.

A rigorous safety change management process is applied to ensure that changes that may have an impact on operational services are managed appropriately. This includes being able to demonstrate that safety has been adequately considered. This process will ensure:

  • qualified and capable safety resourcing is assigned to support the magnitude of the change
  • safety related effects and context of the change across all impacted areas of the business are determined
  • hazards are identified and associated controls implemented as part of the risk assessment and risk management activities
  • safety goals are achieved
  • sufficient evidence and argument to provide assurance that the operational safety effects of a change have been identified and will be managed in the execution of the change to an acceptably safe level
  • ongoing monitoring of the operational safety performance.

We will continue to engage with stakeholders to inform this process and the change.

Regulator's response

The REPCON and response have been reviewed. Given the early stage of the proposal, CASA expects Airservices to complete robust safety assessments and change management as per their Safety Management System. CASA will remain engaged with the proposal as it develops.

ATSB comment

The ATSB received an update and further response from Airservices on 23 February 2024:

Taking into consideration the current operating environment, Airservices undertook further employee engagement and operational analysis to validate our approach to integrate Sydney approach services into Melbourne and provide an updated plan. In early 2024, the Airservices Board endorsed a ‘single transition’ whereby Western Sydney airspace will be established in the current Sydney Eurocat environment in 2026, and all services will be integrated in Melbourne, aligning with the CMATS project timeline (targeting 2027 delivery).

We will continue to work with our team members in Sydney to ensure they are supported throughout the transition.