Loss of separation at FL350 near Grafton - Two E190 aircraft.
Thread Starter
Loss of separation at FL350 near Grafton - Two E190 aircraft.
An interesting occurrence. Reports elsewhere say 400' was the least vertical separation reached.
https://www.atsb.gov.au/publications...rt/ao-2023-039
https://www.atsb.gov.au/publications...rt/ao-2023-039
The following users liked this post:
When you live....
I'm curious to know what happens in these TRA sectors - do the all the conflict alarms get turned off, screens switch off etc? I'd be surprised if there is no-one looking at them - but just not enough (qualified) people to provide the service. The airport that most recently started all of this - Darwin - clearly had some staff on duty through the nights - just not enough.
So for this incident, I wonder if it is possible someone noticed the impending problem - or an alarm went off - and that caused the instruction to go out - even though they weren't technically controlling the airspace?
So for this incident, I wonder if it is possible someone noticed the impending problem - or an alarm went off - and that caused the instruction to go out - even though they weren't technically controlling the airspace?
I'm curious to know what happens in these TRA sectors - do the all the conflict alarms get turned off, screens switch off etc? I'd be surprised if there is no-one looking at them - but just not enough (qualified) people to provide the service. The airport that most recently started all of this - Darwin - clearly had some staff on duty through the nights - just not enough.
So for this incident, I wonder if it is possible someone noticed the impending problem - or an alarm went off - and that caused the instruction to go out - even though they weren't technically controlling the airspace?
So for this incident, I wonder if it is possible someone noticed the impending problem - or an alarm went off - and that caused the instruction to go out - even though they weren't technically controlling the airspace?
As post # 3 & post #4 explained it wasn't tra/tiba so it's not relevant.
ATSB states it was "Loss of separation assurance". That is not "Loss of separation" so not sure what your other sources are talking about.
Aiservices definition: "Loss of Separation Assurance (LOSA) is when there has not been a clear application of a separation standard"
ICAO is slightly different, and in my opinon, much clearer "Loss of separation assurance: An occurrence where separation has been maintained but has not been planned, actioned or monitored appropriately.
So the incident must have involved unplanned maintenance of separation - I imagine that would be an alternative definition of TIBA!
Aiservices definition: "Loss of Separation Assurance (LOSA) is when there has not been a clear application of a separation standard"
ICAO is slightly different, and in my opinon, much clearer "Loss of separation assurance: An occurrence where separation has been maintained but has not been planned, actioned or monitored appropriately.
So the incident must have involved unplanned maintenance of separation - I imagine that would be an alternative definition of TIBA!
I'm curious to know what happens in these TRA sectors - do the all the conflict alarms get turned off, screens switch off etc? I'd be surprised if there is no-one looking at them - but just not enough (qualified) people to provide the service. The airport that most recently started all of this - Darwin - clearly had some staff on duty through the nights - just not enough.
So for this incident, I wonder if it is possible someone noticed the impending problem - or an alarm went off - and that caused the instruction to go out - even though they weren't technically controlling the airspace?
So for this incident, I wonder if it is possible someone noticed the impending problem - or an alarm went off - and that caused the instruction to go out - even though they weren't technically controlling the airspace?
Thread drift, but the question about alarms is important, especially when the APP/DEP function isn't staffed and whether other Units assuming responsibility e.g. Cairns Tower, Mackay Tower or an enroute group has the same alarms, different alarms or no alarms.
The following users liked this post:
I'd say there was no "Loss of Separation" as the aircraft did not breach the standards, due to the actions of the controller in recognizing and resolving the conflict prior to that happening. I guess that is why it's a loss of "assurance" only and the investigation will be why the aircraft were put into a "potential" conflict in the first place. Both the AsA and ICAO definitions cover that.
Wonder what the workload was on the said controller at the time. Or let me rephrase, how many peoples job was the controller doing at the given time?
Reminds me of Velocity calling centre the other night. After about 5 attempts they finally got someone. The controller sounded like he was doing about 3 peoples job.
Reminds me of Velocity calling centre the other night. After about 5 attempts they finally got someone. The controller sounded like he was doing about 3 peoples job.