(Regulars please change the category as you see fit)
I would like to start off by thanking IFATC Lee 3440 and the approach controller at the time for dealing with the very busy YSSY airspace. I was surprised, however, that tower was unaware on two occasions that collisions were imminent. I have never experienced such a situation on the Expert server before with qualified ATC online.
I am making a topic regarding this issue as I want to reach out to the controller and hear responses from the community. Maybe controllers should be looking at airport charts before opening ATC? I feel they should be more prepared for hundreds of aircraft to swarm.
@Mavic and I had flown 2 hours from Townsville Airport (YBTL), north of Sydney. Upon arrival to the YSSY airspace, we were dealt with by approach. One thing I noticed was that commercial jets were taking off from GA-only airports nearby, which is quite unrealistic. These aircraft then proceeded to clog up the airspace, and priority was not provided to larger aircraft, nor aircraft that had flown in from destinations further away. As you will soon learn, priority was not provided to aircraft landing either. Another thing, runway 07 is rarely used in conjunction to 34L, which was occurring at the time and making things even more confusing for ATC and incoming/outgoing traffic.
I was switched over to tower once nearing the ILS triangle, and was cleared to land on runway 34R which is not capable of dealing with an A380 - when quite clearly, “Super” was in my callsign (this runway is usually only used by 767s at largest). I realise I should have been clearer about the runway I was intending to land on when I communicated to ATC. After being cleared to land on 34L, I moved forward at a normal speed which gave ATC enough time to deal with potential hazards. However, 1.5nm away from the threshold, “Qantas 11” in another A380 was cleared to take off on runway 34L. I initiated a go-around once I saw the A380 commence its takeoff roll, and ATC issued a go-around command. I thought this was perfectly fine and gave ATC benefit of the doubt by going in for a second attempt at landing as mistakes can happen. Just to let you know, at this time, an aircraft was lined up ready to take off on runway 07, and many aircraft in the queue for that runway were requesting takeoff out of order (which again, should not be happening).
After going around and making a stable approach towards 34L for the second time (after @Mavic had landed), I was cleared to land. On short final to the runway, what I think was a KLM 737 was cleared for takeoff on runway 07. Out of the 50 times I have flown out of Sydney Airport, I’m fairly sure runways 16R/34L and 07/25 have been connected every single time!? I told ATC twice I was on short final after hearing this (keep in mind I had been cleared minutes before), just to warn them that they should not be clearing an aircraft to take off on RWY 07 while an aircraft is about to touch down on 34L. I started a steep go-around regardless, and sure enough the 737 passed beneath my aircraft as I neared the runway intersection. I feel a cancel takeoff command was necessary for the departing aircraft, and over this period I was still not issued a go-around request by ATC. By this point I was fed up and quit my session.
Thanks for your concern and making it this far through my topic, hopefully this won’t happen again or at least not to this extent.
Please see the screenshots below for reference. They should be in order of time.