ANNEX
SUBPART PBN — Performance-based navigation
AUR.PBN.1005 Subject-matter
In accordance with Article 3, this Subpart sets out the requirements for the implementation of performance-based navigation (PBN) to be complied with by providers of ATM/ANS.
AUR.PBN.2005 Routes and procedures
(1)
Providers of ATM/ANS shall implement, at all instrument runway ends, approach procedures in accordance with the requirements of the RNP approach (RNP APCH) specification, including LNAV, LNAV/VNAV and LPV minima and, where required due to traffic density or traffic complexity, radius to fix (RF) legs.
(2)
By way of derogation from point (1), at instrument runway ends where, due to terrain, obstacles or air traffic separation conditions, the implementation of 3D approach procedures is excessively difficult, providers of ATM/ANS shall implement 2D approach procedures in accordance with the requirements of the RNP approach (RNP APCH) specification. In that case, they may also, in addition to the implementation of those 2D approach procedures, implement 3D approach procedures in accordance with the requirements of the RNP authorisation required (RNP AR APCH) specification.
(3)
By way of derogation from point (1) at instrument runway ends without an appropriate SBAS coverage, providers of ATM/ANS shall implement RNP APCH procedures, including LNAV and LNAV/VNAV minima. Providers of ATM/ANS shall also implement LPV minima at those instrument runway ends, no later than 18 months from the date at which such appropriate SBAS coverage is available.
(4)
Where providers of ATM/ANS have established SID routes or STAR routes, they shall implement those routes in accordance with the requirements of RNAV 1 specification.
(5)
By way of derogation from point (4), where providers of ATM/ANS have established SID routes or STAR routes and where higher performance requirements than those referred to in that point are required in order to maintain air traffic capacity and safety in environments with high traffic density, traffic complexity or terrain features, they shall implement those routes in accordance with the requirements of the RNP 1 specification, including one or more of the following additional navigation functionalities:
(a)
operations along a vertical path and between two fixes and with the use of:
(i)
an ‘AT’ altitude constraint;
(ii)
an ‘AT OR ABOVE’ altitude constraint;
(iii)
an ‘AT OR BELOW’ altitude constraint;
(iv)
a ‘WINDOW’ constraint;
(b)
the radius to fix (RF) leg.
(6)
Where providers of ATM/ANS have established ATS routes for en route operations, they shall implement those routes in accordance with the requirements of the RNAV 5 specification.
(7)
By way of derogation from points (4) and (6), where providers of ATM/ANS have established ATS routes, SID routes or STAR routes for rotorcraft operations, they shall implement those routes in accordance with the requirements of the RNP 0.3, RNAV 1 or RNP 1 specifications. In that case, they shall be entitled to decide which of those three sets of requirements they comply with.