Aeronautical Study of Port Macquarie - Civil Aviation Safety Authority
Aeronautical Study of Port Macquarie - Civil Aviation Safety Authority
Aeronautical Study of Port Macquarie - Civil Aviation Safety Authority
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Airspace Review <strong>of</strong><br />
<strong>Port</strong> <strong>Macquarie</strong><br />
(Incorporates stakeholder comments)<br />
May 2010<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version: 1.0
Office <strong>of</strong> Airspace Regulation Page 2 <strong>of</strong> 69<br />
DOCUMENT SPONSOR: OFFICE OF AIRSPACE REGULATION<br />
PROJECT No: 08/14<br />
TRIM REF: ED10/134994<br />
FILE REF: EF10/4919<br />
Document control:<br />
Version Issue/Nature <strong>of</strong> Revision Date<br />
0.0 Report for Industry comment August 2009<br />
1.0 Incorporates stakeholder feedback November 2010<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version: 1.0
Office <strong>of</strong> Airspace Regulation Page 3 <strong>of</strong> 69<br />
1 Executive Summary<br />
The Office <strong>of</strong> Airspace Regulation (OAR 1 ) within the <strong>Civil</strong> <strong>Aviation</strong> <strong>Safety</strong> <strong>Authority</strong><br />
(CASA) commissioned Hyder Consulting (Hyder) to conduct an independent review<br />
<strong>of</strong> the airspace as defined by the area marked on <strong>Aeronautical</strong> Information<br />
Publication (AIP) charts as the <strong>Port</strong> <strong>Macquarie</strong> (PMQ) Common Traffic Advisory<br />
Frequency (Radio Required) 2 (CTAF(R)) procedural broadcast area (inclusive <strong>of</strong><br />
Taree (TRE) aerodrome), New South Wales (NSW).<br />
The review <strong>of</strong> the airspace within the PMQ CTAF(R) (hereafter referred to as PMQ<br />
CTAF) procedural broadcast area has addressed the type and frequency <strong>of</strong><br />
operations, with particular emphasis on passenger transport. The review provided<br />
recommendations to CASA to address any short-comings <strong>of</strong> current airspace<br />
architecture and <strong>of</strong> the services and facilities provided by air navigation service<br />
providers, based on identified risk factors and to increase the safety and efficiency <strong>of</strong><br />
that airspace.<br />
By identifying and engaging with stakeholders, Hyder have focused on equitable<br />
access for all airspace users with particular attention to the safety <strong>of</strong> Passenger<br />
Transport (PT).<br />
Hyder have engaged in and facilitated extensive industry consultation. Input was<br />
sought from all stakeholders including, but not limited to:<br />
�<br />
�<br />
�<br />
�<br />
�<br />
�<br />
�<br />
�<br />
�<br />
the aerodrome operator;<br />
any PT operators - that use the airspace within the scope <strong>of</strong> the review<br />
(normally only those who use the aerodrome);<br />
Emergency services - that frequent the aerodrome;<br />
Flying schools based at the aerodrome;<br />
Local aeroclubs;<br />
Charter organisations - that are based at the aerodrome or frequently use the<br />
airspace;<br />
CASA - local inspectors and safety advisors;<br />
Australian Transport <strong>Safety</strong> Bureau (ATSB) - for incident data local to the<br />
airspace; and<br />
Airservices Australia (Airservices) - for traffic movement data and where<br />
applicable feedback on level <strong>of</strong> service provided (if any).<br />
The required outcomes <strong>of</strong> the proposed review were:<br />
a. A review <strong>of</strong> the airspace within the PMQ CTAF procedural broadcast area to<br />
determine the appropriateness <strong>of</strong> the current airspace classifications and the<br />
air traffic services (ATS) provided that has reviewed access for all types <strong>of</strong><br />
airspace users and provided recommendations to CASA to address any<br />
documented short-comings <strong>of</strong> the current airspace architecture.<br />
Recommendations are supported by risk assessment evaluation and<br />
analysis consistent with Australian and New Zealand Standard (AS/NZS)<br />
4360:2004 Risk Management standard.<br />
1 A list <strong>of</strong> acronyms is in Annex A.<br />
2 From 03 June 2010, changes to <strong>Civil</strong> <strong>Aviation</strong> Regulation (CAR) 166 removed the CTAF(R) designation. As <strong>Port</strong> <strong>Macquarie</strong> is<br />
a certified aerodrome, the carriage and use <strong>of</strong> radio is required at or in its vicinity.<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 4 <strong>of</strong> 69<br />
b. A vehicle for industry consultation in relation to the appropriateness <strong>of</strong> the<br />
current airspace classifications and the ATS provided.<br />
c. A third-party, objective review <strong>of</strong> the current airspace architecture within the<br />
PMQ CTAF procedural broadcast area.<br />
The review considered the findings <strong>of</strong> the above enquiries in terms <strong>of</strong> the following<br />
key policy principles from the Australian Airspace Policy Statement 3 (AAPS) released<br />
in 2007:<br />
� <strong>Safety</strong>,<br />
� Efficiency,<br />
�<br />
�<br />
�<br />
�<br />
National security,<br />
Environmental protection,<br />
Equitable access, and<br />
Global harmonisation.<br />
This report is structured on the OAR’s Airspace Review template, detailing:<br />
a. An analysis <strong>of</strong> the current traffic levels and mix <strong>of</strong> aircraft operations within<br />
the existing airspace in relation to the level <strong>of</strong> services provided;<br />
b. Identification <strong>of</strong> any threats to the operations, focussing as a priority on the<br />
safety and protection <strong>of</strong> PT services;<br />
c. Identification <strong>of</strong> appropriate and acceptable risk mitigators to the known<br />
threats, including recommendations to reduce those risks coupled to the<br />
expected impact <strong>of</strong> any proposed improvements;<br />
d. A qualitative and quantitative risk assessment <strong>of</strong> the current airspace<br />
environment and the expected impact <strong>of</strong> any changes. The quantitative data<br />
was assessed for accuracy and consistency and analysed using CASA’s<br />
modelling tool;<br />
e. Transfer <strong>of</strong> ownership <strong>of</strong> the quantitative data to CASA in Excel spreadsheet<br />
format;<br />
f. Stakeholder consultation with the aerodrome operator, PT providers, local<br />
flying schools and training organisations, and where applicable military and<br />
emergency services, to establish and assess their opinion <strong>of</strong> the<br />
appropriateness <strong>of</strong> the current airspace classification, access issues,<br />
anticipated changes to the current traffic levels and mix <strong>of</strong> aircraft operations<br />
within the existing airspace;<br />
g. A review <strong>of</strong> extant AIP entries for applicability, inclusive <strong>of</strong> any stakeholder<br />
feedback; and<br />
h. Assurances to CASA’s OAR on the levels <strong>of</strong> airspace risk associated with<br />
the subject aerodrome’s airspace.<br />
1.1 Findings<br />
Key points in relation to the PMQ aerodrome are:<br />
�<br />
�<br />
there is generally good weather at PMQ;<br />
PMQ aerodrome would need upgrading to increase PT capacity;<br />
3<br />
The AAPS 2007 has been superseded by the AAPS 2010, however the key principles from the AAPS 2007 are still relevant to<br />
the AAPS 2010.<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 5 <strong>of</strong> 69<br />
�<br />
�<br />
�<br />
�<br />
�<br />
�<br />
an increase in General <strong>Aviation</strong> (GA) capacity is possible and likely;<br />
Runway (RWY) 22 is the preferred runway direction for PT arrivals/departures;<br />
Non-directional Radio Beacon (NDB) and Area Navigation (RNAV) Global<br />
Navigation Satellite System (GNSS) arrivals and approaches are suitable for<br />
traffic and conditions at both PMQ and TRE;<br />
the lack <strong>of</strong> full length taxiways at both RWY 03/21 at PMQ and RWY 04/22 at<br />
TRE cause aircraft to backtrack and limit airspace capacity;<br />
simultaneous use <strong>of</strong> multiple runways at PMQ is a concern; and<br />
the single CTAF frequency (118.1) covering three major aerodromes (PMQ,<br />
TRE and Kempsey (KMP)) is an operational concern leading to overtransmissions<br />
and difficulty for pilots in their ability to transmit/receive calls.<br />
In respect <strong>of</strong> the airspace it was found that:<br />
�<br />
�<br />
�<br />
�<br />
�<br />
�<br />
�<br />
�<br />
there is a problem between conflicting instrument approaches at PMQ and<br />
TRE;<br />
there is a problem <strong>of</strong> little manoeuvring room for Global Positioning System<br />
(GPS) approaches adjacent to Restricted Area (RA) R574 (formally R595)<br />
Boundary;<br />
there is a two-way route structure to Sydney (SY) but not to C<strong>of</strong>fs Harbour<br />
(CH);<br />
lack <strong>of</strong> access to Williamtown (WLM) RAs forces late descents into TRE;<br />
clearances through RAs requested due to bad weather are <strong>of</strong>ten still not<br />
available;<br />
coastal Visual Flight Rules (VFR) traffic (on area frequency) may not call on<br />
CTAF frequency. While the designated broadcast area has defined lateral<br />
limits, upper limits are pilot determined;<br />
there is a capacity issue with the CTAF frequency; and<br />
a study will be required for the Class E airspace corridor, including<br />
consideration <strong>of</strong> an appropriate lower limit (LL) suitable to the radar coverage.<br />
In respect <strong>of</strong> the local operators it was found that:<br />
�<br />
�<br />
�<br />
�<br />
there are several PT companies operating to and from Sydney (including<br />
Virgin Blue E170 jets) and one PT to and from C<strong>of</strong>fs Harbour;<br />
there is only one significant aircraft operator at PMQ aerodrome;<br />
there is no PT scheduled hub and spoke system (i.e. no scheduled PT light<br />
twins servicing outlaying areas); and<br />
there is a mix <strong>of</strong> aircraft types – from jets on straight in landing to microlights in<br />
the circuit.<br />
In respect <strong>of</strong> the validation data it was found that:<br />
�<br />
�<br />
�<br />
�<br />
Aerodrome movements (landings and take-<strong>of</strong>fs) are around 26,000 per annum;<br />
Touch and Go circuit movements (estimated by Airservices Australia<br />
(Airservices) at 30,000 per annum) are additional to the 26,000 total but cannot<br />
be verified and seem optimistic given the runway configuration. The Review<br />
Snapshot suggests a figure <strong>of</strong> 11,000 per annum;<br />
PT passenger numbers appear to be in the vicinity <strong>of</strong> 168,000 to 180,000 per<br />
annum;<br />
by comparison, BITRE data shows 167,200 passengers between PMQ and<br />
Sydney year on year to Jan 2009; and<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 6 <strong>of</strong> 69<br />
� the aerodrome operator reported growth in passenger numbers over the last<br />
few months.<br />
In respect <strong>of</strong> the traffic assessment it was found that:<br />
�<br />
�<br />
�<br />
�<br />
there is an issue <strong>of</strong> frequency congestion, and sometimes confusion, on the<br />
single large CTAF frequency;<br />
circuit area operations and arrivals into the circuit area have been reported as<br />
the highest risk area (due to volume <strong>of</strong> traffic, mix <strong>of</strong> types and pilot<br />
competencies); whereas conflict between IFR aircraft generally occurs in a<br />
lower traffic environment;<br />
some operators recommended restriction <strong>of</strong> grass RWY 10/28 to arrivals and<br />
departures and only when operationally necessary; and<br />
some operators have suggested a limitation on the number <strong>of</strong> aircraft that can<br />
safely be allowed simultaneously in the circuit area. However, it is not clear<br />
how this would be managed.<br />
It was found in respect <strong>of</strong> some points and issues that:<br />
�<br />
�<br />
�<br />
�<br />
�<br />
�<br />
radio frequency congestion occurs on the CTAF frequency;<br />
Parachute Jumping Exercises (PJE) occur on the PMQ aerodrome. Several<br />
operators indicated that it should be banned from the aerodrome. However,<br />
neither the Aerodrome Operator nor an examination <strong>of</strong> <strong>Aviation</strong> <strong>Safety</strong> Incident<br />
Reports/Electronic <strong>Safety</strong> Incident Reports (ASIR/ESIR) have reported<br />
problems;<br />
there is a lack <strong>of</strong> a parallel full length taxiway to RWY 03/21;<br />
simultaneous use <strong>of</strong> two runways occurs at PMQ;<br />
the number <strong>of</strong> aircraft in the circuit area is uncontrolled; and<br />
the proximity <strong>of</strong> RA R595 boundary is an issue for GPS approaches.<br />
Stakeholders have requested that CASA liaise with the military to review the<br />
extent <strong>of</strong> the boundary and its impact upon the existing approaches 4 .<br />
In respect <strong>of</strong> Incidents at PMQ it was found that:<br />
�<br />
�<br />
�<br />
a total <strong>of</strong> 39 incidents were filed over two years <strong>of</strong> which 10 related to airspace;<br />
and<br />
the 10 airspace incidents comprised two AIRPROX events in 2007 (which<br />
were investigated by the ATSB); two Traffic Alert and Collision Avoidance<br />
System (TCAS) Resolution Advisory (RA) events; one landing on an occupied<br />
runway; one go around; and four failures to broadcast correctly.<br />
1.2 Recommendations<br />
The report makes the following recommendations:<br />
The PMQ procedural broadcast area to remain subject to CTAF procedures.<br />
4 Defence OAR has subsequently investigated the PMQ GPS approaches in relation to the boundary <strong>of</strong> RA R574 (formally<br />
R595), and found that they are appropriately separated laterally. This issue has been raised and closed at the New South Wales<br />
(NSW) Regional Airspace User’s Advisory Committee (RAPAC). More information can be found at Annex F.<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 7 <strong>of</strong> 69<br />
�<br />
�<br />
(The OAR makes the following additional comments:<br />
o Qualitative feedback received by Hyder during compilation <strong>of</strong> the Report<br />
indicated that the level <strong>of</strong> service within the airspace <strong>of</strong> the PMQ<br />
procedural broadcast area was acceptable to most stakeholders.<br />
o The Report’s risk modelling analysis also reflected that the level <strong>of</strong> risk<br />
was within acceptable parameters. The movement data used during the<br />
modelling process was a mixture <strong>of</strong> Airservices arrival and departure<br />
movement data plus a revised figure thought to more accurately represent<br />
circuit movements. The revised circuit movement figure was based upon<br />
traffic observations made during the Report’s data gathering phase. The<br />
use <strong>of</strong> this revised figure was thought to more accurately reflect the actual<br />
circuit movements with its use for modelling purposes agreed upon after<br />
consultation with the OAR.<br />
o Since publication <strong>of</strong> the report, traffic movement data has been revised<br />
significantly by Airservices. Further modelling <strong>of</strong> the revised data by the<br />
OAR has indicated that the risk <strong>of</strong> conflict between an IFR (RPT) and VFR<br />
aircraft has reduced from the original assessment made by Hyder utilising<br />
the same modelling methodology. This <strong>of</strong>fers support to the qualitative<br />
feedback that no airspace change is required based on the existing traffic<br />
numbers and mix <strong>of</strong> operations.<br />
o Outside <strong>of</strong> the original scope <strong>of</strong> the Report and as part <strong>of</strong> its work program<br />
the OAR is carrying out a review <strong>of</strong> Australian-administered airspace in<br />
accordance with the principles <strong>of</strong> the Airspace Act 2007, guided by the<br />
AAPS. This review will include investigations into the introduction <strong>of</strong> a<br />
regional solution (including PMQ) that will assess the safety benefit <strong>of</strong>fered<br />
by the introduction <strong>of</strong> Class E airspace corridors, and the possible<br />
lowering <strong>of</strong> Class E terminal airspace. In the interim the OAR will continue<br />
to monitor traffic mix and movements at PMQ over the next 12 months.<br />
Should any feedback received or data trends suggest that the level <strong>of</strong><br />
airspace risk is approaching unacceptable, it will be acted upon by the<br />
OAR.<br />
The OAR to maintain a watch <strong>of</strong> activity at PMQ and TRE aerodromes during<br />
its bi-annual review <strong>of</strong> movement data, and, if total aircraft movements<br />
significantly increase, or after five years, whichever occurs first, an airspace<br />
review or aeronautical study should be conducted to reassess the risk to<br />
passenger transport.<br />
(The OAR makes the following additional comments - Regular monitoring<br />
and review <strong>of</strong> aircraft and passenger movement numbers, analysis <strong>of</strong> accident<br />
and incident data trends and analysis <strong>of</strong> feedback from stakeholders either by<br />
direct communication or various consultative forums, is part <strong>of</strong> the OAR’s dayto-day<br />
business. No additional action is required on this recommendation.)<br />
Suggestion for airport operator on limiting operations on the grass runway at<br />
PMQ and restricting number <strong>of</strong> simultaneous circuit aircraft, particularly at<br />
night, possibly through charging policies.<br />
(The OAR makes the following additional comments - requires further<br />
investigation by the Aerodrome Operator to establish the level <strong>of</strong> risk posed by<br />
grass runway operations.)<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 8 <strong>of</strong> 69<br />
�<br />
�<br />
CASA to further consider/investigate the safety <strong>of</strong> parachuting operations onto<br />
a secure aerodrome serviced by three PT operators and a busy GA area.<br />
(The OAR makes the following additional comments - requires further<br />
consultation between the Aerodrome Operator and parachute operators to<br />
establish the level <strong>of</strong> risk posed by parachuting operations in the vicinity <strong>of</strong><br />
PMQ.)<br />
Review the options <strong>of</strong> either splitting the CTAF frequency in a safe fashion or<br />
complete a more in-depth study for the possibility <strong>of</strong> lowering Class E airspace<br />
where radar coverage permits and/or introducing a Class E airspace corridor<br />
along the main TRE/PMQ IFR routes. Other considerations for such a study<br />
could include other means <strong>of</strong> surveillance such as Wide Area Multilateration<br />
(WAM).<br />
(The OAR makes the following additional comments - the OAR has no<br />
intention <strong>of</strong> investigating the option <strong>of</strong> splitting the CTAF procedural area<br />
however it is progressing investigation into the benefit <strong>of</strong> implementing Class E<br />
airspace to lower levels to afford greater protection to RPT operations.<br />
Additional surveillance methods such as the use <strong>of</strong> WAM will be considered, if<br />
appropriate, as part <strong>of</strong> this study.)<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 9 <strong>of</strong> 69<br />
Contents<br />
1 EXECUTIVE SUMMARY....................................................................................................................... 3<br />
2 PURPOSE ....................................................................................................................................... 10<br />
3 AERODROME AND INFRASTRUCTURE................................................................................................ 12<br />
4 AIRSPACE....................................................................................................................................... 21<br />
5 STAKEHOLDER CONSULTATION........................................................................................................ 28<br />
6 SUMMARY OF MOVEMENT DATA ...................................................................................................... 35<br />
7 SUMMARY OF INCIDENTS AND ACCIDENTS ........................................................................................ 39<br />
8 MODELLING METHODOLOGY AND RISK ASSESSMENT........................................................................ 41<br />
9 EVALUATION................................................................................................................................... 45<br />
10 CONCLUSIONS ................................................................................................................................49<br />
11 CASA FINAL COMMENT AND ACTIONS FOR PORT MACQUARIE.......................................................... 51<br />
12 REFERENCES ................................................................................................................................. 52<br />
ANNEXES: ............................................................................................................................................... 53<br />
ANNEX A – ACRONYMS ............................................................................................................................ 54<br />
ANNEX B – AUSTRALIAN AIRSPACE STRUCTURE........................................................................................ 58<br />
ANNEX C – STAKEHOLDERS ..................................................................................................................... 59<br />
ANNEX D – AERODROME OPERATOR DATA ............................................................................................... 61<br />
ANNEX E – DEFINITIONS AND EXPLANATION OF TERMS.............................................................................. 62<br />
ANNEX F – STAKEHOLDER CONSULTATION / FEEDBACK REGISTER............................................................. 65<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version: 1.0
Office <strong>of</strong> Airspace Regulation Page 10 <strong>of</strong> 69<br />
2 Purpose<br />
The purpose <strong>of</strong> this Airspace Review was to conduct a risk assessment <strong>of</strong> the<br />
airspace within the <strong>Port</strong> <strong>Macquarie</strong> (PMQ) 5 CTAF(R) 6 procedural broadcast area<br />
(inclusive <strong>of</strong> Taree (TRE) aerodrome), New South Wales (NSW). The review forms<br />
part <strong>of</strong> the <strong>of</strong>fice <strong>of</strong> Airspace Regulation (OAR) Work Program as required by the<br />
Airspace Act 2007 (Act).<br />
2.1 Scope<br />
The scope <strong>of</strong> the review includes identification and consultation with stakeholders to<br />
gather necessary data and information related to airspace issues within the<br />
PMQ CTAF(R) (hereafter referred to as PMQ CTAF) procedural broadcast area<br />
(inclusive <strong>of</strong> TRE). As a minimum this includes consultation with passenger transport<br />
(PT) operators, charter operators, flying training schools, military operators,<br />
emergency services operators and the aerodrome operator<br />
The scope <strong>of</strong> this review is not intended to examine aerodrome facilities and<br />
infrastructure issues unless any weakness or failings in these areas have a<br />
significant impact on the safety <strong>of</strong> airspace operations in the vicinity <strong>of</strong> PMQ and TRE<br />
aerodromes.<br />
2.2 Objective<br />
The objective <strong>of</strong> this Review is to examine the airspace within the PMQ CTAF<br />
procedural broadcast area (inclusive <strong>of</strong> TRE aerodrome) to determine the<br />
appropriateness <strong>of</strong> the current airspace classification. This was accomplished by:<br />
a. Analyses <strong>of</strong> current traffic levels and mix <strong>of</strong> aircraft operations within the<br />
existing airspace in relation to the level <strong>of</strong> services provided;<br />
b. Identifying any threats to the operations, focussing as a priority on the safety<br />
and protection <strong>of</strong> PT services;<br />
c. Identifying appropriate and acceptable risk mitigators to the known threats;<br />
d. Carrying out a qualitative and quantitative risk assessment <strong>of</strong> the current<br />
airspace environment and the expected impact <strong>of</strong> any changes;<br />
e. Investigating through stakeholder consultation, the appropriateness <strong>of</strong> the<br />
current airspace classification, access issues, expected changes to the<br />
current traffic levels and mix <strong>of</strong> aircraft operations within the existing<br />
airspace;<br />
f. Reviewing extant <strong>Aeronautical</strong> Information Publication (AIP) entries for<br />
applicability;<br />
g. Ensuring that the issues are passed onto the relative stakeholder group for<br />
their consideration; and<br />
h. Providing assurance to the Executive Manager OAR <strong>of</strong> the levels <strong>of</strong> airspace<br />
risk are within acceptable tolerances for PMQ aerodrome.<br />
5 A list <strong>of</strong> acronyms is in Annex A.<br />
6 From 03 June 2010, changes to <strong>Civil</strong> <strong>Aviation</strong> Regulation (CAR) 166 removed the CTAF(R) designation. As <strong>Port</strong> <strong>Macquarie</strong> is<br />
a certified aerodrome, the carriage and use <strong>of</strong> radio is required at or in its vicinity.<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version: 1.0
Office <strong>of</strong> Airspace Regulation Page 11 <strong>of</strong> 69<br />
The review considered the findings <strong>of</strong> the above enquiries in terms <strong>of</strong> safety,<br />
efficiency, national security, environmental protection and equitable access.<br />
2.3 Due Diligence<br />
The review was conducted within a due diligence framework. The work was<br />
conducted in three phases:<br />
a. The Concept and Scope phase demonstrated understanding <strong>of</strong> the subject<br />
matter and was expressed in terms <strong>of</strong>:<br />
�<br />
�<br />
�<br />
�<br />
�<br />
Airspace description;<br />
Aerodrome and Infrastructure; and<br />
Stakeholder Consultation (encouraging discussion <strong>of</strong> issues and options).<br />
b. The Identification and Analysis phase commenced with a summary <strong>of</strong><br />
incidents and accidents and application <strong>of</strong> the Airspace Risk Model (ARM)<br />
base case. The documentation included:<br />
Modelling Methodology; and<br />
Airspace Risk Assessment.<br />
c. The Evaluation phase employed a range <strong>of</strong> qualitative and quantitative risk<br />
assessment techniques and cost:benefit analyses (as required) to establish<br />
effectiveness <strong>of</strong> precautionary options. The outputs comprised:<br />
� Findings; and<br />
� Recommendations<br />
The approach was based on an understanding <strong>of</strong> CASA requirements and the Key<br />
Policy Principles behind them. Regard has been given to other recent airspace<br />
reviews including Adelaide and Maroochydore by Hyder and Ayers Rock and<br />
Bathurst internally reviewed by CASA. The approach considered relevant standards<br />
and methodologies for Stakeholder consultations, options analyses and<br />
recommendations.<br />
2.4 Overview <strong>of</strong> Australian Airspace<br />
The OAR within the <strong>Civil</strong> <strong>Aviation</strong> <strong>Safety</strong> <strong>Authority</strong> (CASA) has sole carriage <strong>of</strong> the<br />
regulation <strong>of</strong> Australian-administered airspace, in accordance with section 11 <strong>of</strong> the<br />
Act. Section 12 <strong>of</strong> the Act requires CASA to foster both the efficient use <strong>of</strong> Australianadministered<br />
airspace and equitable access to that airspace for all users. CASA must<br />
also take into account the capacity <strong>of</strong> Australian-administered airspace to<br />
accommodate changes to its use.<br />
In line with the International <strong>Civil</strong> <strong>Aviation</strong> Organization (ICAO) Annex 11 and as<br />
described in the Australian Airspace Policy Statement (AAPS), Australian airspace is<br />
classified as Class A, C, D, E and G depending on the level <strong>of</strong> service required to<br />
manage traffic safely and effectively. Class B and F are not currently used in<br />
Australia. The classification determines the category <strong>of</strong> flights permitted and the level<br />
<strong>of</strong> air traffic services (ATS) provided. Annex B provides details <strong>of</strong> the classes <strong>of</strong><br />
airspace used in Australia. Within this classification system aerodromes are either<br />
controlled (i.e. Class C or Class D) or non-controlled.<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 12 <strong>of</strong> 69<br />
3 Aerodrome and Infrastructure<br />
3.1 Background<br />
3.1.1 <strong>Port</strong> <strong>Macquarie</strong><br />
PMQ is a large town on the mid-North Coast <strong>of</strong> NSW, Australia, located<br />
about 390 kilometres (km) North <strong>of</strong> Sydney, and 570 km South <strong>of</strong> Brisbane.<br />
The town is located on the coast, at the mouth <strong>of</strong> the Hastings River. The<br />
nearest railway town is Wauchope, 19 km to the West.<br />
PMQ is a popular retirement location and tourist destination. It is known for<br />
its extensive beaches and waterways.<br />
The residential suburbs stretch to Lighthouse Beach in the South, Thrumster<br />
to the West and to the so-called "North Shore" on the North bank <strong>of</strong> the river.<br />
In the 2006 Census the wider area <strong>of</strong> the Hastings Valley had a total<br />
population <strong>of</strong> 68,429 up 9.5% from the 2001 Census.<br />
The PMQ Aerodrome is located 5 km West <strong>of</strong> the town, near the Southern<br />
bank <strong>of</strong> the Hastings River as shown in Figure 1.<br />
Figure 1 - PMQ Location<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version: 1.0
Office <strong>of</strong> Airspace Regulation Page 13 <strong>of</strong> 69<br />
PMQ has predominantly fine weather – Visual Metrological Conditions<br />
(VMC). The annual average cloud cover at PMQ (Bellevue Gardens) is just<br />
under four eights coverage and the average number <strong>of</strong> cloudy days is 114<br />
per annum (source Bureau <strong>of</strong> Meteorology (BOM):1957 – 2003). The mean<br />
0900 local time wind speed is 14 km/hr (BOM: 1957 – 2003) and the<br />
prevailing direction is South West to West. The mean 1500 local wind speed<br />
is 20.1 km/hr and the prevailing direction is North Easterly to South Easterly.<br />
PMQ can experience fog as it is close to the coast.<br />
Figure 2 presents 0900 and 1500 local Wind Roses for PMQ (Bellevue<br />
Gardens). (Note: Observed data for PMQ aerodrome started in 1995 and<br />
only mean wind speed <strong>of</strong> 12.9 km/hr is available on the BOM website).<br />
Figure 2 – 0900 and 1500 local time Wind Roses for PMQ (Bellevue Gardens)<br />
Figure 3 shows the location <strong>of</strong> the aerodrome to the west <strong>of</strong> the town <strong>of</strong><br />
PMQ.<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 14 <strong>of</strong> 69<br />
3.1.2 Taree<br />
Figure 3 – PMQ Area<br />
TRE is a city on the Mid North Coast, NSW, Australia. TRE and nearby<br />
Cundletown were settled in 1831 by William Wynter. It is 16 km from the sea<br />
coast, 317 km North <strong>of</strong> Sydney and 33 nautical miles (NM) by air to PMQ.<br />
Taree can be reached by train via the North Coast Railway, and by the<br />
Pacific Highway.<br />
TRE has predominantly fine weather (VMC). The annual average cloud cover<br />
at TRE (Robertson Street) at 0900 local is just under four eights, and the<br />
average number <strong>of</strong> cloudy days is 121 per annum (BOM - 1965 – 2006). The<br />
mean 0900 local time wind speed is 6.6 km/hr and the mean 1500 local wind<br />
speed is 20.1 km/h (1965 – 2006). The prevailing direction is not given in the<br />
BOM Weather statistics for TRE.<br />
Figure 4 shows the location <strong>of</strong> TRE aerodrome to the East <strong>of</strong> the town.<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 15 <strong>of</strong> 69<br />
Taree Aerodrome<br />
Figure 4 – TRE Area<br />
In the following sections the PMQ and TRE aerodromes and their runways<br />
and facilities are first described and then an overview <strong>of</strong> airspace architecture<br />
is given.<br />
3.2 PMQ Aerodrome<br />
PMQ is a security controlled airport.<br />
3.2.1 Runways<br />
There are two runways (RWY) at PMQ:<br />
�<br />
�<br />
RWY 03/21 sealed 1,600 metres x 30 metres; and<br />
RWY 10/28 grass runway 696 metres x 18 metres.<br />
There is Low Intensity Runway Lighting on RWY 03/21 and Illuminated<br />
windsocks. The aerodrome lighting is controlled by a Pilot Activated Lighting<br />
(PAL) system (Frequency 122.3 MegaHertz (MHz)).<br />
Figure 5 gives the aerodrome layout.<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 16 <strong>of</strong> 69<br />
3.2.2 Taxiways and Aprons<br />
Figure 5 – PMQ Aerodrome Layout<br />
Two taxiways (TWY) enter the main runway. TWY A, near the Northern end<br />
<strong>of</strong> the runway, and TWY C further South. There is no full length taxiway to<br />
RWY 03/21. Aircraft using RWY 03/21 need to enter the runway at either<br />
TWY A or TWY C and backtrack. There are taxiway sideline blue lights and<br />
apron lighting.<br />
The Apron area has 4 parking bays that can simultaneously accommodate<br />
the current types <strong>of</strong> PT aircraft regularly operating into PMQ (Embraer jet<br />
ERJ170; Dash 8-300 and 400; and Jetstream J41).<br />
There is a General <strong>Aviation</strong> (GA) area, with two aprons, located along TWY<br />
C adjacent to the grass runway. Parking on the grass for GA aircraft is also<br />
available adjacent to TWY C.<br />
3.2.3 AWIS/AFRU<br />
The following services are provided:<br />
�<br />
�<br />
Aerodrome Weather Information Service (AWIS). This is available by<br />
telephone and is also transmitted on frequency 128.45 MHz; and<br />
Aerodrome Frequency Response Unit (AFRU) (”Beep-Back”).<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 17 <strong>of</strong> 69<br />
3.2.4 Navigational Aids<br />
A Non Directional Beacon (NDB) (Frequency 395 KHz) is located South <strong>of</strong><br />
the grass runway.<br />
The closest civil radar head to PMQ is located at The Round Mountain (TRM)<br />
which is located west <strong>of</strong> C<strong>of</strong>fs Harbour. This Secondary Surveillance Radar<br />
(SSR) gives radar coverage down to approximately 3,000 feet (ft) Above<br />
Mean Sea Level (AMSL) to 2,000 ft AMSL (depending upon location) in the<br />
vicinity <strong>of</strong> PMQ.<br />
The Airservices Australia (Airservices) radar coverage diagram for TRM<br />
indicates coverage at 2,000 ft AMSL near PMQ. Refer Figure 6.<br />
The radar coverage over the PMQ/TRE CTAF procedural area could possibly<br />
permit additional radar services to be applied in this area (such as Radar<br />
services in E Class airspace with a base lower than the present<br />
8,500 ft AMSL). A more in depth study <strong>of</strong> the feasibility <strong>of</strong> suggestions such<br />
as this would need to be undertaken including specific modelling <strong>of</strong> conflict<br />
pairs.<br />
3.2.5 Landing Aids<br />
Figure 6 – Radar Coverage – PMQ at 2,000 ft<br />
There are Precision Approach Path Indicators (PAPI) on RWY 03 and<br />
RWY 21.<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 18 <strong>of</strong> 69<br />
3.2.6 Instrument Approaches<br />
PMQ has a Global Position System (GPS) arrival procedure, using the NDB,<br />
which is divided into three Sectors covering all tracks within 360 degrees.<br />
The Category C (Cat C) aircraft circling minima is 1,030 ft AMSL for the GPS<br />
Arrival procedure. Cat C aircraft are heavy turboprop and medium jet aircraft<br />
e.g. B737 and DHC-8.<br />
In addition to the GPS Arrival Procedure, PMQ has three instrument<br />
approaches for pilots to choose from:<br />
�<br />
�<br />
�<br />
�<br />
�<br />
�<br />
NDB RWY 21 approach (Cat C minima Straight In RWY 21 is<br />
770 ft AMSL);<br />
Area Navigation (RNAV) Global Navigation Satellite System (GNSS)<br />
RWY 21 approach (Cat C minima Straight In RWY 21 is 550 ft<br />
AMSL); and<br />
RNAV (GNSS) RWY 03 approach (Cat C minima Straight In RWY 03<br />
is 680 ft AMSL).<br />
3.2.7 Radio Communications/Facilities<br />
Aircraft operating at PMQ can access the following radio communication<br />
facilities:<br />
Flight Information Area (FIA) from Brisbane Centre on 120.55 MHz.<br />
Only available within the circuit area (1,000 ft AMSL);<br />
Ground communications contact Brisbane Centre on 126.6 MHz; and<br />
CTAF 118.1 MHz.<br />
3.2.8 Improvements/developments<br />
The PMQ-Hasting Council is the owner and operator <strong>of</strong> the PMQ aerodrome.<br />
The council has published a Discussion Paper (2009) regarding the PMQ<br />
airport master plan.<br />
The discussion paper (Executive Summary page 6) states that ’…in order to<br />
cater for larger jet aircraft up to B737-800 and A320 series aircraft, a<br />
significant upgrade <strong>of</strong> the main RWY 03/21 will be required, including an<br />
extension in length to 1,800 metres and an increase in pavement strength’.<br />
Two primary options are presented in the Discussion Paper: ‘either to<br />
upgrade the existing runway on its current alignment (and construct a new<br />
parallel taxiway); or to construct a new runway (1,800 m long x 30 m wide)<br />
parallel to and 101 m to the West <strong>of</strong> the existing runway (with the existing<br />
runway being converted to a parallel taxiway)’.<br />
The existing grass RWY10/28, used by light aircraft, has been identified as ‘a<br />
potential constraint to the long-term development <strong>of</strong> the airport and<br />
surrounding area’. One <strong>of</strong> the key issues for the Discussion Paper and<br />
subsequent master plan is ‘to determine whether it will be necessary to close<br />
the existing RWY 10/28 in the medium to long-term to make way for future<br />
airport development, and to determine the potential impact that this would<br />
have on general aviation stakeholders’.<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 19 <strong>of</strong> 69<br />
3.3 Taree Aerodrome<br />
TRE is a security controlled aerodrome.<br />
3.3.1 Runways<br />
�<br />
�<br />
RWY 04/22, sealed 1,504 metres x 30 metres; and<br />
RWY 12/30, grass 564 metres x 18 metres.<br />
There is Low Intensity Runway Lighting on RWY 04/22 together with an<br />
illuminated windsock. The aerodrome lighting is controlled by PAL (frequency<br />
122.4 MHz).<br />
The aerodrome layout is given below in Figure 7.<br />
3.3.2 Taxiways and Aprons<br />
Figure 7 – TRE Aerodrome Layout<br />
There is one TWY that enters the RWY 04/22 near the southern end.<br />
There is no taxiway to RWY 22. Aircraft using RWY 22 need to enter the<br />
runway at the TWY near the southern end and back track the entire length <strong>of</strong><br />
the RWY.<br />
The apron area, and TWY width are very limited in size. The apron can<br />
accommodate the current scheduled PT operation <strong>of</strong> a Regional Express<br />
SF340 aircraft. The taxiway has sideline blue lights and apron lighting.<br />
3.3.3 AWIS/AFRU<br />
The following services are provided at TRE:<br />
�<br />
�<br />
AWIS is available by telephone only; and<br />
TRE does not have AFRU.<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 20 <strong>of</strong> 69<br />
3.3.4 Navigational Aid<br />
The only navigational aid provided is a NDB (frequency 371 KHz) located<br />
near the terminal building.<br />
3.3.5 Landing Aids<br />
TRE does not have any visual landing aids (e.g. no PAPI).<br />
3.3.6 Instrument Approaches<br />
TRE has a GPS Arrival Procedure, using the NDB, which is divided into three<br />
Sectors covering all tracks within 360 degrees. The Cat C aircraft circling<br />
minima is 1,000 ft AMSL for the GPS Arrival procedure.<br />
In addition to the GPS Arrival Procedure, TRE has two instrument<br />
approaches for pilots to choose from:<br />
�<br />
�<br />
�<br />
�<br />
NDB-A approach (Cat C circling minima is 890 ft AMSL); and<br />
RNAV (GNSS) RWY 22 approach (Cat C minima Straight In RWY 22<br />
is 640 ft AMSL).<br />
3.3.7 Radio Communications/Facilities<br />
Aircraft operating at TRE can access the following radio communication<br />
facilities:<br />
Flight Information Area (FIA) from Brisbane Centre on 120.55 MHz<br />
on the ground.<br />
CTAF frequency <strong>of</strong> 118.1 MHz.<br />
3.3.8 Improvements/Developments<br />
The TRE airport is owned and operated by the Greater Taree/Manning Valley<br />
City Council. The council has published commercial development plans for<br />
aerodrome land however there is no current published airport master plan for<br />
additional runway development.<br />
The council states that it has been negotiating with State and Federal<br />
Government Agencies with a view to attracting large scale grant(s) to assist<br />
with providing the infrastructure for the development plans.<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 21 <strong>of</strong> 69<br />
4 Airspace<br />
The PMQ and TRE broadcast area is depicted on aviation charts as a large CTAF<br />
area and is classified as Class G airspace. For ease <strong>of</strong> description in this section this<br />
large CTAF broadcast area will be referred to as the “PMQ/TRE CTAF” area and<br />
each aerodrome will be referred to separately by its acronym.<br />
The airspace surrounding PMQ and TRE aerodromes is Class G airspace from the<br />
surface (SFC) to an altitude <strong>of</strong> 8,500 ft AMSL. In this location Class E airspace exists<br />
between 8,500 ft AMSL and Flight Level (FL) 180. Class A airspace exists above<br />
FL 180. 7<br />
A CTAF is essentially a broadcast procedure normally used as an air/ground/air VHF<br />
radio frequency and not an ICAO Class <strong>of</strong> airspace or a defined volume <strong>of</strong> airspace.<br />
A CTAF can be used at any landing area and not just a purpose built aerodrome. As<br />
such, it generally has no defined vertical or lateral boundary.<br />
Where aerodromes are situated close together, and have traffic patterns that are <strong>of</strong><br />
mutual interest to pilots at these aerodromes, there has <strong>of</strong>ten been a single CTAF<br />
frequency allocated to a particular area, which is marked on aeronautical charts. This<br />
single CTAF frequency allocated to a number <strong>of</strong> adjacent aerodromes is a different<br />
frequency to the Air Traffic Control (ATC) Area Frequency that is used in the wider<br />
area. The Area Frequency is not related to any particular aerodrome and it is used<br />
for pilot communications over a wide geographical area and to provide the relevant<br />
ATS services from Airservices.<br />
In the case <strong>of</strong> the PMQ/TRE CTAF area, the Area Frequency in the surrounding<br />
Class G airspace (and up to FL125) is 120.55 MHz and is provided from Brisbane<br />
Centre’s radio facility at Berrico.<br />
In addition to PMQ and TRE aerodromes all aerodromes and landing areas<br />
contained within the geographical area marked on the aeronautical charts (10 NM<br />
radius from PMQ and TRE aerodromes) have been allocated CTAF 118.1 MHz.<br />
Refer to Figure 8 below.<br />
7 Refer to Annex B for a description <strong>of</strong> Australian Airspace Structure.<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 22 <strong>of</strong> 69<br />
Figure 8 - Visual Navigation Chart (VNC) indicating the location <strong>of</strong> the PMQ/TRE CTAF<br />
and the Military Restricted Areas R587B, R583B and R595 8 .<br />
8 Airspace configuration at time <strong>of</strong> draft report. The northern section <strong>of</strong> R574 (formally R595) has been amended, however, the<br />
changes have no impact on the study.<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 23 <strong>of</strong> 69<br />
Aerodromes (AD) and other private Aircraft Landing Areas (ALA) within this large<br />
CTAF area which are marked on aeronautical charts include:<br />
�<br />
�<br />
�<br />
�<br />
�<br />
PMQ AD,<br />
Camden Haven (CMH) ALA,<br />
The Lakes (LKS) ALA,<br />
TRE AD, and<br />
Old Bar (OBR) ALA.<br />
Kempsey aerodrome (KMP) is located only 23 NM from PMQ and is not within the<br />
PMQ/TRE CTAF area boundary marked on maps. However, KMP has also been<br />
allocated the CTAF 118.1 MHz.<br />
Issues identified by stakeholders with both the PMQ/TRE CTAF area and general<br />
CTAF radio frequencies and procedures are discussed below in the Stakeholder<br />
Consultation <strong>of</strong> this review.<br />
4.1 Restricted Areas<br />
The PMQ/TRE CTAF has three military RAs nearby that are relevant to operations<br />
within the subject CTAF procedural area. A number <strong>of</strong> issues were raised in the<br />
consultation with stakeholders but, apparently, have never been brought forward at<br />
any other forums.<br />
4.1.1 R587B<br />
RA R587B is located above the PMQ/TRE CTAF. This area is from FL125 to<br />
FL600 and is activated by a Notice to Airmen (NOTAM). This area is<br />
designated for military flying training. Hours <strong>of</strong> activity are published by<br />
NOTAM.<br />
When R587B is active, aircraft inbound to the aerodromes in the PMQ/TRE<br />
CTAF need to reach a level under FL125 prior to reaching the southern<br />
boundary <strong>of</strong> R587B if they cannot get a clearance. As this RA boundary is<br />
located only approximately 10 NM from TRE aerodrome, aircraft need to<br />
commence descent early in order to get under this airspace prior to the<br />
boundary.<br />
4.1.2 R583B<br />
RA R583B is located immediately adjacent to the South <strong>of</strong> the PMQ/TRE<br />
CTAF area and is from surface (SFC) to 10,000 ft AMSL. This area is used<br />
for military flying training and is activated by NOTAM. It was reported as<br />
frequently active.<br />
Aircraft inbound to TRE or PMQ from Sydney are <strong>of</strong>ten restricted on descent<br />
until clear <strong>of</strong> R538B. This restriction on descent, in turn prevents the PT<br />
aircraft from conducting a straight in approach to RWY 04 at TRE.<br />
Consequently the PT aircraft may choose to conduct a GNSS Approach to<br />
RWY 22 at TRE. However, aircraft tracking for the TRE RWY 22 approach<br />
can come into conflict with other aircraft using the PMQ RWY 03 GNSS<br />
approach.<br />
4.1.3 R574 (formally R595)<br />
RA R574 is located to the East <strong>of</strong> the PMQ/TRE CTAF. This area is SFC to<br />
FL600 and is declared for military intercept training. It is activated by<br />
NOTAM. It was reported as frequently active. The Western boundary <strong>of</strong> R574<br />
is located approximately (under) 5 NM from the intercept positions <strong>of</strong>:<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 24 <strong>of</strong> 69<br />
�<br />
�<br />
�<br />
�<br />
�<br />
�<br />
PMQ Runway 03 RNAV points <strong>of</strong> PMQSA, and PMQSH<br />
PMQ Runway 21 RNAV points PMQNG and PMQNH<br />
TRE Runway 22 RNAV point TRENG<br />
There have been five restricted area incursions <strong>of</strong> R595 since January 2007.<br />
These incidents have involved scheduled PT aircraft conducting RNAV<br />
approaches.<br />
It is recognised that the RNAV approaches have been designed in<br />
accordance with international PANS-OPS instrument design criteria and<br />
comply with the CASR Part 173 Manual <strong>of</strong> Standards (MOS).<br />
4.2 Aircraft tracking<br />
4.2.1 IFR tracks<br />
The busiest IFR route through the PMQ/TRE CTAF area used by PT aircraft<br />
is the route between Sydney and PMQ. The next busiest routes for<br />
scheduled PT aircraft through the PMQ/TRE CTAF area are the PMQ – C<strong>of</strong>fs<br />
Harbour – Brisbane route, and the Sydney to TRE route.<br />
Virgin Blue Airlines and QantasLink operate the route between<br />
Sydney and PMQ;<br />
Brindabella Airlines operate the route between PMQ and Brisbane,<br />
via C<strong>of</strong>fs Harbour; and<br />
Regional Express Airlines operate the route between Sydney and<br />
TRE.<br />
IFR aircraft proceeding from Sydney to PMQ, or TRE, may flight plan to track<br />
from Williamtown (WLM) direct to TRE or PMQ provided the WLM Restricted<br />
areas are not active. Refer Figure 9 below for tracks W603 and W223.<br />
If, however, the WLM Restricted areas are active then IFR aircraft must plan<br />
from WLM via W182 to the turning point <strong>of</strong> NICLA thence PMQ (W106) or<br />
TRE (W223). NICLA is a position bearing 237 degrees magnetic from TRE at<br />
28 NM (W223).<br />
IFR aircraft departing from PMQ or TRE to Sydney, must flight plan to track<br />
respectively via the turning point <strong>of</strong> “SORTI” thence Singleton (SGT) via<br />
W214 and Sydney via W180. “SORTI” is a position bearing 233 degrees<br />
magnetic PMQ at 56 NM (W768).<br />
This route structure (inbound via NICLA or WLM and outbound via SORTI)<br />
produces a race track route structure to/from Sydney that assists with the<br />
segregation <strong>of</strong> aircraft, both inside and outside controlled airspace.<br />
IFR aircraft proceeding between PMQ and C<strong>of</strong>fs Harbour may flight plan to<br />
track on the direct route between these aerodromes. The current traffic levels<br />
on this route are such that a two way route structure has not been required at<br />
this point.<br />
Other IFR tracking within the PMQ/TRE CTAF area is not as regular or as<br />
predictable as the PT routes. Other IFR tracking involves a mixture <strong>of</strong> IFR<br />
training and travel flights between the navigation aids at PMQ, TRE, KMP<br />
and other aerodromes further afield such as C<strong>of</strong>fs Harbour and Western<br />
locations such as Armidale and Tamworth.<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 25 <strong>of</strong> 69<br />
W214<br />
W180<br />
W608<br />
SORTI<br />
W768<br />
NICLA<br />
Figure 9 - En route Low Chart depicting various air routes relevant to the PMQ/TRE CTAF<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0<br />
W182<br />
W603<br />
W106<br />
W223<br />
W223
Office <strong>of</strong> Airspace Regulation Page 26 <strong>of</strong> 69<br />
4.2.2 Instrument Approach confliction<br />
Figure 10 depicts the confliction between instrument approaches at PMQ and<br />
TRE.<br />
Figure 10 - Approximation <strong>of</strong> the TRE & PMQ RNAV Approaches<br />
Aircraft using the PMQ RNAV RWY 03 approach and other aircraft using the<br />
TRE RNAV RWY 22 approach can come into lateral conflict with each other.<br />
Stakeholders reported that these two instrument approaches are sometimes<br />
required to be used at the same time period during scheduled PT arrivals at<br />
both TRE and PMQ.<br />
IFR aircraft conducting these instrument approaches receive a traffic<br />
information service from ATS on other IFR traffic and any known VFR aircraft<br />
in the area.<br />
The pilots are also required to broadcast their positions and intentions to<br />
allow other aircraft in the CTAF area to determine appropriate separation,<br />
particularly during these instrument approaches. In this regard it is important<br />
that TRE and PMQ are on the same CTAF frequency.<br />
4.2.3 VFR tracks<br />
In addition to aircraft operating within the circuit areas <strong>of</strong> aerodromes within<br />
the PMQ/TRE CTAF area, VFR tracking to and from these aerodromes is<br />
essentially in directions as required by the pilot. When flying training was<br />
previously occurring at high levels at PMQ, VFR flights were <strong>of</strong>ten tracking<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 27 <strong>of</strong> 69<br />
to/from the local flying training areas that are not specifically published on<br />
aviation charts. Some VFR circuit area training has also been conducted at<br />
KMP in order to reduce the amount <strong>of</strong> traffic in the circuit at PMQ.<br />
GA flights at PMQ include local joy flights (<strong>of</strong>ten coastal); travel flights to<br />
other destinations; training flights; parachuting activity; ultra light and microlight<br />
flights (fitted with radio). A float plane also conducts VFR operations<br />
from a location nearby on the river. There is also a significant amount <strong>of</strong> VFR<br />
coastal traffic overflying the vicinity <strong>of</strong> the aerodrome, tracking North to South<br />
and vice versa at various altitudes, generally below 5,000 ft AMSL.<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 28 <strong>of</strong> 69<br />
5 Stakeholder Consultation<br />
The review set out to consult widely and engage with stakeholders on identification <strong>of</strong><br />
issues. The review team sought input from a number <strong>of</strong> stakeholders who operate in<br />
and around PMQ and TRE aerodromes. Generative stakeholder interviews were<br />
conducted during June 2009.<br />
Comments were sought and received from the following organisations:<br />
�<br />
�<br />
�<br />
�<br />
�<br />
�<br />
�<br />
�<br />
�<br />
�<br />
Resident Operators:<br />
Johnston <strong>Aviation</strong><br />
Hastings District Flying Club<br />
Pacific Coast Flying School and Seaplane Flights<br />
Coastal Skydivers <strong>Port</strong> <strong>Macquarie</strong><br />
Arena International <strong>Aviation</strong> College<br />
Non Resident Operators:<br />
Qantas Link<br />
Brindabella Airlines<br />
Virgin Blue Airlines<br />
Regional Express Airlines (REX)<br />
Royal Flying Doctor Service (RFDS) Eastern Section<br />
At the time <strong>of</strong> this review, PMQ’s previous largest local operator (Coast Jet) was no<br />
longer trading. Coast Jet had operated a large fleet <strong>of</strong> Cessna 152, 172, and Piper<br />
aircraft. The company has been replaced by Arena International <strong>Aviation</strong> College<br />
which intends to establish a significant flying school for foreign students at the airport<br />
and initially operate a fleet <strong>of</strong> C172s. Johnston <strong>Aviation</strong> is now the largest operator at<br />
PMQ and was previously part <strong>of</strong> Coast Jet.<br />
5.1 CASA<br />
The review team consulted internally within the various functional areas <strong>of</strong> CASA,<br />
including Flying Operations Inspectors (FOI) and <strong>Aviation</strong> <strong>Safety</strong> Advisors (ASA).<br />
CASA employs ASAs throughout Australia as an integral mechanism for providing<br />
safety promotion and educational material to the various industry segments. An ASA<br />
had visited PMQ to liaise with local operators, and discuss airspace issues. FOI<br />
feedback to the review team on airspace issues at PMQ was limited to noting that an<br />
Airservices enhanced UNICOM trial had recently ended there.<br />
5.2 Aerodrome Operator<br />
PMQ Airport is owned and operated by the PMQ-Hastings Council. The Review team<br />
interviewed the airport General Manager concerning current operations and airport<br />
development plans.<br />
The TRE Airport is owned and operated by the Greater TRE/Manning Valley City<br />
Council. The Airport General Manager was invited to contribute to the airspace<br />
review.<br />
5.3 Aerodrome Users<br />
5.3.1 Passenger Transport<br />
Passenger Transport (PT) includes regular public transport and all<br />
non-freight-only charter operations.<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 29 <strong>of</strong> 69<br />
The scheduled PT at PMQ and TRE include QantasLink, Brindabella Airlines,<br />
Virgin Blue Airlines and Regional Express Airlines (REX). The review team<br />
conducted generative interviews with the following:<br />
�<br />
�<br />
�<br />
�<br />
QantasLink – Deputy Chief Pilot and Regulatory Affairs Manager;<br />
Brindabella Airlines – Chief Pilot and PMQ Base pilot;<br />
Virgin Blue Airlines – Flight Operations Manager and Embraer pilot;<br />
and<br />
Regional Express Airlines – Group <strong>Safety</strong> Manager and Flight<br />
Operations Manager.<br />
In addition to interviewing pilots in management positions within the airlines,<br />
a questionnaire produced by the review team was distributed to many line<br />
pilots that regularly operate into the PMQ/TRE CTAF in order to obtain their<br />
views on various airspace matters. At the time <strong>of</strong> writing no questionnaire<br />
feedback had been received from Brindabella Airlines.<br />
Non-Resident PT operators operate the following aircraft into PMQ and TRE:<br />
QantasLink<br />
� QantasLink operate DHC-8-315 (50 seats) and DHC-8-Q400 (74 seats)<br />
on scheduled flights to and from PMQ and Sydney. Between<br />
September and May, scheduled flights are also operated to Lord Howe<br />
Island.<br />
Virgin Blue<br />
� Virgin Blue operate Embraer ERJ170-100 (78 seats) with two return<br />
flights daily between Sydney and PMQ.<br />
Brindabella Airlines<br />
� Brindabella Airlines operate Jetstream J41 (30 seats) and Metro 111<br />
(18 seats) with two return flights daily between PMQ and C<strong>of</strong>fs Harbour;<br />
and two return flights daily between PMQ and Brisbane.<br />
Regional Express (REX) Airlines<br />
� REX operate SAAB SF340 (34 and 36 seat models) with three flights<br />
per day between TRE and Sydney and three flights daily between TRE<br />
and Grafton.<br />
5.3.2 Other <strong>Aviation</strong> Activities<br />
Consultation conducted with the other operators who operate Charter and<br />
Aerial Work operations at PMQ that involve passengers included the<br />
following resident operators and their aircraft fleet:<br />
Johnston <strong>Aviation</strong><br />
� Johnston <strong>Aviation</strong> operates twin engine aircraft and 10 single engine<br />
aircraft namely C152; C172; C182; BE58; and PA31.<br />
Hastings District Flying Club<br />
� Hastings District Flying Club operate C172; Recreational <strong>Aviation</strong><br />
Australia (RA-Aus) Foxbat and Eur<strong>of</strong>ox.<br />
Pacific Coast Flying School and Seaplane flights<br />
� Pacific Coast Flying School and Seaplane Flights operate a C182<br />
Floatplane from the Hastings River.<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 30 <strong>of</strong> 69<br />
Coastal Skydivers <strong>Port</strong> <strong>Macquarie</strong><br />
� Coastal Skydivers <strong>Port</strong> <strong>Macquarie</strong> conduct parachute jumping<br />
exercises (PJE) from a C206 at PMQ aerodrome. They carry out 200 to<br />
300 drops per year and time releases to avoid PT operations.<br />
5.4 Military<br />
Consultation was conducted with Defence OAR (Defence members within the OAR)<br />
and also with the Detachment Commander 44 Wing Detachment Williamtown<br />
(RAAF).<br />
5.5 Airservices<br />
Consultation was conducted with the nominated point <strong>of</strong> contact for Airservices (the<br />
Air Navigation Service Provider – ANSP). Receipt <strong>of</strong> various Airservices reports and<br />
data is gratefully acknowledged.<br />
Airservices had conducted a UNICOM (Universal Communications Frequency) trial at<br />
PMQ from October 2008 until the trail was terminated on 31 March 2009.<br />
Staff from Airservices’ <strong>Safety</strong> Management Group had conducted a Site visit to PMQ<br />
in February 2009 as part <strong>of</strong> their Airspace Risk Assessment Process (ARAP). Their<br />
ARAP determined that the traffic levels at the time <strong>of</strong> the site visit did not indicate the<br />
need for an enhanced traffic service beyond a CTAF.<br />
5.6 Points and Issues<br />
The various points and issues (concerns) that were raised by stakeholders were wide<br />
ranging. They have been categorised under some common headings <strong>of</strong>: Aerodrome,<br />
Facilities and Equipment, Airspace and Procedures, and Concerns/General<br />
Feedback.<br />
5.6.1 Aerodrome<br />
The following points were raised in respect <strong>of</strong> the PMQ and TRE<br />
aerodromes:<br />
�<br />
�<br />
The lack <strong>of</strong> full length taxiway creates backtrack problems on<br />
RWY 03 at PMQ and RWY 22 at TRE. Backtracking requires other<br />
aircraft to extend down wind adding to aircraft in the circuit which in<br />
turn adds to frequency congestion in the CTAF during peak hours.<br />
The lack <strong>of</strong> visual slope guidance (PAPI) at night at TRE.<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 31 <strong>of</strong> 69<br />
5.6.2 Facilities and Equipment<br />
The following points were raised in respect <strong>of</strong> the PMQ and TRE facilities<br />
and equipment:<br />
�<br />
�<br />
�<br />
�<br />
�<br />
�<br />
�<br />
�<br />
�<br />
Several PT operators stated that “Everybody should have a<br />
transponder on” i.e. they are <strong>of</strong> the opinion that the PMQ/TRE CTAF<br />
area should be a DTA.<br />
PT Operators stated that they believed that TCAS provides essential<br />
situational awareness, in addition to radio broadcasts. This enhanced<br />
situational awareness is only available to TCAS equipped aircraft,<br />
normally larger aircraft (greater than 30 seats) and is reliant on other<br />
aircraft being equipped with serviceable transponders.<br />
5.6.3 Airspace and Procedures<br />
The following points were raised in respect <strong>of</strong> the PMQ and TRE airspace<br />
and procedures:<br />
PMQ CTAF – without Unicom – was reported as working<br />
satisfactorily at the moment, but this may change if there is a<br />
significant increase in flying training or upgrading for larger jet<br />
operations.<br />
The proximity <strong>of</strong> R574 (formally R595) boundary is an issue. It was<br />
requested that the military review and try to move the boundary<br />
slightly.<br />
(OAR makes the following additional comments - The NSW<br />
Regional Airspace Procedural Advisory Committee (RAPAC)<br />
discussed the issue at the June 2010 meeting. Defence advised the<br />
meeting that the existing volume <strong>of</strong> the area is completely required<br />
for operations. The Restricted Area boundary aligns with other<br />
Restricted Areas. By moving the R574 boundary, all the other<br />
Restricted Area boundaries would also need to be moved. The<br />
Instrument Approach meets PANS-OPS standards and is clear <strong>of</strong><br />
R574. RAPAC formed the view that with five VCAs within the past<br />
three years, generally <strong>of</strong> PT origin, it was seen as an issue to be<br />
addressed through the respective company's <strong>Safety</strong> Management<br />
Systems procedures in the short term.)<br />
5.6.4 Concerns/General Feedback<br />
The following concerns were raised in respect <strong>of</strong> the PMQ and TRE<br />
aerodromes and/or airspace:<br />
there is radio frequency congestion on the CTAF;<br />
PJE occur on the PMQ aerodrome. Several operators indicated that<br />
it should be banned from the aerodrome. Examination <strong>of</strong> <strong>Aviation</strong><br />
<strong>Safety</strong> Incident Reports/Electronic <strong>Safety</strong> Incident Reports<br />
(ASIR/ESIR) has reported no problems. The Aerodrome Operator<br />
reported an incident where a parachutists failed to comply with<br />
dropping procedures when PT aircraft movements in progress;<br />
there is a lack <strong>of</strong> a parallel full length taxiway to PMQ RWY 03/21;<br />
simultaneous use <strong>of</strong> two runways occurs at PMQ;<br />
the number <strong>of</strong> aircraft in the circuit area is uncontrolled;<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 32 <strong>of</strong> 69<br />
�<br />
�<br />
�<br />
�<br />
�<br />
�<br />
the proximity <strong>of</strong> R574 (formally R595) boundary is an issue for GPS<br />
approaches. Stakeholders have requested that the military review<br />
and try to move the boundary slightly to accommodate the<br />
approaches;<br />
clearance through military restricted areas should be available for PT<br />
aircraft when essential due to severe weather conditions (other than<br />
having to declare an emergency);<br />
(The OAR makes the following additional comments - Expedition<br />
<strong>of</strong> clearances through Restricted Airspace is already managed by the<br />
airspace controlling authority in accordance with procedures detailed<br />
within the Manual <strong>of</strong> Air Traffic Services (MATS). These procedures<br />
take into account diversion requests through Restricted Areas due to<br />
severe weather.)<br />
the LSALT (Lowest Safe Altitude) within 25 NM <strong>of</strong> PMQ is<br />
5,300 ft AMSL, and 4,500 ft AMSL within 25 NM <strong>of</strong> TRE;<br />
the possibility <strong>of</strong> a Class E airspace corridor, using BN Radar, (Lower<br />
Limit <strong>of</strong> 4,500 ft AMSL), would provide IFR to IFR separation within<br />
this area; directed traffic information-radar information service (DTI-<br />
RIS) about known VFR aircraft to IFR; and a VFR traffic (on request)<br />
service to VFR aircraft above the Class E base;<br />
Class E airspace LL (base) 4,500 ft AMSL would still not provide<br />
additional services in the CTAF procedural area or at the<br />
aerodromes. However it would provide additional services from the<br />
current Class E airspace base <strong>of</strong> 8,500 ft AMSL (an additional<br />
4,000 ft AMSL <strong>of</strong> protection); and<br />
if a Class E airspace corridor was considered it could possibly be<br />
confined to an arc that encompasses the standard arrival and<br />
departures tracks to/from PMQ/TRE (i.e. in via NICLA and out via<br />
SORTI).<br />
5.7 PMQ/TRE CTAF Frequency Congestion<br />
The VHF allocated to the PMQ CTAF is 118.1 MHz. This frequency is also allocated<br />
to operations at TRE aerodrome located South <strong>of</strong> PMQ and also allocated to<br />
operations at KMP aerodrome which is located 23 NM North West <strong>of</strong> PMQ.<br />
There have been numerous reports by pilots <strong>of</strong> frequency congestion occurring on<br />
the CTAF 118.1 MHz.<br />
Aircraft on the ground at any one <strong>of</strong> the three aerodromes in this location (PMQ, TRE<br />
or KMP) are generally unable to hear other aircraft transmitting on the ground at any<br />
<strong>of</strong> the other two aerodromes and consequently can unintentionally broadcast on the<br />
frequency at the same time as another aircraft is broadcasting. A pilot may be<br />
unaware that the transmission just made was over transmitted by another aircraft.<br />
It was also reported that pilots operating at PMQ, TRE or KMP need to determine<br />
which broadcasts are pertinent to the aerodrome that they are operating at. The<br />
irrelevant traffic can be discounted only if the location is contained in the broadcast.<br />
The use <strong>of</strong> both TRE and PMQ at similar times gives rise to considerations <strong>of</strong><br />
splitting the CTAF frequency (118.1 MHz) between the ports. However, this would<br />
create problems with situational awareness <strong>of</strong> possible conflictions between the two<br />
ports.<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 33 <strong>of</strong> 69<br />
The NSW RAPAC meeting held at Bankstown on June 25th 2009 discussed the<br />
PMQ CTAF area frequency. The conclusion or desired outcome was that the main<br />
users <strong>of</strong> the airspace would not like to see a change to the frequencies that would<br />
result in TRE or PMQ being on separate frequencies.<br />
5.8 PMQ Survey <strong>of</strong> Airline Pilots<br />
A survey was conducted amongst a sample <strong>of</strong> PT pilots that operate regularly into<br />
PMQ. Seven airline pilots responded. The survey sought their views on the current<br />
airspace architecture; provision <strong>of</strong> ATS; air traffic density and complexity; radio<br />
communications, navigation aids; weather conditions; aerodrome facilities and any<br />
perceived safety issues in the PMQ/TRE CTAF.<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 34 <strong>of</strong> 69<br />
The following results were obtained:<br />
a. Airspace and ATS<br />
Most PT respondents did not believe that the current CTAF procedures provided<br />
suitable protection for their operations. They showed a preference for a UNICOM, or<br />
a CA/GRO, or a Control Tower service. An explanation <strong>of</strong> terminology can be found<br />
in Annex E.<br />
b. Traffic<br />
The PT respondents indicated that the traffic volume and/or complexity is <strong>of</strong>ten high<br />
or complex and that was normal for this CTAF during peak times.<br />
c. Radio<br />
Respondents very strongly reported that it is <strong>of</strong>ten difficult to get calls in on the radio<br />
due to frequency congestion, and there is <strong>of</strong>ten traffic that does not appear to be on<br />
the radio frequency.<br />
d. Navigation Aids and weather conditions<br />
The pilots agreed that the radio navigation aids currently provided are sufficient for a<br />
safe and efficient operation. Some pilots commented that the current PT levels would<br />
warrant a VHF Omni-directional Radio Range (VOR)/Distance Measuring Equipment<br />
(DME); and that the lack <strong>of</strong> visual slope guidance and the state <strong>of</strong> the runway at TRE<br />
is a concern. They also commented that a VOR at TRE would be useful, plus a<br />
RNAV approach from the South.<br />
Respondents agreed that the weather conditions are <strong>of</strong>ten such that instrument<br />
approaches are required at both aerodromes and there is other IFR traffic also<br />
arriving or departing at the same time. They also agreed that there can be a lot <strong>of</strong><br />
VFR traffic operating below the cloud base, providing little time for visual acquisition.<br />
e. Aerodrome facilities<br />
The pilots expressed concerns about the physical condition <strong>of</strong> the runways and<br />
taxiways, particularly at TRE. It is recommended that CASA follow this up with further<br />
consultation to establish the level <strong>of</strong> dissatisfaction<br />
f. <strong>Safety</strong><br />
The pilots expressed concerns regarding CTAF procedures. They indicated that they<br />
believed that the current airspace design only provided the minimum safety standard,<br />
and that this area should have improved air traffic services due to the traffic numbers<br />
and mix <strong>of</strong> operations.<br />
5.9 Stakeholder comments and feedback<br />
Stakeholder comments in response to the draft Airspace Review can be found in<br />
Annex F.<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 35 <strong>of</strong> 69<br />
6 Summary <strong>of</strong> Movement Data<br />
Movement data was sourced from Airservices, the Airport operator and a Review<br />
snapshot.<br />
6.1 Airservices<br />
The OAR supplied Airservices Data Validation Report and Trigger Criteria Snapshot<br />
for the 12 months reported to February 2009:<br />
�<br />
�<br />
�<br />
�<br />
Arrivals – 13,324. Departures – 13,392 = 26,716. Circuits – 29,800;<br />
Total movements as per count – 56,516 per annum (i.e. 155 per day);<br />
Air Transport Movements – 9,571;<br />
VFR Movements Factor = 2; and, from their Trigger Criteria Snapshot<br />
o Movements 56,516 (155 per day),<br />
o Air Transport 9,571 (26 per day), and<br />
o Passenger counts 212,666 (582 per day).<br />
In addition, the Airservices ‘Aircraft Types By <strong>Port</strong>’ data was analysed as to the type<br />
<strong>of</strong> aircraft that frequented PMQ as per the ARM categories.<br />
6.2 Airport operator<br />
The airport operator supplied movement data for May 2008 to April 2009 listed<br />
13,108 landings. Doubling this figure to represent both take-<strong>of</strong>fs and landings results<br />
in a total movement figure <strong>of</strong> 26,216 per annum. This figure is 500 less than the<br />
Airservices figure <strong>of</strong> 26,716 stated above.<br />
The monthly distribution is shown in figure 11 with a linear line <strong>of</strong> best fit.<br />
Figure 11 – Movements (Take/<strong>of</strong>fs(T/O) and Landings) from Aerodrome Operator Records<br />
April 09 (Total movements 26,216 per annum). Linear line <strong>of</strong> best fit.<br />
The peak <strong>of</strong> movements in September 2008 may be an artefact <strong>of</strong> the UNICOM trial<br />
commencing and capturing more data, and the downward trend after September<br />
2008 may be a result from Coast Jet which ceased trading in January 2009.<br />
6.3 Review Snapshot<br />
A review snapshot was taken during daylight hours on Monday 8 th June 2009<br />
(Queens Birthday long weekend). 61 movements were observed and another 10<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 36 <strong>of</strong> 69<br />
added for PT operations morning and night, totalling 71 movements for that day. This<br />
is consistent with total movements <strong>of</strong> approximately 26,000 per annum, but is only<br />
half <strong>of</strong> the total movements inclusive <strong>of</strong> estimated circuits reported by Airservices<br />
above.<br />
During this day there were six cases observed <strong>of</strong> VFR aircraft overflying below<br />
5,000 ft AMSL. Some tracked coastal others via overhead.<br />
During the snapshot there was one Ultralight conducting circuits. 30 movements from<br />
the Ultralight and another 30 movements from traffic arriving and departing were<br />
observed. If this is indicative <strong>of</strong> normal circuit activity then it would equate to<br />
approximately 11,000 circuit movements per annum. This number <strong>of</strong> circuits would<br />
need to triple to reach the 30,000 predicted by Airservices data. For ARM modelling<br />
purposes a figure <strong>of</strong> 11,000 was adopted for the circuit. Added to the previous<br />
Airservices figure <strong>of</strong> 26,716 gives a revised total movement figure <strong>of</strong> 37,716.<br />
6.4 Passengers<br />
Airservices Data Validation Report for the 12 months to February 2009 reported<br />
passenger aircraft arrivals – 16,247. Passenger aircraft departures – 16,871<br />
Total passenger count labelled by Airservices Data Validation Report as ‘DOTARS<br />
Passenger count’ was 179,548 for 12 months to February 2009.<br />
Airport operator supplied information indicated around 168,000 airline passengers in<br />
2008.<br />
6.5 Traffic assessment<br />
This section presents information on traffic patterns and traffic density and<br />
complexity.<br />
6.5.1 Traffic Patterns<br />
The IFR pattern to and from Sydney is a race track pattern; in from the South<br />
and out to the West. The traffic pattern to the North is direct to and from<br />
C<strong>of</strong>fs Harbour.<br />
The complexity for IFR traffic patterns in the CTAF would occur when there<br />
are a number <strong>of</strong> instrument approaches to be conducted around the same<br />
time at both PMQ and TRE.<br />
The current PT schedules at PMQ are designed to produce a gap between<br />
the competing companies and their route schedules (arrivals and<br />
departures). However, conflicts in scheduling still occur due to weather<br />
and/or other reasons.<br />
The VFR traffic patterns are predominately up and down the coast and travel<br />
flights to destinations North, South and West. This VFR traffic pattern could<br />
rapidly change with an increase in local area flying training activity.<br />
The greatest number <strong>of</strong> confliction pairs seemed to occur within the circuit<br />
area and joining the circuit area (IFR to VFR, and VFR to VFR).<br />
The Airservices provided movement data presented in Figure 12 indicated a<br />
peak time, in February, <strong>of</strong> around 0900 hrs local. This timing seems to be<br />
consistent with our snapshot where between 0700 and 0945 hrs local, three<br />
PT flights arrived and departed (QantasLink; Virgin Blue; and Brindabella)<br />
and a number <strong>of</strong> GA aircraft departed.<br />
However the predicted peak numbers at around 100/hour seems high. Single<br />
runway operations and backtrack required produced a circuit time around<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 37 <strong>of</strong> 69<br />
6 minutes for a GA aircraft; so the maximum number <strong>of</strong> circuits is 10 per<br />
hour. At this point in time it seems reasonable to predict a maximum <strong>of</strong><br />
around 20 movements per hour with the single runway and perhaps 30 per<br />
hour if both runways were operational.<br />
Figure 12 - PMQ Airservices movements (arrivals by hour for Feb 2009<br />
6.5.2 Traffic density and complexity<br />
Although at times during the day it was reported that the traffic density in the<br />
circuit area can get high, this level <strong>of</strong> traffic does not always persist<br />
throughout the day, unlike at some other locations that are currently serviced<br />
by a Tower or a CA/GRO.<br />
Also the complexity <strong>of</strong> the traffic mix and patterns is not as high as some<br />
other locations that may involve issues such as high terrain; high lowest safe<br />
altitudes; frequent poor weather conditions; limited navigation aids; lack <strong>of</strong><br />
visual features; noise abatement or other local procedural issues.<br />
The two real challenges reported by pilots here were circuit area conflictions,<br />
particularly when the circuit is busy with arrivals and departures, and the<br />
issue <strong>of</strong> frequency congestion on the single CTAF frequency. Traffic in the<br />
circuit at PMQ can hear traffic at TRE and it was reported by pilots that they<br />
need to sort out in their minds who is local and who is not.<br />
When the grass runway at PMQ is serviceable there have been instances <strong>of</strong><br />
multiple aircraft conducting circuits on both runways (grass runway and main<br />
sealed runway) simultaneously, creating a confliction where the circuit<br />
patterns cross. This has been perceived as too risky and there have been<br />
instances where a pilot has had to request everybody make a full stop<br />
landing and sort it out on the ground.<br />
It was recommended by several operators that the aerodrome operator place<br />
restrictions on the grass runway so that it is only available for take<strong>of</strong>f or<br />
landings (no circuit training) and only when weather conditions prohibit the<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 38 <strong>of</strong> 69<br />
use <strong>of</strong> the main runway. Aircraft can land on the grass strip whenever they<br />
want to, including during PT arrivals. This leads to conflicts between the two<br />
different circuit patterns (e.g. downwind on the main RWY crosses final<br />
approach (or departure leg) on the cross runway. This remains a concern.<br />
Also other operators have suggested that the aerodrome operator place a<br />
limit on the number <strong>of</strong> aircraft that can conduct circuits simultaneously,<br />
particularly at night.<br />
6.5.3 Estimated Traffic Mix<br />
The data provided by the Aerodrome operator comprised individual landing<br />
call-signs recorded over a 12 month period. For commercial and privacy<br />
reasons, the details are not reported here. However, the summary<br />
information provides a valuable understanding <strong>of</strong> the operations at PMQ<br />
aerodrome.<br />
In line with the ARM, four categories are considered:<br />
VFR including gliders and helicopters, or simply (V),<br />
IFR(L), IFR Light – up to 9 passengers (L),<br />
IFR(M), IFR Medium – 10 to 38 passengers (M), and<br />
IFR(H), IFR High – more than 38 passengers (H).<br />
2,810 IFR(H) movements were evident from the Airservices ‘Aircraft Types<br />
By <strong>Port</strong>’ data with 138,400 passengers (assuming 70% occupancy) and an,<br />
average <strong>of</strong> 49 passengers per aircraft.<br />
The IFR(M) group comprised 2,164 movements with 29,760 passenger<br />
passengers at an average <strong>of</strong> 14 per aircraft.<br />
The data did not readily distinguish between IFR(L) and VFR, the flight mode<br />
depending on the pilot and the weather rather than the aircraft type.<br />
However, for the purposes <strong>of</strong> this review, a boundary was drawn at 6 seats<br />
for fixed wing aircraft.<br />
Thus, the IFR(L) group comprised 4,819 movements with 18,270 passengers<br />
at four average per aircraft plus 50% <strong>of</strong> 11,000 circuits = 10,319.<br />
The VFR group, including helicopters made 16,923 movements with 2.3<br />
persons average occupancy plus 50% <strong>of</strong> 11,000 circuits = 22,423.<br />
Total movements for consideration in the ARM therefore amount to<br />
37,716 per annum.<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 39 <strong>of</strong> 69<br />
7 Summary <strong>of</strong> Incidents and Accidents<br />
There were 32 ASIRs filed relating to PMQ aerodrome or airspace in the vicinity <strong>of</strong><br />
PMQ, during the period 1 January 2007 to December 2008. In addition there were<br />
also 7 ESIRs filed between 1 March 2008 and 28 February 2009. These are<br />
discussed below.<br />
7.1 Electronic <strong>Safety</strong> Incident Reports (ESIRs)<br />
ESIRs are an electronically submitted air safety occurrence report, which forms part<br />
<strong>of</strong> the ESIR system, maintained by Airservices, which permits systemic analysis and<br />
trend monitoring.<br />
Airservices had filed 7 ESIRs in the 12 months to February 2009. Only 1 <strong>of</strong> these<br />
ESIRs related to occurrences in the PMQ CTAF area (TCAS RA) and it was a<br />
duplicate <strong>of</strong> the ASIR on 8 August 2008.<br />
7.2 <strong>Aviation</strong> <strong>Safety</strong> Incident Reports<br />
All accidents and incidents involving Australian registered aircraft, or foreign aircraft<br />
in Australian airspace must be reported to the Australian Transport <strong>Safety</strong><br />
Bureau (ATSB). The ATSB maintains its own database, the <strong>Safety</strong> Investigation<br />
Information Management System (SIIMS), in which all reported occurrences are<br />
logged, assessed, classified and recorded. The information contained within SIIMS is<br />
dynamic and subject to change based on additional and/or updated data. Each<br />
individual report is known as an <strong>Aviation</strong> <strong>Safety</strong> Incident Report (ASIR) and for<br />
identification purposes is allocated its own serial number.<br />
The 32 ASIRs regarding PMQ that were filed over a 2 year period (January 2007 –<br />
December 2008) included the following type <strong>of</strong> occurrences which are shown in<br />
Figure 13.<br />
Figure 13 - ASIR by Category/Type <strong>of</strong> Occurrence<br />
From the total <strong>of</strong> 32 ASIRs filed, there were 12 occurrences that were considered to<br />
have involved aircraft operating in or around the PMQ/TRE CTAF area.<br />
7.3 Issues and Options Arising from Incident and Accident Data<br />
The PMQ incident data (ASIRs, ESIRs, operator records) examined from<br />
January 2007 until April 2009 indicates an incident tends to occur on average<br />
approximately every 2 to 3 months (12 airspace incidents in 28 months).<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 40 <strong>of</strong> 69<br />
An examination <strong>of</strong> the 12 airspace/aerodrome type incidents suggests a number <strong>of</strong><br />
recurring themes, or possible contributory factors, such as:<br />
�<br />
�<br />
�<br />
�<br />
�<br />
�<br />
�<br />
�<br />
�<br />
�<br />
�<br />
�<br />
frequency congestion on the CTAF,<br />
the need for active listening on the CTAF,<br />
the need for vigilant visual look out,<br />
the need to understand the AFRU response,<br />
reliance on TCAS,<br />
inaccurate and inadequate communications by pilots.<br />
It is suggested that many <strong>of</strong> the issues above are generic in nature to operations in<br />
non-controlled airspace and the only location specific issues at PMQ are:<br />
the lack <strong>of</strong> a taxiway to RWY 03/21, causing additional runway occupancy time<br />
and subsequent circuit area problems;<br />
the occasional simultaneous use <strong>of</strong> several intersecting runways (03/21 and<br />
grass 10/28); and<br />
frequency congestion on the CTAF 118.1.<br />
The incident data, and the anecdotal evidence from pilots, also suggests that the<br />
majority <strong>of</strong> conflict pairs occur either in the circuit area; joining the circuit; or by<br />
aircraft over flying or in the vicinity <strong>of</strong> the aerodrome. There is little evidence from the<br />
incident records to date that there is a problem occurring in the volume <strong>of</strong> airspace<br />
further out from the circuit area.<br />
7.4 Aerodrome operator records<br />
The PMQ airport operator’s internal safety records support the ATSB data as most <strong>of</strong><br />
the occurrences detailed were reported by pilots to the ATSB and an ASIR was filed.<br />
However there were three events during 2007 and 2008 listed in the operator’s<br />
records that do not seem (or require) to have a matching ASIR report:<br />
11/8/2007. Parachutists failed to comply with dropping procedures when PT<br />
aircraft movements in progress,<br />
18/6/2008. A Eurobat was on base when a turbo prop established on final<br />
requested by radio to land in front. The turbo prop performed a missed<br />
approach passing over the top <strong>of</strong> the Eurobat on the runway,<br />
26/8/2008. Go around. A Metro called 20 NM final for a straight in approach.<br />
A Cessna 150 made a short approach in front <strong>of</strong> the Metro and occupied the<br />
runway (causing a go-around).<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 41 <strong>of</strong> 69<br />
8 Modelling Methodology and Risk Assessment<br />
8.1 Methodology Outline<br />
CASA has developed ‘acceptable risk’ criteria with regards to the risk <strong>of</strong> midair<br />
conflicts within regional aerodrome terminal areas. The ARM, developed by CASA in<br />
1996, is focused on a non-radar controlled terminal area model and no significant<br />
changes have been made since its development and presentation to the Review <strong>of</strong><br />
the General Concept <strong>of</strong> Separation Panel (RGCSP), now the Separation and<br />
Airspace <strong>Safety</strong> Panel (SASP) <strong>of</strong> ICAO.<br />
The OAR uses the ARM, a cause:consequence model, to calculate the probability <strong>of</strong><br />
midair collisions (MAC) in various airspace environments. The ARM and a FN-curve<br />
were developed by CASA and are the primary modelling tools utilised by the OAR.<br />
This method is used to calculate benefits in terms <strong>of</strong> fatalities avoided by<br />
implementing safety measures. The ARM presumes that there is a ‘Potential Conflict<br />
Pair’, i.e. a pair <strong>of</strong> aircraft whose manoeuvres are such that if no intervening action is<br />
taken, the aircraft will reach a point where it will be too late to take evasive action and<br />
chance becomes the determining factor in whether the aircraft collide or not. This is<br />
known as the Loss <strong>of</strong> Control (LoC) point in this review.<br />
The ARM model is based on the Linear Criterion concept which stipulates that the<br />
frequency <strong>of</strong> an accident should be inversely proportional to its severity, i.e. an<br />
accident involving one or more fatality may happen ten times as <strong>of</strong>ten as an accident<br />
involving ten or more fatalities.<br />
Using the ARM, the existing scenario was modelled for PMQ aerodrome – CTAF(R)<br />
with an AFRU. Collision pairs for this review were calculated applying the CASA<br />
regression formula. It was established that this formula over estimates collision pairs<br />
therefore it is reasonable to assume that the real risk figures calculated for this<br />
review could be lower.<br />
8.2 Airspace Risk Assessment<br />
8.2.1 Assumptions<br />
The ARM is configured for various aviation operational environments. The<br />
relevant case for PMQ is uncontrolled non-radar, Class G terminal area<br />
operating as CTAF(R). For the purpose <strong>of</strong> estimating conflict pairs, it has a<br />
radius <strong>of</strong> 15 NM and extends to 5,000 ft above ground level (AGL).<br />
8.2.2 Conflict Pairs<br />
The conflict pairs were grouped in proportion to traffic and in addition, the<br />
following assumptions were made:<br />
�<br />
�<br />
�<br />
Factor up like pairs by 1.5.<br />
Factor down unlike pairs by 0.67.<br />
IFR-IFR pairs are 80% in Visual Meteorological Conditions (VMC) and<br />
20% In Instrument Meteorological Conditions (IMC).<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 42 <strong>of</strong> 69<br />
8.3 Results<br />
The ARM considered the following protection barriers:<br />
�<br />
�<br />
�<br />
�<br />
�<br />
�<br />
�<br />
�<br />
�<br />
�<br />
Ground control: - Not provided, no claim made e.g. failure rate =1<br />
1st aircraft considered action based on CTAF frequency and protocols (e.g.<br />
H-V pair 3.23% failure)<br />
2nd aircraft considered action based on CTAF frequency and protocols (e.g.<br />
H-V pair 16.4% failure)<br />
Common mode failure (no working radio or wrong frequency) ( e.g. H-V pair<br />
1.11% failure)<br />
Combination <strong>of</strong> mutual considered action or common mode leads to<br />
avoidance action failure (e.g. H-V pair 1.63% failure)<br />
1st aircraft evasive action VMC based on unalerted see and avoid protocols<br />
(e.g. H-V pair 31.2% failure)<br />
2nd aircraft evasive action VMC based on unalerted see and avoid protocols<br />
(e.g. H-V pair 25.5% failure)<br />
Combination <strong>of</strong> mutual evasive action in VMC (e.g. H-V pair 7.95% failure)<br />
Note evasive action fails in IMC. No claim made<br />
Conflict geometry – collision avoided due to chance (e.g. H-V pair 0.2%)<br />
The model assumes that a mid-air collision will occur if a conflict pair exists and all<br />
six barriers fail. (e.g. H-V pair VMC 2.6 chances in a million).<br />
Table 3 presents the results for all ten pairs for VMC and IMC (expressed in terms <strong>of</strong><br />
chances per million). MAC probabilities are then given, also on chances per million,<br />
as the composite <strong>of</strong> likelihood per pair times the number <strong>of</strong> pairs derived from the<br />
movement data for PMQ.<br />
1 st aircraft V L L M M M H H H H<br />
2 nd aircraft V V L V L M V L M H<br />
VMC generic 2.24 1.07 0.17 1.96 0.13 0.04 2.6 0.15 0.04 0.13<br />
IMC generic 2.48 1.84 0.84 3.177 1.31 2.18<br />
PMQ MAC probability 718 141 43 54 6 0.6 93 12 1 3<br />
Table 3 – Mid air collision probability as generic likelihood multiplied by no. <strong>of</strong> conflict pairs for<br />
PMQ<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 43 <strong>of</strong> 69<br />
Table 4 completes the model analysis by assuming a range <strong>of</strong> consequences<br />
depending on aircraft type:<br />
� IFR(H) are assumed to carry 69 persons at risk,<br />
� IFR(M) 30,<br />
� IFR(L) 6 and<br />
� VFR 2.<br />
The consequences to PT operations (H, M and L) comprise average seating capacity<br />
modified by a 70% occupancy factor. It is also assumed that only one aircraft is lost<br />
in a MAC. The other flies away.<br />
First aircraft V L L M M M H H H H<br />
Second aircraft V V L V L M V L M H<br />
Consequences<br />
(N or more<br />
fatalities)<br />
Cumulative<br />
frequency<br />
2 4 6 16 18 30 36 39 57 69<br />
1.07<br />
E-03<br />
3.53<br />
E-04<br />
2.12<br />
E-04<br />
1.69<br />
E-04<br />
1.15<br />
E-04<br />
1.09<br />
E-04<br />
1.09<br />
E-04<br />
1.61<br />
E-05<br />
Table 4 – Cumulative frequency <strong>of</strong> N or more fatalities in a mid-air collision<br />
3.76<br />
E-06<br />
2.73<br />
E-06<br />
Figure 14 presents an XY log-log graph <strong>of</strong> the last two lines <strong>of</strong> Table 4, namely:<br />
cumulative frequency <strong>of</strong> N or more fatalities plotted in comparison with CASA interim<br />
risk criteria lines.<br />
The criteria are presented in five regions.<br />
• Below the bottom ‘Acceptable Risk’ line, in the bottom left corner, risks are<br />
said to be trivial.<br />
• Between the bottom ’Acceptable Risk’ and second bottom ‘Middle ALARP’<br />
lines, risks are in the bottom part <strong>of</strong> the As Low As Reasonable Practicable<br />
(ALARP) region. Risks in this region are tolerable only if the cost <strong>of</strong> risk<br />
reduction would exceed the improvement gained.<br />
• Between the middle two lines – the ‘Middle ALARP’ line and the ‘Scrutiny’<br />
line, risks are in the top part <strong>of</strong> the ALARP region, tolerable only when<br />
reduction is impractical or if cost is grossly disproportionate to the<br />
improvement gained<br />
• Between the second top ‘Scrutiny’ line and the top lines, risks above the<br />
scrutiny level are possibly unjustifiable<br />
• Above the top line, in the top right corner, risks are considered intolerable<br />
except in extraordinary circumstances.<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 44 <strong>of</strong> 69<br />
1.00E-01<br />
1.00E-02<br />
1.00E-03<br />
1.00E-04<br />
1.00E-05<br />
1.00E-06<br />
1 10 100<br />
Acceptable<br />
Figure 14 - Cumulative frequency <strong>of</strong> N or more fatalities in a mid-air collision<br />
Scrutiny<br />
Undesirable<br />
Tolerable<br />
Series1<br />
For PMQ, the IFR(H)-VFR conflict pair represents by far the greatest risk. This risk at<br />
1.09 E-4 likelihood <strong>of</strong> 36 fatalities is certainly undesirable, but does not yet approach<br />
the scrutiny line. A significant increase in total movements, to 50,000 per annum for<br />
example, is expected to exceed the scrutiny line.<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 45 <strong>of</strong> 69<br />
9 Evaluation<br />
This section presents the sensitivity analysis <strong>of</strong> the options including AFRU, Unicom,<br />
CA/GRO, Class E airspace and Class D tower. It considers options to reduce risks at<br />
CTAF(R) where the ARM results are in the undesirable upper part <strong>of</strong> the ALARP<br />
region approaching the scrutiny line.<br />
As above, for 37,716 movements per annum there were 623.3 conflict pairs at PMQ<br />
and the highest risk was IFR(H) - VFR at N =>36 fatalities with frequency F=1.9 E-4,<br />
scrutiny being at F=2.6 E-4 for that value <strong>of</strong> N. This is closer to scrutiny than<br />
tolerable.<br />
The ARM ‘Grand Table’ comprises a number <strong>of</strong> fault tree models including CTAF and<br />
Mandatory Broadcast Zones (MBZ) - now CTAF(R) with and without DTI, AFRU and<br />
CA/GRO.<br />
In the ARM Grand Table, there are numerous options. These have been collated in<br />
the following Table 5 for all 16 conflict pairs, focussed on the loss <strong>of</strong> control point.<br />
A/c1 (V, L, M or H) V L L L M M M M M H H H H H H H<br />
A/c2 (V, L, M or H) V V L L V L L M M V L L M M H H<br />
VMC or IMC V V V I V V I V I V V I V I V I<br />
Basic CTAF 95 15765 6217 228 3373 6685 94 1319 17 365 4945 62 1319 12 365 3 365<br />
CTAF 95 with DTI 15664 6114 172 2552 6626 65 902 15 333 4903 43 902 11 333 2 333<br />
CTAF 95 with AFRU<br />
& CAGRO 8582 3040 150 2220 2990 46 647 7 152 2212 31 647 5 152 1 152<br />
Basic MBZ 6014 2031 228 3373 1755 94 1319 17 365 1299 62 1319 12 365 3 365<br />
MBZ with DTI 6019 1975 172 2552 1733 65 902 15 333 1282 43 902 11 333 2 333<br />
MBZ with AFRU &<br />
CAGRO 4232 1191 150 2220 810 46 647 7 152 599 31 647 5 152 1 152<br />
MBZ with AFRU,<br />
CAGRO & DTI 4232 1191 134 1980 810 37 520 7 142 599 25 520 5 142 1 142<br />
Table 5 – Sensitivity <strong>of</strong> ARM<br />
Numbers are given in chances per million and must be multiplied by both the collision<br />
geometry probability and collisions pairs at the aerodrome to give an absolute<br />
estimate.<br />
The highest numbers, expressed in thousands per million involve VFR as one part <strong>of</strong><br />
a pair. IFR-IFR pairs have very low probabilities in VMC and somewhat higher in IMC<br />
(where see-and-avoid does not work). In this model, the basic MBZ (CTAF(R)) case<br />
for IFR(H) – VFR in VMC (HVV) carries a loss <strong>of</strong> control number <strong>of</strong> 1299 chances per<br />
million. Note that CTAF is 4,945 per million.<br />
Further consideration was given to which assumptions vary with each option –<br />
increased effectiveness <strong>of</strong> radio calls is apparent between CTAF and CTAF(R), but<br />
DTI, AFRU and CA/GRO act in different ways for different conflict pairs as shown in<br />
Table 6:<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 46 <strong>of</strong> 69<br />
A/c1 (V, L, M or H) V L L L M M M M M H H H H H H H<br />
A/c2 (V, L, M or H) V V L L V L L M M V L L M M H H<br />
VMC or IMC V V V I V V I V I V V I V I V I<br />
RISK REDUCTION SERIES 1 (Percentage compared to base case = 100 (98 is little reduction 12 is much risk reduction))<br />
Basic CTAF 95 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100<br />
CTAF 95 wirth DTI 99 98 76 76 99 68 68 91 91 99 68 68 91 91 91 91<br />
CTAF 95 with AFRU<br />
& CAGRO 54 49 66 66 45 49 49 42 42 45 49 49 42 42 42 42<br />
Basic MBZ 38 33 100 100 26 100 100 100 100 26 100 100 100 100 100 100<br />
MBZ with DTI 38 32 76 76 26 68 68 91 91 26 68 68 91 91 91 91<br />
MBZ with AFRU &<br />
CAGRO 27 19 66 66 12 49 49 42 42 12 49 49 42 42 42 42<br />
MBZ with AFRU,<br />
CAGRO & DTI 27 19 59 59 12 39 39 39 39 12 39 39 39 39 39 39<br />
RISK REDUCTION SERIES 2 (Percentage compared to base case = 100 ((98 is little reduction 12 is much risk reduction))<br />
Basic MBZ 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100<br />
MBZ with DTI 100 97 76 76 99 68 68 91 91 99 68 68 91 91 91 91<br />
MBZ with AFRU &<br />
CAGRO 70 59 66 66 46 49 49 42 42 46 49 49 42 42 42 42<br />
MBZ with AFRU,<br />
CAGRO & DTI 70 59 59 59 46 39 39 39 39 46 39 39 39 39 39 39<br />
Table 6 – Risk Reduction Series Note Mandatory Broadcast Zone (MBZ) now known as CTAF(R)<br />
In Table 6, Risk reduction Series 1 commences with the Basic CTAF 95 set at = 100<br />
and calculates the risk reduction from various cases. For IFR(H)-VFR in VMC (HVV)<br />
for example:<br />
�<br />
�<br />
�<br />
�<br />
�<br />
�<br />
�<br />
�<br />
Basic CTAF 95 100;<br />
with DTI 99;<br />
with AFRU and CAGRO 45; and<br />
with CTAF(R) 26.<br />
Taking MBZ-CTAF(R) as the base case, note that all <strong>of</strong> the CTAF options are less<br />
safe than CTAF(R).<br />
For CTAF(R) base case:<br />
CTAF(R) 100;<br />
with DTI 99;<br />
with AFRU and CAGRO 46; and<br />
with AFRU and CAGRO and DTI 46.<br />
The DTI case applies only to IFR-IFR pairs and provides reasonable risk reductions<br />
by ensuring that IFR(L) are known to IFR(M) and IFR(H) especially in IMC<br />
AFRU & CA/GRO essentially reduce risk across the board by 50%. This would<br />
reduce the IFR(H) – VFR point on the graph to closer to tolerable than scrutiny.<br />
A more detailed examination <strong>of</strong> the ARM would be required to determine the<br />
individual contributions <strong>of</strong> AFRU and CA/GRO.<br />
The ARM also provides insights into the operation <strong>of</strong> TCAS and transponders. TCAS<br />
is a particular implementation <strong>of</strong> Airborne Collision Avoidance System (ACAS). ACAS<br />
is designed to provide a Traffic Advisory (TA) alert at 45 seconds from closest point<br />
<strong>of</strong> approach (CPA); a mandatory Resolution Advisory (RA) at 25 seconds and, if the<br />
threat persists, a reversal.<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 47 <strong>of</strong> 69<br />
These timeframes are well inside both separation and segregation standards and<br />
explain three things:<br />
�<br />
�<br />
�<br />
why ACAS is a last line <strong>of</strong> defence; and<br />
the ACAS safety net is outside the normal ATS system;<br />
ICAO has stated that the ‘carriage <strong>of</strong> ACAS by aircraft in a given area shall<br />
not be a factor in determining the need for air traffic services in that area’<br />
(Annex 11.2.4.2)<br />
Nevertheless, large aircraft are required to have TCAS and any aircraft entering<br />
controlled airspace must have a transponder. Pilots can and do use the system for<br />
long range detection to enhance radio calls and visual acquisition, the latter being<br />
improved by as much as a factor <strong>of</strong> eight.<br />
A recent cost: benefit and risk study <strong>of</strong> ‘ACAS and Transponders’ for Department <strong>of</strong><br />
Infrastructure, Transport, Regional Development and Local Government<br />
recommended to extend the existing mandate covering Class A, C and E airspace<br />
and above 10,000 ft AMSL to new transponder designated areas such as Class D<br />
and CTAF(R). The latter is supported by this review.<br />
With respect to Class E, the National Airspace System experience was that<br />
exhaustive safety assessments need to be conducted on both the design <strong>of</strong> airspace<br />
and its implementation into an Australian NAS. The suggestion <strong>of</strong> installing Class E<br />
airspace in order to simply have aircraft equipped with transponders would require a<br />
full safety assessment and would meet much resistance. Most pilots should already<br />
have transponders. It is a case <strong>of</strong> education to get them to turn them on and make<br />
the correct broadcasts.<br />
Figure 15 presents the cumulative risk curve (FN curve) <strong>of</strong> annual frequency (F) <strong>of</strong> N<br />
or more fatalities plotted against the number <strong>of</strong> fatalities (N). The risk criteria lines are<br />
as given on Figure 14.<br />
Figure 15 further presents the sensitivity <strong>of</strong> the risk analysis to a +/- 10% movement<br />
envelope.<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 48 <strong>of</strong> 69<br />
Annual Frequency <strong>of</strong> N or More Fatalities (Likelihood)<br />
1<br />
0.1<br />
0.01<br />
0.001<br />
0.0001<br />
0.00001<br />
0.000001<br />
Cumulative Risk Line (FN Curve)<br />
± 10% Movement Envelope<br />
<strong>Port</strong> <strong>Macquarie</strong><br />
Acceptable Risk<br />
Criteria<br />
1<br />
0.1<br />
0.01<br />
0.001<br />
0.0001<br />
0.00001<br />
0.000001<br />
0.0000001<br />
1 10 100 1000<br />
Fatalities<br />
Figure 15 - Cumulative frequency <strong>of</strong> N or more fatalities in a mid-air collision<br />
Scrutiny Risk Line<br />
Middle ALARP Line<br />
Acceptable Risk Line<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 49 <strong>of</strong> 69<br />
10 Conclusions<br />
a. According to stakeholders and a recent review by Airservices, the current traffic<br />
levels and complexity at PMQ aerodrome did not indicate the need for a higher<br />
level <strong>of</strong> service beyond the present CTAF. However, the ARM shows<br />
undesirable risks levels which could approach scrutiny levels with only a modest<br />
increase in aircraft movements. In the words <strong>of</strong> Charles Perrow’s book on<br />
‘Normal Accidents’, constant vigilance is indicated. A number <strong>of</strong> options are<br />
available to address the issues raised. These include:<br />
• Unicom or CA/GRS;<br />
• Lowering <strong>of</strong> Class E airspace; and<br />
• Provision <strong>of</strong> Class D tower procedural services<br />
(The OAR makes the following additional comments:<br />
o The Report’s risk modelling analysis reflected that the level <strong>of</strong> risk<br />
was within acceptable parameters. The movement data used during<br />
the modelling process was a mixture <strong>of</strong> Airservices arrival and<br />
departure movement data plus a revised figure thought to more<br />
accurately represent circuit movements. The revised circuit<br />
movement figure was based upon traffic observations made during<br />
the Report’s data gathering phase. The use <strong>of</strong> this revised figure<br />
was thought to more accurately reflect the actual circuit movements<br />
with its use for modelling purposes agreed upon after consultation<br />
with the OAR.<br />
o Since publication <strong>of</strong> the report, traffic movement data has been<br />
revised significantly by Airservices. Further modelling <strong>of</strong> the revised<br />
data by the OAR has indicated that the risk <strong>of</strong> conflict between an<br />
IFR (RPT) and VFR aircraft has reduced from the original<br />
assessment made by Hyder utilising the same modelling<br />
methodology. This <strong>of</strong>fers support to the qualitative feedback that no<br />
airspace change is required based on the existing traffic numbers<br />
and mix <strong>of</strong> operations. Accident<br />
o Feedback received by CASA on the content <strong>of</strong> the Report has since<br />
highlighted certain levels <strong>of</strong> stakeholder dissatisfaction with the level<br />
<strong>of</strong> ATS provided, with one stakeholder specifying that introduction <strong>of</strong><br />
Class E airspace corridor, or as a minimum, introduction <strong>of</strong> a<br />
Certified Air/Ground Radio Service (CA/GRS) should be considered<br />
before further growth in traffic is allowed.<br />
o Outside <strong>of</strong> the original scope <strong>of</strong> the Report and as part <strong>of</strong> its work<br />
program the OAR is carrying out a review <strong>of</strong> Australian-administered<br />
airspace with the intention <strong>of</strong> implementing a new structure<br />
developed in accordance with the principles <strong>of</strong> the AAPS. This<br />
review will include investigations into the introduction <strong>of</strong> a regional<br />
solution (including PMQ) that will assess the safety benefit <strong>of</strong>fered<br />
by the introduction <strong>of</strong> Class E airspace corridors, and the possible<br />
lowering <strong>of</strong> Class E terminal airspace. In the interim the OAR will<br />
continue to monitor traffic mix and movements at PMQ over the next<br />
12 months. Should any feedback received or data trends suggest<br />
that the level <strong>of</strong> airspace risk is approaching unacceptable, it will be<br />
acted upon by the OAR.)<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 50 <strong>of</strong> 69<br />
b. If there is any significant increase in movement numbers in the PMQ CTAF,<br />
(such as the introduction <strong>of</strong> a large flying school operation), or any increase in<br />
the complexity <strong>of</strong> the traffic mix (such as the introduction <strong>of</strong> a larger PT jet<br />
service), it is recommended that CASA conducts an aeronautical study<br />
regarding risk levels in the ‘scrutiny’ region and the need for increased<br />
airspace services.<br />
(The OAR makes the following additional comments - Regular monitoring<br />
and review <strong>of</strong> aircraft and passenger movement numbers, analysis <strong>of</strong> accident<br />
and incident data trends and analysis <strong>of</strong> feedback from stakeholders either by<br />
direct communication or various consultative forums, is part <strong>of</strong> the OAR’s dayto-day<br />
business.)<br />
c. In order to lower potential risk during simultaneous use <strong>of</strong> the main and grass<br />
runways the PMQ airport operator is to impose operating limitations (via<br />
ERSA) on the grass runway 10/28 (e.g. not to be used for circuit training or<br />
during PT arrival and departures). The aerodrome operator may also wish to<br />
consider placing a restriction in ERSA on the number <strong>of</strong> aircraft that can<br />
simultaneous use the circuit area for circuit training, particularly at night. CASA<br />
Operations are able to assist in the development <strong>of</strong> any procedural changes.<br />
(The OAR makes the following additional comments - requires further<br />
investigation by the Aerodrome Operator to establish the level <strong>of</strong> risk posed by<br />
grass runway operations.)<br />
d. While there have been no formal incident reports or complaints, consideration<br />
should still be given to the safety <strong>of</strong> the parachuting jumping operation onto a<br />
secure aerodrome that is serviced by three PT operators and a busy GA area.<br />
(The OAR makes the following additional comments - requires further<br />
consultation between the Aerodrome Operator and parachute operators to<br />
establish the level <strong>of</strong> risk posed by parachuting operations in the vicinity <strong>of</strong><br />
PMQ.)<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 51 <strong>of</strong> 69<br />
11 CASA Final Comment and Actions for <strong>Port</strong> <strong>Macquarie</strong><br />
CASA makes the following final recommendations for PMQ:<br />
1. As part <strong>of</strong> its normal business the OAR will maintain a watch <strong>of</strong> activity at PMQ<br />
aerodrome. This will include monitoring traffic levels and complexity, and will<br />
focus particularly on the frequency and type <strong>of</strong> operations. Should any<br />
significant change to movements or type <strong>of</strong> operations occur a further<br />
aeronautical study will be conducted by the OAR to reassess the risk to any PT<br />
operations.<br />
2. That the existing airspace classification in the vicinity <strong>of</strong> the aerodrome remains<br />
Class G, subject to CTAF procedures.<br />
3. That QantasLink and Virgin Blue consult with Airservices, Airport Relations to<br />
discuss their issue with regards the close proximity <strong>of</strong> the RNAV approach fix <strong>of</strong><br />
PMQNG to R574.<br />
4. That the aerodrome operator carry out further investigation to quantify grass<br />
runway operations and assess the impact <strong>of</strong> these operations in opposition to<br />
passenger transport operations using the main runway.<br />
5. That the aerodrome operator carries out consultation with the parachute<br />
operator to establish the risk posed by their activities to passenger transport<br />
operations.<br />
6. That CASA <strong>Aviation</strong> <strong>Safety</strong> Advisors (ASAs) consult and coordinate with the<br />
aerodrome operator to establish a regular program <strong>of</strong> aviation safety seminars<br />
and encourages attendance by PMQ aerodrome stakeholders. This will enable<br />
the aviation community to provide feedback to CASA and to receive updates on<br />
regulatory reform that may impact on their business or recreational activities.<br />
The ASAs will also be able to provide the aerodrome operator with guidance on<br />
the reduction <strong>of</strong> risks posed to passenger transport activity by grass runway and<br />
parachuting operations.<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 52 <strong>of</strong> 69<br />
12 References<br />
<strong>Aeronautical</strong> Information Publication, revised 4 th June 2009<br />
Airservices Australia Data Validation Report – February 2008 to February 2009<br />
ATSB Air <strong>Safety</strong> Incident Reports – 1 st January 2007 to 31 st December 2008<br />
Airspace Act 2007<br />
Airspace Reviews by Office <strong>of</strong> Airspace Regulation including Adelaide, Ayers Rock,<br />
Bathurst and Maroochydore.<br />
AS/NZS 4360:2004 Risk Management<br />
Bureau <strong>of</strong> Meteorology<br />
CASA Instrument number CASA 443/05 <strong>of</strong> 9 November 2005<br />
CASA’s modelling tool - Airspace Risk Model<br />
CAR 1988, regulation 166.<br />
Airservices Electronic <strong>Safety</strong> Incident Reports – 12 months to February 2009<br />
ICAO Annex 11<br />
ICAO Review <strong>of</strong> the General Concept <strong>of</strong> Separation Panel (RGCSP) 1996<br />
presentation on ARM.<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 53 <strong>of</strong> 69<br />
Annexes:<br />
A. Acronyms<br />
B. Australian Airspace Structure<br />
C. Stakeholders<br />
D. Aerodrome Operator Data<br />
E. Definitions and Explanation <strong>of</strong> Terms<br />
F. Stakeholder Consultation / Feedback Register<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version: 1.0
Office <strong>of</strong> Airspace Regulation Page 54 <strong>of</strong> 69<br />
Annex A – Acronyms<br />
Acronym Explanation<br />
AAPS Australian Airspace Policy Statement, 28 June 2007<br />
ACAS Airborne Collision Avoidance System<br />
ACP Aircraft Change proposal<br />
Act Airspace Act 2007<br />
AD Aerodrome<br />
ADF Australian Defence Force<br />
AGL Above Ground level (in feet)<br />
AFRU Aerodrome Frequency Response Unit<br />
AIP <strong>Aeronautical</strong> Information Publication<br />
Airservices Airservices Australia<br />
Airprox Two or more aircraft in close proximity<br />
ALA Aircraft Landing Area<br />
ALARP As Low As Reasonably Practicable<br />
AMSL Above Mean Sea Level<br />
ANSP Air Navigation Service Provider<br />
AOC Air Operators’ Certificate<br />
ARAP Airspace Risk Assessment Process<br />
ARFSS Aerodrome Rescue and Fire Fighting Service<br />
ARM Airspace Risk Model<br />
AS/NZS Australian/New Zealand Standard<br />
ASA <strong>Aviation</strong> <strong>Safety</strong> Advisor<br />
ASIR <strong>Aviation</strong> <strong>Safety</strong> Incident Reports<br />
ATC Air Traffic Control<br />
ATS Air Traffic Services<br />
ATSB Australian Transport <strong>Safety</strong> Bureau<br />
AWIS Automated Weather Information System<br />
BOM Bureau <strong>of</strong> Meteorology<br />
CAR <strong>Civil</strong> <strong>Aviation</strong> Regulation<br />
CASA <strong>Civil</strong> <strong>Aviation</strong> <strong>Safety</strong> <strong>Authority</strong><br />
CASR <strong>Civil</strong> <strong>Aviation</strong> <strong>Safety</strong> Regulation<br />
CA/GRS Certified Air/Ground Radio Service<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version: 1.0
Office <strong>of</strong> Airspace Regulation Page 55 <strong>of</strong> 69<br />
Acronym Explanation<br />
CH C<strong>of</strong>fs Harbour<br />
CMH Camden Haven<br />
CPA Closest Point <strong>of</strong> Approach<br />
CTA Controlled Airspace<br />
CTAF Common Traffic Advisory Frequency<br />
CTAF(R) Common Traffic Advisory Frequency (Radio Required)<br />
CTR Control Zone<br />
DA Danger Area<br />
DME Distance Measuring Equipment<br />
DTA Designated Transponder Area<br />
DTI Directed Traffic Information<br />
ERSA En Route Supplement Australia (AIP)<br />
ESIR Electronic <strong>Safety</strong> Incident Report<br />
FAF Final Approach Fix<br />
FIA Flight Information Area<br />
FIS Flight Information Service<br />
FL Flight Level<br />
FOI Flying Operations Inspector<br />
FN-curve Frequency (F) <strong>of</strong> N or more fatalities<br />
FNA Fly Neighbourly Agreement<br />
ft feet<br />
FTC Failure to Comply<br />
GA General <strong>Aviation</strong><br />
GAOG General <strong>Aviation</strong> Operations Group, CASA<br />
GNSS Global Navigation Satellite System (Navigational Aid)<br />
GPS Global Positioning System (Navigational Aid)<br />
H24 24 hours a day<br />
HEL Helicopter<br />
Hyder Hyder Consulting<br />
IAS Indicated Air Speed<br />
ICAO International <strong>Civil</strong> <strong>Aviation</strong> Organization<br />
IFR Instrument Flight Rules<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 56 <strong>of</strong> 69<br />
Acronym Explanation<br />
IFR(H) IFR heavy - more than 38 passengers<br />
IFR(L) IFR light - less than 10 passengers<br />
IFR(M) IFR medium – 10 to 38 passengers 38 passengers<br />
IMC Instrument Meteorological Conditions<br />
KMP Kempsey<br />
KT Knot<br />
LKS The Lakes<br />
LL Lower Limit<br />
LSALT Lowest Safe Altitude<br />
MAC Mid air collision<br />
MATS Manual <strong>of</strong> Air Traffic Services<br />
MBZ Mandatory Broadcast Zone<br />
MED Medical<br />
MEL Minimum Equipment List<br />
MHz MegaHertz<br />
Mode C Transponder mode relaying information about aircraft identity, position and<br />
altitude<br />
MOS Manual <strong>of</strong> Standards<br />
MOU Memorandum <strong>of</strong> Understanding<br />
NDB Non-directional Radio Beacon (Navigational Aid)<br />
NM Nautical mile<br />
NOTAM Notice to Airmen<br />
NPRM Notice <strong>of</strong> Proposed Rule Making<br />
OAR Office <strong>of</strong> Airspace Regulation<br />
OBR Old Bar<br />
PA Prohibited Area<br />
PAL Pilot Activated Lighting<br />
PAPI Precision Approach Path Indicator (Navigational Aid)<br />
PJE Parachute Jumping Exercise<br />
PMQ <strong>Port</strong> <strong>Macquarie</strong><br />
PT Passenger Transport (encompassing regular public transport and all<br />
non-freight-only carrying charter operations)<br />
RA Resolution Advisory (ACAS)<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 57 <strong>of</strong> 69<br />
Acronym Explanation<br />
RA Restricted Area<br />
RAAF Royal Australian Air Force<br />
RAPAC Regional Airspace Procedural Advisory Committee<br />
RFDS Royal Flying Doctor Service<br />
RIS Radar Information Service<br />
RNAV Area Navigation (Navigational Aid)<br />
RWY Runway<br />
SAR Search and Rescue<br />
SFAIRP So Far As Is Reasonably Practicable, also SFAP (So far As Practicable)<br />
SFC Surface<br />
SOP Standard Operating Procedure<br />
SP Special Procedure<br />
SSR Secondary Surveillance Radar<br />
SY Sydney<br />
TA Traffic Advisory (ACAS)<br />
TAF Terminal Aerodrome Forecast<br />
TCAS Traffic Alert and Collision Avoidance System<br />
TRE Taree<br />
TRM The Round Mountain<br />
TWY Taxiway<br />
UNL Unlimited<br />
VCA Violation <strong>of</strong> Controlled Airspace<br />
VFG VFR Flight Guide<br />
VHF Very High Frequency radio<br />
VMC Visual Meteorological Conditions<br />
VOR VHF Omni-directional Radio Range (Navigational Aid)<br />
WAM Wide Area Multilateration<br />
WLM Williamtown<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 58 <strong>of</strong> 69<br />
Annex B – Australian Airspace Structure<br />
Class Description Summary <strong>of</strong> Services/Procedures/Rules<br />
A<br />
All airspace above<br />
Flight Level (FL) 180 (east<br />
coast) or FL 245<br />
B Not currently used in Australia<br />
C<br />
D<br />
E<br />
In control zones (CTRs) <strong>of</strong><br />
defined dimensions and<br />
control area steps<br />
generally associated with<br />
controlled aerodromes<br />
Towered locations such<br />
as Bankstown, Jandakot,<br />
Archerfield, Parafield and<br />
Alice Springs.<br />
Controlled airspace not<br />
covered in classifications<br />
above<br />
F Not currently used in Australia<br />
G Non-controlled<br />
*Not applicable to military aircraft<br />
Instrument Flight Rules (IFR) only. All aircraft require a clearance from Air Traffic Control (ATC) and are separated by<br />
ATC. Continuous two-way radio and transponder required. No speed limitation.<br />
� All aircraft require a clearance from ATC to enter airspace. All aircraft require continuous two-way radio and<br />
transponder.<br />
� IFR separated from IFR, Visual Flight Rules (VFR) and Special VFR (SVFR) by ATC with no speed limitation for<br />
IFR operations.<br />
� VFR receives traffic information on other VFR but are not separated from each other by ATC. SVFR are separated<br />
from SVFR when visibility (VIS) is less than Visual Meteorological Conditions (VMC).<br />
� VFR and SVFR speed limited to 250 knots (kt) Indicated Air Speed (IAS) below 10,000 feet (ft) Above Mean Sea<br />
Level (AMSL)*.<br />
� All aircraft require a clearance from ATC to enter airspace. For VFR flights this may be in an abbreviated form. As<br />
in Class C airspace all aircraft are separated on take <strong>of</strong>f and landing. All aircraft require continuous two-way radio<br />
and are speed limited to 200 kt IAS at or below 2,500 ft within 4 NM <strong>of</strong> the primary Class D aerodrome and 250 kt<br />
IAS in the remaining Class D airspace.<br />
� IFR are separated from IFR, SVFR, and are provided with traffic information on all VFR.<br />
� VFR receives traffic on all other aircraft but are not separated by ATC.<br />
� SVFR are separated from SVFR when VIS is less than VMC.<br />
� All aircraft require continuous two-way radio and transponder. All aircraft are speed limited to 250 kt IAS below<br />
10,000 ft AMSL*,<br />
� IFR require a clearance from ATC to enter airspace and are separated from IFR by ATC, and provided with traffic<br />
information as far as practicable on VFR.<br />
� VFR do not require a clearance from ATC to enter airspace and are provided with a Flight Information Service<br />
(FIS). On request and ATC workload permitting, a Radar / ADS-B Information Service (RIS) is available within<br />
surveillance coverage.<br />
� Clearance from ATC to enter airspace not required. All aircraft are speed limited to 250 kt IAS below 10,000 ft<br />
AMSL*.<br />
� IFR require continuous two-way radio and receive a FIS, including traffic information on other IFR.<br />
� VFR receive a FIS. On request and ATC workload permitting, a RIS is available within surveillance coverage. VHF<br />
radio required above 5,000 ft AMSL and at aerodromes where carriage and use <strong>of</strong> radio is required.<br />
Table 7- Australian Airspace Classifications<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version: 1.0
Office <strong>of</strong> Airspace Regulation Page 59 <strong>of</strong> 69<br />
Annex C – Stakeholders<br />
Position Organisation<br />
<strong>Aviation</strong> <strong>Safety</strong> Advisor (ASA) Operations, CASA<br />
Aerodrome Operator – General<br />
Manager<br />
Aerodrome Operator – General<br />
Manager<br />
Resident Operator Johnston <strong>Aviation</strong><br />
<strong>Port</strong> <strong>Macquarie</strong> Airport, <strong>Port</strong> <strong>Macquarie</strong>-Hastings<br />
Council<br />
Taree Airport – Greater Taree/Manning Valley City<br />
Council<br />
Resident Operator Hastings District Flying Club<br />
Chief Pilot Pacific Coast Flying School and Seaplane Flights<br />
Resident Operator Coastal Skydivers <strong>Port</strong> <strong>Macquarie</strong><br />
Resident Operator Arena International <strong>Aviation</strong> College<br />
Deputy Chief Pilot and Manager<br />
Regulatory Affairs<br />
Qantas Link (Eastern)<br />
Chief Pilot and PMQ Base Pilot Brindabella Airlines<br />
Non-resident operator Virgin Blue Airlines<br />
Group <strong>Safety</strong> Manager<br />
Sydney and Flight Operations<br />
Manager<br />
Regional Express (REX) Airlines<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation<br />
Page 60 <strong>of</strong> 69<br />
Eastern Section Royal Flying Doctor Service<br />
Table 8 – List <strong>of</strong> Stakeholders<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 61 <strong>of</strong> 69<br />
Annex D – Aerodrome Operator Data<br />
The Aerodrome Operator provided data on landings over a 12 month period.<br />
Table 9 below analyses movements in terms <strong>of</strong> landings made by particular aircraft.<br />
.<br />
Description<br />
Average<br />
capacity<br />
Landings<br />
Passenger<br />
capacity<br />
IFR(H) e.g.DHC-8 43 2032 88051<br />
IFR(M) e.g. SA227 14 1643 22,253<br />
IFR(L) e.g. PA31 5 2,016 9,431<br />
VFR e.g. Cessna 172 2 4,821 11,322<br />
Total Landings/seats 10,512 131,058<br />
Movements (landings x 2) 21,024 261,116<br />
Passengers (70% occupancy) 238,501<br />
Table 9 - Aircraft landings at PMQ (12 months) by group and frequency<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version: 1.0
Office <strong>of</strong> Airspace Regulation Page 62 <strong>of</strong> 69<br />
Annex E – Definitions and Explanation <strong>of</strong> Terms<br />
The below explanation <strong>of</strong> terms are based upon information found within the<br />
Australian Airspace Policy Statement 2007, CASR Part 139 and CASR Part 139<br />
Manual <strong>of</strong> Standards (MOS).<br />
Prohibited Area The declaration <strong>of</strong> a Prohibited Area (PA) defines an area over<br />
which aircraft may not fly. PAs have activity times and lateral and vertical limits.<br />
Restricted Area The declaration <strong>of</strong> a Restricted Area (RA) creates airspace <strong>of</strong><br />
defined dimensions within which the flight <strong>of</strong> aircraft is restricted in accordance with<br />
specified conditions. Clearances to fly over an active RA are generally only withheld<br />
when activities hazardous to the aircraft are taking place, or when military activities<br />
require absolute priority. RAs are mainly declared over areas where military<br />
operations occur. However, RAs have also been declared to cater for<br />
communications and space tracking operations or to control access to emergency or<br />
disaster areas. RAs are generally promulgated at specified times and dates. For<br />
example, a temporary RA may be declared for special events where there may be a<br />
public safety issue – such as the Avalon Air Show or the Commonwealth Games.<br />
Danger Area The declaration <strong>of</strong> a Danger Area (DA) defines airspace within which<br />
activities dangerous to the flight <strong>of</strong> aircraft may exist at specified times. Approval for<br />
flight over a DA outside controlled airspace is not required. However pilots are<br />
expected to maintain a higher level <strong>of</strong> vigilance in when transiting DAs. DAs are<br />
primarily established to alert aircraft on the following:<br />
� Flying training areas where student pilots are learning to fly and/or gather in<br />
large numbers;<br />
� Gliding areas where communications with airborne gliders might be difficult;<br />
� Blasting on the ground at mine sites;<br />
� Parachute operations;<br />
� Gas discharge plumes; and<br />
� Small arms fire from rifle ranges.<br />
Special Procedure A Special Procedure (SP) is a mutually agreed 'procedure' for<br />
aircraft operations in a particular area. Like a FNA, a SP is negotiated between<br />
aircraft operators and communities or authorities (e.g. a National Park) that have an<br />
interest in reducing the disturbance caused by aircraft within that area.<br />
Aerodrome Frequency Confirmation At all non-controlled aerodromes subject to<br />
CTAF procedures which are used not less than 5 times per week by aircraft engaged<br />
in air transport operations that have a maximum passenger seating capacity greater<br />
than nine, a ground-based frequency confirmation system is required. The frequency<br />
confirmation system must comply with the standards for frequency confirmation<br />
systems set out in the <strong>Civil</strong> <strong>Aviation</strong> <strong>Safety</strong> Regulation (CASR) Part 139 Manual <strong>of</strong><br />
Standards (MOS). This requirement may be practically satisfied by one <strong>of</strong> the<br />
following facilities:<br />
a. an Aerodrome Frequency Response Unit (AFRU)<br />
b. a Unicom (Universal Communications) service.<br />
c. a Certified Air/Ground Radio Service (CA/GRS)<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version: 1.0
Office <strong>of</strong> Airspace Regulation Page 63 <strong>of</strong> 69<br />
Automatic Frequency Response Unit (AFRU) An AFRU is an electronic, ground<br />
based, aviation safety enhancement device, intended for use on the CTAF frequency<br />
at non-controlled aerodromes. AFRU transmissions are triggered when the Unit<br />
detects aircraft transmissions on the correct aerodrome frequency. This response<br />
capability is intended to reduce the incidence <strong>of</strong> incorrect VHF radio frequency<br />
channel selection by pilots. The confirming AFRU transmission will be either a short<br />
pre-recorded voice message (e.g. aerodrome name followed by CTAF, or a short<br />
(300 millisecond) tone burst. An AFRU may also have an optional facility<br />
incorporated to allow pilot activation <strong>of</strong> the runway lights during hours <strong>of</strong> reduced light<br />
and darkness.<br />
Unicom Unicom is a non-regulated, third party, radio information service used at<br />
non-controlled aerodromes. Unicom services are non-Air Traffic Service (ATS) which<br />
enhance the value <strong>of</strong> information normally available about a non-controlled<br />
aerodrome. The primary function <strong>of</strong> the CTAF frequency is to provide the means for<br />
pilots operating in the vicinity <strong>of</strong> a non-controlled aerodrome to exchange traffic<br />
information for separation purposes. Unicom services, being a secondary use <strong>of</strong><br />
these frequencies, must not inhibit the exchange <strong>of</strong> aircraft to aircraft traffic<br />
information. Participation in Unicom services by an aerodrome operator, whether for<br />
the purposes <strong>of</strong> a frequency confirmation system or otherwise, is to be limited to the<br />
exchange <strong>of</strong> radio messages concerning:<br />
a. confirmation <strong>of</strong> the CTAF frequency selected by aircraft;<br />
b. general aerodrome weather reports;<br />
c. aerodrome information;<br />
d. estimated times <strong>of</strong> arrival and departure;<br />
e. passenger requirements;<br />
f. aircraft refuelling arrangements;<br />
g. maintenance and servicing <strong>of</strong> aircraft including the ordering <strong>of</strong> urgently<br />
required parts;<br />
h. unscheduled landings by aircraft.<br />
General aerodrome weather reports provided by a Unicom operator are to be limited<br />
to simple, factual statements about the weather, unless the Unicom operator is<br />
authorised by CASA to make meteorological observations.<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 64 <strong>of</strong> 69<br />
Certified Air/Ground Radio Service (CA/GRS). A CA/GRS is a non-controlled<br />
aerodrome based, third party radio information service, certified by CASA under <strong>Civil</strong><br />
<strong>Aviation</strong> <strong>Safety</strong> Regulation (CASR) Part 139. The primary purpose <strong>of</strong> a CA/GRS is to<br />
enhance the safety <strong>of</strong> air transport aircraft operations at a particular non-controlled<br />
aerodrome by the provision <strong>of</strong> relevant traffic information. Unless operating under an<br />
exemption from CASA the CA/GRS must be operating during the arrival and<br />
departure <strong>of</strong> aircraft engaged in PT or charter operations where the passenger<br />
seating capacity is greater than 29 seats. In accordance with CASR Part 139 Manual<br />
<strong>of</strong> Standards (MOS) a CA/GRS must provide the following services to aircraft within<br />
airspace as a designated non-controlled aerodrome:<br />
a. advice <strong>of</strong> relevant air traffic in the vicinity <strong>of</strong> the non-controlled aerodrome;<br />
b. aerodrome weather and operational information, including:<br />
(i) wind speed and direction;<br />
(ii) the runway preferred by wind or noise abatement requirements;<br />
(iii) runway surface conditions;<br />
(iv) QNH;<br />
(v) temperature;<br />
(vi) cloud base and visibility;<br />
(vii) present weather;<br />
(viii) other operational information;<br />
(ix) for departing aircraft, a time check;<br />
(x) call-out <strong>of</strong> the aerodrome emergency services;<br />
(xi) provide aerodrome information to pilots who telephone the service.<br />
A CA/GRS operator may also provide other information requested by pilots. The<br />
decision to use, or not to use, information provided by a CA/GRS rests with the pilot<br />
in command.<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 65 <strong>of</strong> 69<br />
Annex F – Stakeholder Consultation / Feedback Register<br />
No.<br />
1<br />
2<br />
Stakeholder /<br />
Commentator<br />
Airservices Australia,<br />
dated 4 th December<br />
2009<br />
TRIM ED10/134259<br />
Airservices Australia,<br />
dated 4 th December<br />
2009<br />
TRIM ED10/134259<br />
Reference Comment CASA response Action Response<br />
Editorial<br />
corrections<br />
and<br />
comments on<br />
Draft<br />
<strong>Aeronautical</strong><br />
<strong>Study</strong>.<br />
Editorial<br />
corrections<br />
and<br />
comments on<br />
Draft<br />
<strong>Aeronautical</strong><br />
<strong>Study</strong>.<br />
Section 1.1 Findings: the report<br />
found that there was no two way<br />
route structure between <strong>Port</strong><br />
<strong>Macquarie</strong> and C<strong>of</strong>fs Harbour. As<br />
a statement <strong>of</strong> fact it is correct, but<br />
we are unable to determine the<br />
relevance <strong>of</strong> the finding to the<br />
Airspace Review.<br />
Section 5.6.4, dot point 9:”(LSALT)”<br />
should be removed. The lower<br />
limit <strong>of</strong> airspace is not necessarily<br />
the LSALT and given the LSALT in<br />
the <strong>Port</strong> <strong>Macquarie</strong> area is 5,300<br />
feet this is definitely incorrect.<br />
Agreed. Information was<br />
included to provide an<br />
overall description <strong>of</strong> the<br />
airspace and air routes.<br />
No issues were raised by<br />
stakeholders regarding<br />
the air route.<br />
Agreed.<br />
Reference to “LSALT” in<br />
the dot point has been<br />
removed.<br />
None<br />
Removed “(LSALT)“ from<br />
dot point.<br />
Response sent<br />
TRIM<br />
ED10/136498<br />
Response sent<br />
TRIM<br />
ED10/136498<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version: 1.0
Office <strong>of</strong> Airspace Regulation Page 66 <strong>of</strong> 69<br />
Stakeholder /<br />
No. Reference Comment CASA response Action Response<br />
Commentator<br />
3<br />
4<br />
Airservices Australia,<br />
dated 4 th December<br />
2009<br />
TRIM ED10/134259<br />
Johnston <strong>Aviation</strong> dated<br />
1 st October 2009<br />
TRIM ED10/143445<br />
Editorial<br />
corrections<br />
and<br />
comments on<br />
Draft<br />
<strong>Aeronautical</strong><br />
<strong>Study</strong>.<br />
Frequency<br />
congestion<br />
Although not noted in the report,<br />
there is a similarity <strong>of</strong> the<br />
frequencies for <strong>Port</strong> <strong>Macquarie</strong><br />
(118.1) and C<strong>of</strong>fs Harbour (118.2)<br />
is material. In addition to the<br />
frequency congestion on 118.1,<br />
C<strong>of</strong>fs Harbour Tower also have a<br />
number <strong>of</strong> aircraft completing their<br />
all stations call on 118.2. Most <strong>of</strong><br />
these aircraft have departed C<strong>of</strong>fs<br />
Harbour.<br />
Flight crew who have to operate in<br />
the <strong>Port</strong> <strong>Macquarie</strong> airspace everyday<br />
are becoming increasingly<br />
concerned <strong>of</strong> aircraft at Taree overtransmitting<br />
radio transmissions<br />
between aircraft attempting to<br />
maintain separation in the <strong>Port</strong><br />
<strong>Macquarie</strong> CTAF(R), and I’m sure<br />
Taree CTAF users would be<br />
experiencing the same problems.<br />
The Taree over-transmitting<br />
problem is a continuing and everincreasing<br />
risk, and currently there<br />
is heavy fire fighting activity<br />
operating out <strong>of</strong> the Taree CTAF<br />
which is causing some very<br />
concerning problems for all<br />
airspace users at <strong>Port</strong> <strong>Macquarie</strong>.<br />
Agreed.<br />
Changes to CAR 166<br />
should reduce frequency<br />
congestion. Industry have<br />
requested that <strong>Port</strong><br />
<strong>Macquarie</strong> and Taree<br />
remain on the one<br />
frequency. Kempsey will<br />
be given a discrete<br />
frequency to reduce<br />
congestion.<br />
A Memorandum <strong>of</strong><br />
Understanding (MOU) is<br />
being developed between<br />
the Kempsey Shire<br />
Council (KSC) and<br />
the <strong>Port</strong> <strong>Macquarie</strong><br />
Hastings Council (PMHC)<br />
regarding the use <strong>of</strong> each<br />
aerodrome. It is expected<br />
that the MOU will lead to<br />
an expansion <strong>of</strong> jet<br />
services at <strong>Port</strong><br />
<strong>Macquarie</strong> and general<br />
aviation (training) at<br />
Kempsey airport.<br />
Ongoing surveillance<br />
Ongoing surveillance<br />
Response sent<br />
TRIM<br />
ED10/136498<br />
Response sent<br />
TRIM<br />
ED10/136803<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 67 <strong>of</strong> 69<br />
Stakeholder /<br />
No. Reference Comment CASA response Action Response<br />
Commentator<br />
5<br />
VirginBlue Airlines<br />
dated 6 November 2009<br />
TRIM ED09/166599<br />
Frequency<br />
congestion<br />
The Review details the level <strong>of</strong><br />
congestion on the CTAF frequency,<br />
the high and complex traffic volume<br />
and the opinion <strong>of</strong> most Airline<br />
pilots surveyed that the current<br />
level <strong>of</strong> service is inadequate. I<br />
think these factors are not given<br />
sufficient weight in the review.<br />
<strong>Port</strong> <strong>Macquarie</strong> sits in a large<br />
CTAF(R) area, containing five<br />
aerodromes and landing areas,<br />
with the addition <strong>of</strong> Kempsey very<br />
close by on the same CTAF<br />
frequency. Instrument approaches<br />
for <strong>Port</strong> <strong>Macquarie</strong> and Taree<br />
conflict and adjacent military<br />
airspace further complicates the<br />
situation. All these factors<br />
combined with bad weather<br />
produce an extremely high<br />
workload for an PT pilot who also<br />
has to provide own separation from<br />
small and slow GA aircraft possibly<br />
in a conflicting circuit.<br />
Consideration should also be given<br />
to the fact that the current airspace<br />
design actually hampers an<br />
increase in traffic.<br />
Changes to CAR 166<br />
should reduce frequency<br />
congestion. Industry have<br />
requested that <strong>Port</strong><br />
<strong>Macquarie</strong> and Taree<br />
remain on the one<br />
frequency.<br />
Kempsey will be given a<br />
discrete frequency to<br />
reduce congestion.<br />
A MOU is being<br />
developed between the<br />
KSC and the PMHC<br />
regarding the use <strong>of</strong> each<br />
aerodrome.<br />
It is expected that the<br />
MOU will lead to an<br />
expansion <strong>of</strong> jet services<br />
at <strong>Port</strong> <strong>Macquarie</strong> and<br />
general aviation (training)<br />
at Kempsey airport.<br />
Ongoing surveillance.<br />
Response sent<br />
TRIM<br />
ED10/155318<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 68 <strong>of</strong> 69<br />
Stakeholder /<br />
No. Reference Comment CASA response Action Response<br />
Commentator<br />
6<br />
VirginBlue Airlines<br />
dated 25 February 2010<br />
TRIM ED10/37796<br />
Proximity <strong>of</strong><br />
the waypoint<br />
PMQNG to<br />
the boundary<br />
<strong>of</strong> Restricted<br />
area R595.<br />
The Initial Approach Fix (PMQNG)<br />
is 1.49nm from the<br />
boundary <strong>of</strong> Restricted Area R595.<br />
The first proposed solution is to<br />
request that the military move the<br />
boundary <strong>of</strong> R595 to the East.<br />
The second proposed solution<br />
might be to suggest removal <strong>of</strong> the<br />
PMQNG waypoint altogether.<br />
If PMQNG is removed, the only<br />
way to commence another<br />
approach after conducting the<br />
missed approach would be to track<br />
to PMQND and enter the holding<br />
pattern. This would involve tracking<br />
across the inbound section <strong>of</strong> the<br />
approach inside the Intermediate<br />
Approach Fix at about the same<br />
altitude (2,000ft AMSL) as inbound<br />
aircraft.<br />
If PMQNG is removed, publishing a<br />
holding pattern at the waypoint<br />
PMQNE would allow crews to track<br />
there to commence another<br />
approach after a missed approach.<br />
Noted.<br />
R595 has been renamed<br />
R574. The NSW<br />
Regional Airspace<br />
Procedural Advisory<br />
Committee (RAPAC)<br />
discussed the issue at the<br />
June 2010 meeting.<br />
Defence advised the<br />
meeting that the existing<br />
volume <strong>of</strong> the area<br />
is completely required for<br />
operations. The Restricted<br />
Area boundary aligns<br />
with other Restricted<br />
Areas. By moving the<br />
R574 boundary, all the<br />
other Restricted Area<br />
boundaries would also<br />
need to be moved. The<br />
Instrument Approach<br />
meets PANS-OPS<br />
standards and is clear <strong>of</strong><br />
R574. RAPAC formed the<br />
view that with five VCA’s<br />
within the past three<br />
years, generally <strong>of</strong> PT<br />
origin, it was seen<br />
as an issue to be<br />
addressed through the<br />
respective<br />
company's <strong>Safety</strong><br />
Management Systems<br />
procedures in the short<br />
term.<br />
Ongoing surveillance.<br />
Report updated.<br />
Response sent<br />
TRIM<br />
ED10/155318<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0
Office <strong>of</strong> Airspace Regulation Page 69 <strong>of</strong> 69<br />
Stakeholder /<br />
No. Reference Comment CASA response Action Response<br />
Commentator<br />
7<br />
QantasLink Airways<br />
dated 26 February 2010<br />
Proximity <strong>of</strong><br />
the waypoint<br />
PMQNG to<br />
the boundary<br />
<strong>of</strong> Restricted<br />
area R595.<br />
The location <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> on<br />
the coast means that, more <strong>of</strong>ten<br />
than not, the best bad weather<br />
approach is from over the sea as<br />
the thunderstorms are mainly<br />
inland. If the PMQNG waypoint is<br />
removed aircrew will not have this<br />
(better) option.<br />
The airline would therefore prefer<br />
the Restricted Area be moved east<br />
by a few miles.<br />
Noted.<br />
The NSW RAPAC<br />
discussed the issue at the<br />
June 2010 meeting.<br />
Defence advised the<br />
meeting that the existing<br />
volume <strong>of</strong> the area<br />
is completely required for<br />
operations. The Restricted<br />
Area boundary aligns<br />
with other Restricted<br />
Areas. By moving the<br />
R574 boundary, all the<br />
other Restricted Area<br />
boundaries would also<br />
need to be moved. The<br />
Instrument Approach<br />
meets PANS-OPS<br />
standards and is clear <strong>of</strong><br />
R574. RAPAC formed the<br />
view that with five VCA’s<br />
within the past three<br />
years, generally <strong>of</strong> PT<br />
origin, it was seen<br />
as an issue to be<br />
addressed through the<br />
respective<br />
company's <strong>Safety</strong><br />
Management Systems<br />
procedures in the short<br />
term.<br />
Ongoing surveillance.<br />
Response sent<br />
TRIM<br />
ED10/155370<br />
Airspace Review <strong>of</strong> <strong>Port</strong> <strong>Macquarie</strong> (YPMQ) May 2010 Version 1.0