965/2012, PART-SPA: Performance Based Navigation (PBN) Operations

965/2012, PART-SPA: Performance Based Navigation (PBN) Operations OPERATOR: ______AOC # ______Ind.No. ______This compliance list has been checked (date): ______This compliance list has been checked (name): ______

Instructions how to fill the compliance list The compliance list is a tool not replacing the applicable requirements of Regulation (EC) No 216/2008 and its Implementing Rules. The user must read and check the items in accordance with the Regulation (EC) No 216/2008 and its Implementing Rules. In case any error or deficiency is found in this list, it should be notified to the Authority to make the required corrections. All suggestions or corrections to the compliance list will be considered for improving and developing the list, and to make it more usable for the Operator and the Authority.

Compliance checklist includes requirements for both commercial air transport operations with aeroplanes and helicopters.

CONTENTS of Operation Manuals

The content of OM should be in accordance with AMC 3 ORO.MLR.100, where applicable, as relevant for the area and type of operation. If there are sections that, because of the nature of the operation, do not apply, it is recommended that operators maintain the numbering system described in ORO.MLR.101 and in AMC3 and AMC4 to ORO.MLR.100 and insert ‘Not applicable’ or ‘Intentionally blank’ where appropriate.

The operator shall enter to OM/Document Reference column the references to the operator’s manuals. In this column the operator shows where the requirement in the Requirement column will be found. These references must be entered at the highest detail so that they can be easily found.

11112015 1/16 If the required information is not included in the OM but in other document (for example requirements set down in 965/2012 Subpart D: Instruments, Data, Equipment) the operator must put the reference to the relevant document column OM/Document Reference.

If a Rule References paragraph is not applicable to the Operator, N/A should be marked to OM/Document Reference column by the operator. All applicable paragraphs in this compliance list should have either reference or N/A (if not applicable) in the OM/Document Reference column.

The column STATUS is for the authority to note when the applicable part of OM (or other document) is in accordance with the requirements. (OK/N

The column Comments is for user notes and declarations if needed.

In the Rule References column are references to the Rules and Acceptable Means of Compliances (AMCs). Guidance Materials (GMs) are mentioned below the Rules but GM texts are not included in this compliance list. It is the responsibility of the operator to study relevant Guidance Material.

Approval required column refers to ORO.GEN.130. If there is YES (filled by authority) in this column it means that prior approval is required by the competent authority. For any change requiring prior approval the operator shall apply for and obtain an approval issued by the competent authority before any such change takes place. This column is a non-exhaustive list of items that require prior approval (see ORO.GEN.130 and GM1 ORO.GEN.130(a) ja GM3 ORO.GEN.130(b)).

11112015 2/16 References to the Rule

Relevant GMs (if any) (texts are not included in this compliance list)

AMCs are placed right after the Rule they are related to.

Operator writes down the reference (exact location)

Note that in this checklist GM text is also included despite of the above presented generic information regarding Trafi’s compliance check lists.

11112015 3/16 Approval Rule References Requirement OM Reference Comments STATUS required

Commission Regulation NOTE: If certain operations (such --- (EU) No 965/2012 as RNP AR APCH) are not appropriate, please indicate it by writing for example ‘N/A, these operations are not being performed’. ANNEX V --- SPECIFIC APPROVALS ------[PART-SPA] ------SUBPART A --- GENERAL REQUIREMENTS --- SPA.GEN.100 Competent The competent authority for issuing a specific approval for the authority commercial operator shall be the authority of the Member State in which the operator has its principal place of business. SPA.GEN.105 Application for (a) The operator applying for the initial issue of a specific approval a specific approval shall provide to the competent authority the documentation required in the applicable Subpart, together with the following information: (1) the name, address and mailing address of the applicant; (2) a description of the intended operation. (b) The operator shall provide the following evidence to the competent authority: (1) compliance with the requirements of the applicable Subpart; (2) that the relevant elements defined in the mandatory part of the operational suitability data established in accordance with Regulation (EU) No 748/2012 are taken into account. (c) The operator shall retain records relating to (a) and (b) at least for the duration of the operation requiring a specific approval, or, if applicable, in accordance with Annex III (Part-ORO). AMC1 SPA.GEN.105(a) --- Application for a specific approval DOCUMENTATION --- (a) Operating procedures should be documented in the operations manual.

(b) If an operations manual is not required, operating procedures may be described in a manual specifying procedures (procedures manual). If the aircraft flight manual (AFM) or the pilot operating handbook (POH) contains such procedures, they should be considered as acceptable means to document the procedures SPA.GEN.110 Privileges of an The scope of the activity that an operator is approved to conduct operator holding a specific shall be documented and specified: approval (a) for operators holding an air operator certificate (AOC) in the operations specifications to the AOC.

SPA.GEN.115 Changes to a When the conditions of a specific approval are affected by changes, specific approval the operator shall provide the relevant documentation to the competent authority and obtain prior approval for the operation. SPA.GEN.120 Continued Specific approvals shall be issued for an unlimited duration and shall validity of a specific approval remain valid subject to the operator remaining in compliance with the requirements associated with the specific approval and taking into account the relevant elements defined in the mandatory part of the operational suitability data established in accordance with Regulation (EU) No 748/2012. --- Subpart B – Performance Aircraft shall only be operated in designated airspace, on routes or in Yes Based Navigation (PBN) accordance with procedures where performance- based navigation Operations (PBN) specifications are established if the operator has been granted an approval by the competent authority to conduct such operations. No specific approval is required for operations in area navigation 5 (RNAV5 (basic area navigation, B-RNAV)) designated airspace.

How does the operator fulfill this requirement? For example, how is this noticed in flight planning and operations (e.g. what methods, equipment and procedures are in use to ensure that PBN requirements of different airspaces are fulfilled)?

GM1 SPA.PBN.100 There are two kinds of navigation specifications: area navigation PBN operations, paragraph (a) (RNAV) and required navigation performance (RNP). These specifications are similar. The key difference is that a navigation specification that includes a requirement to have an on-board performance monitoring and alerting system is referred to as an RNP specification. An RNAV specification does not have such a requirement. The performance-monitoring and alerting system provides some automated assurance functions to the flight crew. These functions monitor system performance and alert the flight crew when the RNP parameters are not met, or cannot be guaranteed with a sufficient level of integrity. RNAV and RNP performance is expressed by the total system error (TSE). This is the deviation from the nominal or desired position and the aircraft’s true position, measured in nautical miles. The TSE should remain equal to or less than the required accuracy expected to be achieved at least 95 % of the flight time by the population of aircraft operating within the airspace, route or procedure.

 Please ensure that these definitions and issues are considered also in the appropriate PBN training program. GM1 SPA.PBN.100 The structure of RNAV and RNP navigation specifications can be PBN operations, paragraph (b) classified by phases of flight as detailed in Table 1. Some of these special approvals are in current use, some are under development, Note: See table 1 in GM1 and some apply to emerging standards for which AMC-20 material SPA.PBN.100. has yet to be defined.

Please write a list (to the ‘Comments’ column) of all the navigation specifications (as listed in table 1) that are planned to be performed.

GM1 SPA.PBN.100 (c) The following RNAV and RNP navigation specifications are Please specify how the Yes PBN operations, paragraph (c) considered: requirements from EASA AMC 20- (1) - RNP10 (1) Oceanic/Remote, RNAV10 (designated and authorised as RNP10) 12 are fulfilled. Consider all its OPS requirements with emphasis on the Acceptable means of compliance for RNAV10 (RNP10) are provided in following (see further details in EASA AMC 20-12, “Recognition of FAA order 8400.12a for RNP10 AMC 20-12): Operations”. Although RNAV10 airspace is, for historical reasons, also  4.4.1: Eligibility for RNP-10 called RNP10 airspace, there is no requirement for on-board  4.4.2: Aircraft Equipment and monitoring and alerting systems. RNAV10 can support 50 NM track Minimum Equipment List spacing. For an aircraft to operate in RNAV10 (RNP10) airspace it  4.4.3: 4.4.3 Operational needs to be fitted with a minimum of two independent long range Procedures and Training navigation systems (LRNSs). Each LRNS should in principle have a  4.5: Position Updating flight management system (FMS) that utilises positional information  4.5.1: Automatic radio position from either an approved global navigation satellite system (GNSS) or update an approved inertial reference system (IRS) or mixed combination.  4.5.2: Manual radio position The mix of sensors (pure GNSS, pure IRS or mixed IRS/GNSS) update determines pre-flight and in-flight operation and contingencies in the  4.6: Incident reporting event of system failure.

Please specify how these requirements are fulfilled. Please note that requested information is presented in ‘Comments’ column. Write requested information and/or references to OM / AFM to the ‘OM Reference’ column.

GM1 SPA.PBN.100 (c) The following RNAV and RNP navigation specifications are Please specify how the Yes PBN operations, paragraph (c) considered: requirements from ICAO Doc 9613 (2) - RNP4 (2) Oceanic/Remote, RNP4 (rev 4) Volume II Part C Chapter 4 (i.e. from page II-C-1-1) are fulfilled. Guidance for this RNP standard is provided in ICAO Doc 9613. RNP4 is Consider all its OPS requirements the oceanic/remote navigation specification to support 30 NM track with emphasis on the following (see spacing with ADS-C and CPDLC required. To meet this more accurate further details in ICAO Doc 9613): navigation requirement, two independent LRNS are required for  1.3.2.2 Aircraft eligibility which GNSS sensors are mandatory. If GNSS is used as a stand-alone  1.3.2.3.1 Description of aircraft LRNS, an integrity check is foreseen (fault detection and equipment exclusion).Additional aircraft requirements include two long range  1.3.2.3.2 Training communication systems (LRCSs) in order to operate in RNP4 documentation designated airspace. The appropriate air information publication  1.3.2.3.3 OMs and checklists (AIP) should be consulted to assess coverage of HF and SATCOM. The  1.3.2.3.4 MEL considerations additional requirements may include use of automatic dependent  1.3.2.3.5 Continuing surveillance (ADS) and/or controller pilot data link communication airworthiness (CPDLC).  1.3.4.2 Preflight planning  1.3.4.3 Availability of GNSS  Please specify how these requirements are fulfilled.  1.3.4.4 En route Please note that requested information is presented in ‘Comments’  1.3.5 Pilot knowledge and column. Write requested information and/or references to OM / training AFM to the ‘OM Reference’ column.  1.3.6 Navigation database GM1 SPA.PBN.100 (c) The following RNAV and RNP navigation specifications are Please specify how the A specific PBN operations, paragraph (c) considered: requirements from EASA AMC 20-4 operational (3) - B-RNAV (3) RNAV5 (B-RNAV) are fulfilled. Consider all its OPS approval is not requirements with emphasis on the required, but Acceptable means of compliance for RNAV5 are provided in AMC 20- following (see further details in criteria must be 4, “Airworthiness Approval and Operational Criteria for the Use of AMC 20-4): fulfilled so that Navigation Systems in European Airspace Designated for the Basic-  5.2 (a) Normal Procedures, RAIM this can be RNAV Operations”. No specific approval required.  5.2 (b) Normal Procedures, included into database validity AOC Please specify how these requirements are fulfilled.  5.2 (c) Normal Procedures, specification Please note that requested information is presented in ‘Comments’ navigation monitoring column. Write requested information and/or references to OM /  5.3 Abnormal Procedures in the AFM to the ‘OM Reference’ column. event of loss of GPS navigation capability (e.g. RAIM, alarm)  Annex 1 (RAIM prediction programme)

GM1 SPA.PBN.100 (c) The following RNAV and RNP navigation specifications are Please specify how the Yes PBN operations, paragraph (c) considered: requirements from ICAO Doc 9613 (4) - RNAV2 (4) RNAV2 (rev 4) Volume II Part B Chapter 3 (i.e. from page II-B-3-1) are fulfilled. This is a non-European en-route standard. Guidance for this RNP Consider all its OPS requirements standard is provided in ICAO Doc 9613. with emphasis on the following (see further details in ICAO Doc 9613): Please specify how these requirements are fulfilled.  3.3.2.2 Aircraft eligibility Please note that requested information is presented in ‘Comments’  3.3.2.3.1 Description of aircraft column. Write requested information and/or references to OM / equipment AFM to the ‘OM Reference’ column.  3.3.2.3.2 Training documentation  3.3.2.3.3 OMs and checklists  3.3.2.3.4 MEL considerations  3.3.2.3.5 Continuing airworthiness  3.3.2.4 Migration path to RNAV 1 and RNAV 2 (if applicable)  3.3.4.2 Preflight planning  3.3.4.2.4 ABAS availability  3.3.4.2.5 DME availability  3.3.4.3 General operating procedures (specify each individual item from this paragraph)  3.3.4.4 RNAV SID specific requirements  3.3.4.5 RNAV STAR specific requirements  3.3.5 Pilot knowledge and training  3.3.6 Navigation database

GM1 SPA.PBN.100 (c) The following RNAV and RNP navigation specifications are Please specify how the Yes PBN operations, paragraph (c) considered: requirements from JAA TGL-10 rev (5) - RNAV1 / P-RNAV (5) RNAV1 (P-RNAV) 1 are fulfilled. Consider all its OPS requirements with emphasis on the Acceptable means of compliance for RNAV1 (P-RNAV) are provided in following (see further details in JAA JAA TGL-10 ‘Airworthiness and Operational approval for precision TGL-10): RNAV operations in designated European Airspace’, planned to be  8.1: Compliance statement (see replaced by AMC 20 material. 8.1.a or 8.1.2).  9: Aircraft flight manual Please specify how these requirements are fulfilled.  10.2.1: Pre-flight planning Please note that requested information is presented in ‘Comments’  10.2.2: Departure column. Write requested information and/or references to OM /  10.2.3: Arrival AFM to the ‘OM Reference’ column.  10.3: Contingency procedures  10.4: Incident reporting  10.5: Flight crew training  10.6: Database integrity  10.7: Flight operations documentation

GM1 SPA.PBN.100 (c) The following RNAV and RNP navigation specifications are Please specify how the Yes PBN operations, paragraph (c) considered: requirements from ICAO Doc 9613 (6) - RNP1 (6) Basic–RNP1 (rev 4) Volume II Part C Chapter 3 (i.e. from page II-C-3-1) are fulfilled. This is a future standard yet to be implemented. Guidance material is Consider all its OPS requirements provided in ICAO Doc 9613. with emphasis on the following (see further details in ICAO Doc 9613): Please specify how these requirements are fulfilled.  3.3.2.2 Aircraft eligibility Please note that requested information is presented in ‘Comments’  3.3.2.3.1 Description of aircraft column. Write requested information and/or references to OM / equipment AFM to the ‘OM Reference’ column.  3.3.2.3.2 Training documentation  3.3.2.3.3 OMs and checklists  3.3.2.3.4 MEL considerations  3.3.2.3.5 Continuing airworthiness  3.3.4.2 Preflight planning  3.3.4.3 ABAS availability  3.3.4.4 General operating procedures  3.3.4.5 Aircraft with RNP selection capability  3.3.4.6 RNP 1 SID specific requirements  3.3.4.7 RNP 1 STAR specific requirements  3.3.4.8 Contingency procedures  3.3.5 Pilot knowledge and training  3.3.6 Navigation database

GM1 SPA.PBN.100 (c) The following RNAV and RNP navigation specifications are Please specify how the Yes PBN operations, paragraph (c) considered: requirements from EASA AMC 20- (7) - RNP APCH (7) RNP APCH (RNP Approach) 27 are fulfilled by filling out the attached PDF document: Non-precision approaches supported by GNSS and APV (approach procedure with vertical guidance) which are themselves divided in two types of APV approaches: APV Baro and APV SBAS. AMC 20-27A v2.2.pdf RNP APCH is charted as RNAV (GNSS). A minima line is provided for each of the available types of non-precision approaches and the APV Please specify how the procedure at a specific runway: requirements from EASA AMC 20- - non-precision approach – lateral navigation (LNAV) or localiser 28 are fulfilled by filling out the performance (LP) minima line; attached PDF document: - APV Baro - LNAV/VNAV (vertical navigation) minima line; and - APV SBAS - localiser performance with vertical guidance (LPV) minima line. AMC 20-28 v2.1.pdf Non-precision approaches to LNAV minima and APV approaches to LNAV/VNAV minima are addressed in AMC 20-27, “Airworthiness Approval and Operational Criteria for RNP approach (RNP APCH) operations including APV Baro VNAV operations”.

APV approaches to LPV minima are addressed in AMC 20-28 “Airworthiness Approval and. Operational Criteria for RNAV GNSS approach operation to LPV minima using SBAS”.

Non-precision approaches to LP minima have not yet been addressed in AMC 20.

Please specify how these requirements are fulfilled.  Please note that requested information is presented in the respective PDF document attached in ‘comments’ column. Please follow instructions given in those documents.

GM1 SPA.PBN.100 (c) The following RNAV and RNP navigation specifications are Please specify how the Yes PBN operations, paragraph (c) considered: requirements from EASA AMC 20- (8) - RNP AR APCH (8) RNP AR APCH (approach) 26 are fulfilled. Consider all its OPS requirements with emphasis on the RNP AR criteria have been developed to support RNP operations to following (see further details in RNP minima using RNP less than or equal to 0.3 NM or fixed radius AMC 20-26): turns (RF). The vertical performance is defined by a vertical error  9: Aircraft AFM / POH budget based upon Baro VNAV. Equivalent means of compliance  10: Operational criteria using SBAS may be demonstrated.  10.2: Flight operations documentation RNP AR APCH is charted as RNAV (RNP). A minima line is provided for  10.3: Qualification and training each available RNP value.  10.4: Navigation database management Acceptable Means of Compliance for RNP AR are provided in AMC20-  10.5: Reportable events 26 ‘Airworthiness Approval and Operational Criteria for RNP  10.7: RNP monitoring Authorisation Required (RNP AR) Operations’. programme

Each RNP AR approach requires a special approval.

Please specify how these requirements are fulfilled. Please note that requested information is presented in ‘Comments’ column. Write requested information and/or references to OM / AFM to the ‘OM Reference’ column.

GM1 SPA.PBN.100 Guidance material for the global performances specifications, PBN operations, paragraph (d) approval process, aircraft requirement (e.g. generic system performances, accuracy, integrity, continuity, signal-in-space, RNP Note: See table 1 in GM1 navigation specifications required for the on-board performance SPA.PBN.100. monitoring and alerting system), requirements for specific sensor technologies, functional requirements, operating procedures, flight crew knowledge and training and navigation databases integrity requirements, can be found in: (1) ICAO Doc 9613 Performance-Based Navigation (PBN) Manual; and (2) Table 1.

GM1 SPA.PBN.100 refers to ICAO Doc 9613 (rev 4). Therefore it is expected that the requirements of ICAO Doc 9613 are fulfilled. An important entity is ICAO Doc 9613 Volume II Part A Chapter 3 (i.e. from page II-A-3-1) under title ‘Safety Assessment Considerations’. Please familiarize with this chapter and take advantage of it in your own risk assessment. Trafi encourages the operators to prepare safety risk assessments for PBN operations. In certain cases Trafi will also require it. Please write in the ‘OM Reference’ or ‘ Comments’ column the availability and results of such risk assessments. Please also attach copies of such documents. SPA.PBN.105 To obtain a PBN operational approval from the competent authority, Yes PBN operational approval the operator shall provide evidence that: paragraph (a) (a) the relevant airworthiness approval of the RNAV system has been obtained;

Please write a reference (e.g. ind. no of Trafi’s airworthiness approval or AFM page number) to the approval to ‘OM Reference’ column. SPA.PBN.105 To obtain a PBN operational approval from the competent authority, PBN operational approval the operator shall provide evidence that: paragraph (b) (b) a training programme for the flight crew members involved in these operations has been established;

Please see specific requirements for each certain navigation specification as listed ahead. SPA.PBN.105 (c) operating procedures have been established specifying: PBN operational approval (1) the equipment to be carried, including its operating limitations paragraph (c)(1) and appropriate entries in the minimum equipment list (MEL);

 Please specify (in ‘OM Reference’ column) which items in the MEL have an influence on PBN operations.

SPA.PBN.105 (c) operating procedures have been established specifying: PBN operational approval (2) flight crew composition and experience requirements; paragraph (c)(2) Please see specific requirements for each certain navigation specification as listed ahead. SPA.PBN.105 (c) operating procedures have been established specifying: PBN operational approval (2) normal procedures; paragraph (c)(3) Please specify a list of exact OM references where normal procedures are presented. More detailed information for these are available for each certain navigation specification as listed ahead. These normal procedures should include for example (but not be limited only to these):  How is PBN considered in flight planning / preparation (e.g. check of documents, system ground tests, etc.)?  Procedures for confirming availability of GNSS and/or ground NAVAIDs.  Entering of flight plan to FMS/GPS.  Checking of flight plan.  How to handle conflicts between FMS/GPS database and navigation charts.  Use of position sensors (e.g. GPS vs. VOR/LOC, excluding of NAVAIDs, etc.)  CRM procedures (e.g. which FMS page is selected during flight phases, how to check ‘FROM’ waypoint is correct to ensure that correct runway is selected for SID, etc.)  Appropriate checks for different flight phases.  Use of AP and AT.  Limitations related to PBN.  etc. SPA.PBN.105 (c) operating procedures have been established specifying: PBN operational approval (2) contingency procedures; paragraph (c)(4) Please see specific requirements for each certain navigation specification as listed ahead. SPA.PBN.105 (c) operating procedures have been established specifying: PBN operational approval (5) monitoring and incident reporting; paragraph (c)(5) Please see specific requirements for each certain navigation specification as listed ahead.

SPA.PBN.105 (c) operating procedures have been established specifying: PBN operational approval (6) electronic navigation data management. paragraph (c)(6) Please specify a list of exact OM references where for example the following (but not limited only to the following) issues are considered:  Procedures for updating the FMS/GPS navigation databases.  On-going process for integrity checking of NAV database (e.g. does the supplier hold a LOA issued by appropriate regulatory authority, see EASA Opinion Nr. 01/2005).  If the NAV database is bought from a vendore, how is the database approved?  Monitoring of total system error (TSE or ANP, flight phase selection, IRS time limit, use of conventional NAVAIDs, etc.).

The italic text in the table above after the arrows (‘’) help operators to understand what are the main points that are expected so that the requirement is fulfilled. For self explanatory items there is no such guidance written. When Trafi performs oversight actions (such as audits), questions related to these items will be asked, since they have a strong influence on flight safety.

Trafi encourages all the operators to take full advantage of SMS processes to assess its PBN operations and to establish and document appropriate mitigation actions. For certain cases, before an operational approval can be granted, Trafi will require a copy of the associated risk analysis and even audit that analysis and the associated processes before the approval.

The approved PBN operations are listed in the operator’s AOC specification. List the requested PBN operations in the application carefully with such wording as they are requested to be included in the AOC specification.

11112015 16/16