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

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):______

This 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 this compliance list will be considered for improving and developing the list, and to make it more usable for the Operator and the Authority.

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 AMC3 ORO.MLR.100 and insert ‘Not applicable’ or ‘Intentionally blank’ where appropriate. [AMC and GM to Annex III Part ORO:GM1 ORO.MLR.100].

As for OM-A and OM-B, main titles must be in accordance with AMC3 ORO.MLR.100. For example: OM-A 12: Rules of the air.

The correlation between Rule References and the Operations Manuals shall be entered in the column OM/Document Reference.

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) put 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 column STATUS by the operator.

The column STATUS is for the Authority to note when the applicable part of OM is in accordance with the requirements.(OK/NO)

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

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

All applicable paragraphs in this compliance list should have either an OM reference or N/A, if not applicable.

There is a cross reference table which contains the provisions of the new Regulation on Air Operations – Regulation (EU) No 965/2012 - and the corresponding ones of EU-OPS and TGL 44 as well as JAR-OPS 3 (amendment 5), Section 1 and Section 2. One can find this tool from Flight Standards Website.


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

17.6.20131/15

Rule References / Requirement / OM Reference / Comments / Approval required / STATUS
Commission Regulation (EU) No 965/2012 / NOTE: If certain operations (such 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 authority / The competent authority for issuing a specific approval for the commercial air transport 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 specific approval / (a) The operator applying for the initial issue of 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 data established in accordance with Regulation (EC) No 1702/2003 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 procedures manual.
SPA.GEN.110 Privileges of an operator holding a specific approval / The scope of the activity that an operator holding an air operator certificate (AOC) is approved to conduct shall be documented and specified in the operations specifications to the AOC.
SPA.GEN.115 Changes to a specific approval / When the conditions of a specific approval are affected by changes, the operator shall provide the relevant documentation to the competent authority and obtain prior approval for the operation.
SPA.GEN.120 Continued validity of a specific approval / Specific approvals shall be issued for an unlimited duration and shall 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 data established in accordance with Regulation (EC) No 1702/2003.
---
Subpart B – Performance Based Navigation (PBN) Operations / Aircraft shall only be operated in designated airspace, on routes or in accordance with procedures where performance- based navigation (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)? / Yes
GM1 SPA.PBN.100
PBN operations, paragraph (a) / There are two kinds of navigation specifications: area navigation (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
PBN operations, paragraph (b)
Note: See table 1 in GM1 SPA.PBN.100. / The structure of RNAV and RNP navigation specifications can be classified by phases of flight as detailed in Table 1. Some of these special approvals are in current use, some are under development, and some apply to emerging standards for which AMC-20 material 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
PBN operations, paragraph (c)(1) - RNP10 / (c) The following RNAV and RNP navigation specifications are considered:
(1) Oceanic/Remote, RNAV10 (designated and authorised as RNP10)
Acceptable means of compliance for RNAV10 (RNP10) are provided in EASA AMC 20-12, “Recognition of FAA order 8400.12a for RNP10 Operations”. Although RNAV10 airspace is, for historical reasons, also called RNP10 airspace, there is no requirement for on-board monitoring and alerting systems. RNAV10 can support 50 NM track spacing. For an aircraft to operate in RNAV10 (RNP10) airspace it needs to be fitted with a minimum of two independent long range navigation systems (LRNSs). Each LRNS should in principle have a flight management system (FMS) that utilises positional information from either an approved global navigation satellite system (GNSS) or an approved inertial reference system (IRS) or mixed combination. The mix of sensors (pure GNSS, pure IRS or mixed IRS/GNSS) determines pre-flight and in-flight operation and contingencies in the 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. / Please specify how the requirements from EASA AMC 20-12 are fulfilled. Consider all its OPS requirements with emphasis on the following (see further details in AMC 20-12):
  • 4.4.1: Eligibility for RNP-10
  • 4.4.2: Aircraft Equipment and Minimum Equipment List
  • 4.4.3: 4.4.3 Operational Procedures and Training
  • 4.5: Position Updating
  • 4.5.1:Automatic radio position update
  • 4.5.2: Manual radio position update
  • 4.6: Incident reporting
/ Yes
GM1 SPA.PBN.100
PBN operations, paragraph (c)(2) - RNP4 / (c) The following RNAV and RNP navigation specifications are considered:
(2) Oceanic/Remote, RNP4
Guidance for this RNP standard is provided in ICAO Doc 9613. RNP4 is the oceanic/remote navigation specification to support 30 NM track spacing with ADS-C and CPDLC required. To meet this more accurate navigation requirement, two independent LRNS are required for which GNSS sensors are mandatory. If GNSS is used as a stand-alone LRNS, an integrity check is foreseen (fault detection and exclusion).Additional aircraft requirements include two long range communication systems (LRCSs) in order to operate in RNP4 designated airspace. The appropriate air information publication (AIP) should be consulted to assess coverage of HF and SATCOM. The additionalrequirements may include use of automatic dependent surveillance (ADS) and/or controller pilot data link communication (CPDLC).
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. / Please specify how the requirements fromICAO Doc 9613 (rev 4) Volume II Part C Chapter 4 (i.e. from page II-C-1-1) are fulfilled. Consider all its OPS requirements with emphasis on the following (see further details in ICAO Doc 9613):
  • 1.3.2.2 Aircraft eligibility
  • 1.3.2.3.1 Description of aircraft equipment
  • 1.3.2.3.2 Training documentation
  • 1.3.2.3.3 OMs and checklists
  • 1.3.2.3.4 MEL considerations
  • 1.3.2.3.5 Continuing airworthiness
  • 1.3.4.2 Preflight planning
  • 1.3.4.3 Availability of GNSS
  • 1.3.4.4 En route
  • 1.3.5 Pilot knowledge and training
  • 1.3.6 Navigation database
/ Yes
GM1 SPA.PBN.100
PBN operations, paragraph (c)(3) - B-RNAV / (c) The following RNAV and RNP navigation specifications are considered:
(3) RNAV5 (B-RNAV)
Acceptable means of compliance for RNAV5 are provided in AMC 20-4, “Airworthiness Approval and Operational Criteria for the Use of Navigation Systems in European Airspace Designated for the Basic-RNAV Operations”. No specific approval required.
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. / Please specify how the requirements from EASA AMC 20-4 are fulfilled. Consider all its OPS requirements with emphasis on the following (see further details in AMC 20-4):
  • 5.2 (a) Normal Procedures, RAIM
  • 5.2 (b) Normal Procedures, database validity
  • 5.2 (c) Normal Procedures, navigation monitoring
  • 5.3 Abnormal Procedures in the event of loss of GPS navigation capability (e.g. RAIM, alarm)
  • Annex 1 (RAIM prediction programme)
/ A specific operational approval is not required, but criteria must be fulfilled so that this can be included into AOC specification
GM1 SPA.PBN.100
PBN operations, paragraph (c)(4) - RNAV2 / (c) The following RNAV and RNP navigation specifications are considered:
(4) RNAV2
This is a non-European en-route standard. Guidance for this RNP standard is provided in ICAO Doc 9613.
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. / Please specify how the requirements from ICAO Doc 9613 (rev 4) Volume II Part B Chapter 3 (i.e. from page II-B-3-1) are fulfilled. Consider all its OPS requirements with emphasis on the following (see further details in ICAO Doc 9613):
  • 3.3.2.2 Aircraft eligibility
  • 3.3.2.3.1 Description of aircraft equipment
  • 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
/ Yes
GM1 SPA.PBN.100
PBN operations, paragraph (c)(5) - RNAV1 / P-RNAV / (c) The following RNAV and RNP navigation specifications are considered:
(5) RNAV1 (P-RNAV)
Acceptable means of compliance for RNAV1 (P-RNAV) are provided in JAA TGL-10 ‘Airworthiness and Operational approval for precision RNAV operations in designated European Airspace’, planned to be replaced by AMC 20 material.
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. / Please specify how the requirements from JAA TGL-10 rev 1 are fulfilled. Consider all its OPS requirements with emphasis on the following (see further details in JAA TGL-10):
  • 8.1: Compliance statement (see 8.1.a or 8.1.2).
  • 9: Aircraft flight manual
  • 10.2.1: Pre-flight planning
  • 10.2.2: Departure
  • 10.2.3: Arrival
  • 10.3: Contingency procedures
  • 10.4: Incident reporting
  • 10.5: Flight crew training
  • 10.6: Database integrity
  • 10.7: Flight operations documentation
/ Yes
GM1 SPA.PBN.100
PBN operations, paragraph (c)(6) - RNP1 / (c) The following RNAV and RNP navigation specifications are considered:
(6) Basic–RNP1
This is a future standard yet to be implemented. Guidance material is provided in ICAO Doc 9613.
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. / Please specify how the requirements from ICAO Doc 9613 (rev 4) Volume II Part C Chapter 3 (i.e. from page II-C-3-1) are fulfilled. Consider all its OPS requirements with emphasis on the following (see further details in ICAO Doc 9613):
  • 3.3.2.2 Aircraft eligibility
  • 3.3.2.3.1 Description of aircraft equipment
  • 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
/ Yes
GM1 SPA.PBN.100
PBN operations, paragraph (c)(7) - RNP APCH / (c) The following RNAV and RNP navigation specifications are considered:
(7) RNP APCH (RNP Approach)
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.
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 procedure at a specific runway:
- non-precision approach – lateral navigation (LNAV) or localiser performance (LP) minima line;
- APV Baro - LNAV/VNAV (vertical navigation) minima line; and
- APV SBAS - localiser performance with vertical guidance (LPV) minima line.
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 ‘Comments’ column. Write requested information and/or references to OM / AFM to the ‘OM Reference’ column. / Please specify how the requirements from EASA AMC 20-27 are fulfilled. Consider all its OPS requirements with emphasis on the following (see further details in AMC 20-27):
  • 9: Aircraft AFM / POH
  • 10: Operational criteria
  • 10.1: Flight operations documentation
  • 10.2: Flight crew training
  • 10.3: Aerodrome competence and operator verification
  • 10.4: Navigation database management
  • 10.5: Reportable events
Please specify how the requirements from EASA AMC 20-28 are fulfilled. Consider all its OPS requirements with emphasis on the following (see further details in AMC 20-28):
  • 9: Aircraft AFM / POH
  • 10: Operational criteria
  • 10.1: Flight operations documentation
  • 10.2: Flight crew training
  • 10.3: Aerodrome competence and operator verification
  • 10.4: Navigation database management
  • 10.4.3: Reportable events
/ Yes
GM1 SPA.PBN.100
PBN operations, paragraph (c)(8) - RNP AR APCH / (c) The following RNAV and RNP navigation specifications are considered:
(8) RNP AR APCH (approach)
RNP AR criteria have been developed to support RNP operations to RNP minima using RNP less than or equal to 0.3 NM or fixed radius turns (RF). The vertical performance is defined by a vertical error budget based upon Baro VNAV. Equivalent means of compliance using SBAS may be demonstrated.
RNP AR APCH is charted as RNAV (RNP). A minima line is provided for each available RNP value.
Acceptable Means of Compliance for RNP AR are provided in AMC20-26 ‘Airworthiness Approval and Operational Criteria for RNP Authorisation Required (RNP AR) Operations’.
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. / Please specify how the requirements from EASA AMC 20-26 are fulfilled. Consider all its OPS requirements with emphasis on the following (see further details in AMC 20-26):
  • 9: Aircraft AFM / POH
  • 10: Operational criteria
  • 10.2: Flight operations documentation
  • 10.3: Qualification and training
  • 10.4: Navigation database management
  • 10.5: Reportable events
  • 10.7: RNP monitoring programme
/ Yes
GM1 SPA.PBN.100
PBN operations, paragraph (d)
Note: See table 1 in GM1 SPA.PBN.100. / Guidance material for the global performances specifications, approval process, aircraft requirement (e.g. generic system performances, accuracy, integrity, continuity, signal-in-space, RNP navigation specifications required for the on-board performance 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
PBN operational approval
paragraph (a) / To obtain a PBN operational approval from the competent authority, the operator shall provide evidence that:
(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. / Yes
SPA.PBN.105
PBN operational approval
paragraph (b) / To obtain a PBN operational approval from the competent authority, the operator shall provide evidence that:
(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
PBN operational approval
paragraph (c)(1) / (c) operating procedures have been established specifying:
(1) the equipment to be carried, including its operating limitations 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
PBN operational approval
paragraph (c)(2) / (c) operating procedures have been established specifying:
(2) flight crew composition and experience requirements;
Please see specific requirements for each certain navigation specification as listed ahead.
SPA.PBN.105
PBN operational approval
paragraph (c)(3) / (c) operating procedures have been established specifying:
(2) normal procedures;
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
PBN operational approval
paragraph (c)(4) / (c) operating procedures have been established specifying:
(2) contingency procedures;
Please see specific requirements for each certain navigation specification as listed ahead.
SPA.PBN.105
PBN operational approval
paragraph (c)(5) / (c) operating procedures have been established specifying:
(5) monitoring and incident reporting;
Please see specific requirements for each certain navigation specification as listed ahead.
SPA.PBN.105
PBN operational approval
paragraph (c)(6) / (c) operating procedures have been established specifying:
(6) electronic navigation data management.
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.