PPRuNe Forums - View Single Post - Separation issue involving Boeing 737, VH-VXH, and Airbus A320, VH-VGV, near Darwin
Old 11th Apr 2023, 01:33
  #36 (permalink)  
parishiltons
 
Join Date: May 2008
Location: N/A
Posts: 165
Received 3 Likes on 3 Posts
Originally Posted by 43Inches
Lets just say that the QF used the RUSKA Six Departure RWY 11 and the Jestar was inbound on the VEGPU Seven arrival RWY 29 there is NO traffic separation provided by this SID/STAR. The tracks crossover between ITTSA- SARRE inbound and PAGSO-VABLI outbound whats more the departure is restricted to not above 6000 prior to VABLI while the arrival has to be below 8000 after VEGPU, further condensing the traffic into similar airspace considering the arrival is on a constant descent from VEGPU then it would probably pass very close to the departure climbing from 3000 to 6000 ft. These SID/STARs would never be used in actual combination without ATC restrictions. There is nothing on either SID/STAR that prevents the arrival and departure aircraft from being at the same altitude when transiting those tracks.

Hence these SID/STARs should not be used OCTA as pilots do not know what SID/STARs should be used in particular combinations. This is why controllers talk about runway configurations, it is referring to what is being used for arrival and departure paths and determines what SIDs/STARs will be used.

It is obvious that the RWY 29 RUSKA has a not below crossover to allow separation with inbounds to RWY 29. However OCTA an aircraft can choose to operate any runway it wants to, there is no runway configuration in place, so therefor the SID/STAR patterns are not going to ensure traffic separation.

Now what is the answer here, well first of all it needs to be understood when a SID/STAR will ensure separation, nothing in the documentation states that the RUSKA 11 and VEGPU 29 should not be used simultaneously. Remembering that a quick look has the departing aircraft turning at 900ft so it should be quickly out of the way of arrivals if they haven't started the ILS yet, but no, the conflict point is a number of miles from departure approaching the en-route phase. So an aircraft that is miles away suddenly becomes a conflict. None of this is saying that is what happened here, but it highlights how using opposite direction SID/STAR is not a good idea.
There's almost never any segregation or separation by design in RRO! But if they were using the same runway the SID/STAR design does provide segregation/separation. And the aeroplane does not know whether or not an ATC service is available - it will fly what it is programmed to do regardless of the airspace status.
parishiltons is offline