PPRuNe Forums - View Single Post - Accident Near Mangalore Airport - Possibly 2 Aircraft down
Old 10th Mar 2020, 10:46
  #404 (permalink)  
Lead Balloon
 
Join Date: Nov 2001
Location: Australia/India
Posts: 5,307
Received 426 Likes on 213 Posts
Originally Posted by Mr Approach
The report from OAR on Avalon highlights so many anomalies within Australian airspace that this post could be nautical miles in length, for one, the ridiculous RA3 status of restricted airspace around the tin pot little airfield at Point Cook. This place has a terrifying 68,000 movements per year, I do not know how they cope, but keeping those pesky Australian citizens outside of the airspace must help. Perhaps Bankstown and Moorabbin should make similar submissions to CASA OAR.

However sticking to the point, at no stage does CASA OAR recommend Class C airspace. Airservices, on the other hand operates the airspace as if it was Class C, in my view this is because the people running Melbourne ATC Centre (where all the senior management is located) have little-to-zero knowledge about how efficiently airspace can be run by Tower controllers.
Point 1 - CASA OAR asks Airservices (the should word) to propose an airspace plan without Class E airspace. (Which CASA OAR itself recommended some years ago)
Point 2 - CASA OAR recommends that the E airspace become Class D (not C) this would still allow the VFR operations causing the problems, but enable the tower controllers to position that VFR traffic out of the way of arriving and departing IFR traffic.
Point 3 - CASA OAR recommends that Avalon Tower manages the Class D airspace with the use of the Tower Situational Awareness Display (TSAD). This is a perfectly functional display of airborne traffic (and ground if ADS-B is incorporated) which is not able to be used for separation purely because Airservices chooses to install it that way. The system only needs some minor modifications to make it comply with ICAO Annex 10, something it has done with the Essendon installation.
It is Airservices in Melbourne that I believe wants to operate the airspace as Class C. Mainly because that fits in with the uneducated views of the radar-orientated managers at that facility. And unfortunately, as identified by Lead Balloon above, the managers that run CASA OAR (not the staff in the branch) do not want CASA to be responsible for airspace changes. They prefer to simply "approve" whatever Airservices or Defence tell them they want. It is better named the Office of Airspace Rubber-Stamping (OARS)
C’mon, Mr A: The move of OAR into CASA has resulted in airspace designation being on the basis of frank and fearless independent analysis!

What fascinates (and depresses) me most is that the airspace designation system is now so busted that the people involved no longer comprehend what they are revealing in the documents they produce. It’s like the colour-coded sports grants spreadsheet that was emailed and amended so many times spanning the point at which the election was called and the caretaker period commenced. The people involved are now so disconnected from any standards of propriety that they no longer see or worry about the inappropriateness of what they are recording in writing.

So the end result will be that the airspace arrangements in the vicinity of Avalon will be changed to suit the wishes of some Airservices and CASA bureaucrats (having been originally changed to suit a political purpose that may or may not have been justified on objective risk and cost bases), in response to a “Change Proposal” from Airservices. Great. Just great.
Lead Balloon is offline