OFFICE OF THE DIRECTOR GENERAL OF CIVIL AVIATION

Transcription

1 GOVERNMENT OF INDIA OFFICE OF THE DIRECTOR GENERAL OF CIVIL AVIATION TECHNICAL CENTRE, OPP. SAFDARJUNG AIRPORT, NEW DELHI CIVIL AVIATION REQUIREMENT SECTION 8 - AIRCRAFT OPERATIONS SERIES 'O', PART VI ISSUE I, 01 ST AUG 2011 EFFECTIVE: FORTHWITH SUB: PERFORMANCE BASED NAVIGATION (PBN) 1. INTRODUCTION 1.1 All navigation systems can be described in terms of performance. For example, a ground based navigation aid such as VOR delivers a measurable level of performance which is applied in terms of accepted navigational tolerances. PBN operations are similarly based on navigation performance, but the concept of performance is fundamentally different. Whereas an operation based on a ground based navigation aid is dependent upon the performance of the radiated signal and the ability of an aircraft to accurately utilise that signal, in Performance Based Navigation the performance itself is specified and the navigation system is required to meet the minimum level of performance. In principle any method of navigation that achieves the specified level of navigation performance is acceptable. However, in practice a particular navigation system is required in some cases in order to meet the requirements of a particular navigation specification 1.2 The Performance Based Navigation (PBN) concept specifies system performance requirements in terms of accuracy, integrity, availability, continuity and functionality needed for the proposed operations in the context of a particular Airspace Concept, when supported by the appropriate navigation infrastructure. In that context, the PBN concept represents a shift from sensor-based to performance-based navigation. Performance requirements are identified in navigation specifications which also identify the choice of navigation sensors and equipment that may be used to meet the performance requirements.

2 1.3 This CAR is issued under the provisions of Rule 133A of the Aircraft Rules, 1937 for information, guidance and compliance by the concerned s operating air transport services to, through and within the PBN airspace. The contents of the CAR are consistent with the provisions of ICAO Annex 6 Operation of Aircraft and Doc 9613 PBN Manual. Guidance for implementing and obtaining approval for RNAV1, RNAV2, RNAV 5, RNP4, Basic RNP1, RNP APCH, RNP AR APCH, etc. have been specified in Volume II of ICAO Doc 9613 PBN Manual and as an Appendix to this CAR. 2. DEFINITIONS Performance-based navigation (PBN) - Area navigation based on performance requirements for aircraft operating along an ATS route, on an instrument approach procedure or in a designated airspace. Navigation specification - A set of aircraft and flight crew requirements needed to support performance-based navigation operations within a defined airspace as described in the ICAO PBN Manual (DOC 9613). Required navigation performance (RNP) specification - A navigation specification based on area navigation that includes the requirement for performance monitoring and alerting, designated by the prefix RNP. Area navigation (RNAV) specification - A navigation specification based on area navigation that does not include the requirement for performance monitoring and alerting, designated by the prefix RNAV. 3. PERFORMANCE BASED NAVIGATION 3.1 No aircraft shall be operated along ATS routes, on an instrument approach procedure, or in a designated airspace where a Navigation Specification has been prescribed unless: The has received authorization from the Director General The aircraft is equipped with the navigation equipment to enable it to operate in accordance with the prescribed Navigation Specification; and The aircraft is equipped with navigation equipment that continuously provides information to the flight crew of adherence to or departure from track with respect to the required degree of accuracy at any point along that track. 3.2 No shall operate an aircraft unless it has sufficient navigation equipment that will enable the aircraft to navigate in accordance with

3 Paragraph 3.1 above, such that in the event of the failure of any piece of navigation equipment at any stage of flight, the remaining equipment will enable the aircraft to continue to a destination or an alternate destination. 4. ELECTRONIC NAVIGATION DATA MANAGEMENT 4.1 No shall employ electronic navigation data products that have been processed for application in the air and on the ground unless the FSD has approved: The s procedures for ensuring that the process applied and the products delivered have acceptable standards of integrity and that the products are compatible with the intended function of the equipment that will use them; The s program for continual monitoring of both process and products; and The s procedures to ensure the timely distribution and insertion of current and unaltered electronic navigation data to all aircraft that require it. 5. INITIAL PBN OPERATIONS TRAINING 5.1 No person shall serve nor shall any AOP holder use a person as a flight crew member or flight operations officer (if applicable) unless he or she has completed the appropriate initial PBN operations training curriculum approved by the FSD. 5.2 The initial PBN training curriculum for each Navigation Specification shall ensure that each pilot and flight operations officer (if applicable) is qualified in the type of operation in which he or she serves and in any specialized or new equipment, procedures, and techniques, such as: Knowledge of specialized navigation procedures; Knowledge of specialized equipment; SIDs and STARs (if applicable); The ability of the airborne equipment to fly the designed flight path. This may involve pilot intervention where the equipment functionality is limited; Management of changes (procedure, runway, track, etc.); Turn management (turn indications, airspeed & bank angle, lack of guidance in turns); Route modification (insertion/deletion of waypoints, direct to waypoint) and restrictions on route modification; Intercepting route, radar vectors; and

4 5.2.9 Where GNSS is used, flight crews shall be trained in GNSS principles. 5.3 Each shall require each pilot and flight operations officer (if applicable) to complete a demonstration of competence to a defined standard of knowledge and performance. EK Bharat Bhushan Director General of Civil Aviation

5 APPENDIX TO CAR SECTION 8 - AIRCRAFT OPERATIONS, SERIES O, PART VI, ISSUE I, 01ST AUG PBN SUB: GUIDANCE ON PROCESS FOR PBN OPERATIONAL APPROVAL 1. Introduction The operational approval process for established navigation technologies is well known and understood and there is general consistency world-wide in the issue of operational approvals. As Performance Based Navigation is a relatively recent development, some time and experience is required to develop a thorough understanding of PBN operations, the associated technology and the approval process for various navigation specifications. The applying for operational approval must be familiar with ICAO Doc 9613 PBN Manual. 2. Purpose The purpose of this Appendix is to provide guidance for s to obtain PBN operational approvals and supplements CAR Section 8 - Aircraft Operations, Series O, Part VI, Issue I, 01ST AUG PBN. 3. DEFINITIONS Aircraft-based augmentation system (ABAS) - A system which augments and/or integrates the information obtained from the other GNSS elements with information available on board the aircraft. The most common form of ABAS is the receiver autonomous integrity monitoring (RAIM). Area navigation (RNAV) - A navigation method that allows aircraft to operate on any desired flight path within the coverage of ground- or space-based navigation aids, or within the limits of the capability of self-contained aids, or a combination of both methods. Flight technical error (FTE) - The FTE is the accuracy with which an aircraft is controlled as measured by the indicated aircraft position with respect to the indicated command or desired position. It does not include blunder errors. Global navigation satellite system (GNSS) - A generic term used by the International Civil Aviation Organization (ICAO) to define any global position, speed, and time determination system that includes one or more main satellite constellations, such as GPS and the global navigation satellite system (GLONASS), aircraft receivers and several integrity monitoring systems, including aircraft-based augmentation systems (ABAS), satellite-based augmentation systems (SBAS), such as the wide area augmentation systems (WAAS), and ground-based augmentation systems (GBAS), such as the local area augmentation system (LAAS). Global positioning system (GPS) - The global positioning system (GPS) of

6 the United States is a satellite-based radio navigation system that uses precise distance measurements to determine the position, speed, and time in any part of the world. The GPS is made up by three elements: the spatial, the control, and the user elements. The GPS spatial segment nominally consists of, at least, 24 satellites in 6 orbital planes. The control element consists of 5 monitoring stations, 3 ground antennas, and one main control station. The user element consists of antennas and receivers that provide the user with position, speed, and precise time. Navigation specifications - Set of aircraft and flight crew requirements needed to support performance-based navigation operations in a defined airspace. There are two kinds of navigation specifications: Required Navigation Performance (RNP) Specification - Area navigation specification that includes the performance control and alerting requirement, designated by the prefix RNP; e.g., RNP 4, RNP APCH, RNP AR APCH. Area Navigation (RNAV) Specification - Area navigation specification that does not include the performance control and alerting requirement, designated by the prefix RNAV; e.g., RNAV 5, RNAV 2, RNAV 1. Navigation system error (NSE) - The difference between the true position and the estimated position. Path definition error (PDE) - The difference between the defined path and the desired path at a given place and time. Performance-based navigation (PBN) - Performance-based area navigation requirements applicable to aircraft conducting operations on an ATS route, on an instrument approach procedure, or in a designated airspace. Receiver autonomous integrity monitoring (RAIM) - A technique used in a GPS receiver/processor to determine the integrity of its navigation signals, using only GPS signals or GPS signals enhanced with barometric altitude data. This determination is achieved by a consistency check between redundant pseudo-range measurements. At least one additional available satellite is required with respect to the number of satellites that are needed for the navigation solution. RNP operations - Aircraft operations that use an RNP system for RNP applications. RNP system - An area navigation system that supports on-board performance control and alerting. Standard instrument arrival (STAR) - A designated instrument flight rules (IFR) arrival route linking a significant point, normally on an air traffic service (ATS) route, with a point from which a published instrument approach procedure can be commenced.

7 Standard instrument departure (SID) - A designated instrument flight rule (IFR) departure route linking the aerodrome or a specified runway of the aerodrome with a specified significant point, normally on a designated ATS route, at which the en-route phase of a flight commences. Total system error (TSE) - The difference between the true position and the desired position. This error is equal to the sum of the vectors of the path definition error (PDE), the flight technical error (FTE), and the navigation system error (NSE). Note. - FTE is also known as path steering error (PSE), and the NSE as position estimation error (PEE). Way-point (WPT) - A specified geographical location used to define an area navigation route or the flight path of an aircraft employing area navigation. Waypoints area identified as either: Fly-by way-point - A way-point which requires turn anticipation to allow tangential interception of the next segment of a route or procedure. Fly over way-point - A way-point at which a turn is initiated in order to join the next segment of a route or procedure 4. General Requirements The PBN Manual contains a statement of the operational requirements for each type of operation, and while it is necessary that the Operational Approval evaluation determines that the proposed operation meets the minimum requirements, it is also necessary that an assessment is made of the s capability to meet the operational intent of the particular navigation specification. 5. Responsibility for Operational Approval Evaluation Overall responsibility for the evaluation of an operational approval application will be assigned to a Flight Operations Inspector (FOI), who is experienced and trained in PBN operations. The assigned inspector will have access to other specialist expertise where required. It should be recognized that PBN is an operational concept and the primary task is to determine that the applicant s operating practices, procedures and training are adequate. Although some evaluation of aircraft eligibility and airworthiness is required during the operational approval process, PBN operational approval is primarily an operational task. In some cases, particularly where documentation is available to demonstrate the aircraft eligibility, the FOI may be satisfied that any airworthiness issues are addressed and assistance from airworthiness experts may not be necessary. However in most cases issues of configuration control, ongoing maintenance, minimum equipment lists, training of maintenance personnel etc., should be assessed by qualified airworthiness personnel in consultation with the FOI.

8 6. Issue of Approval To obtain a PBN operational approval from FSD, the shall provide evidence that: (a) the relevant airworthiness approval of the RNAV system has been obtained; (b) a training programme for the flight crew members involved in these operations has been established; and (c) operating procedures have been established specifying: (i) the equipment to be carried, including its operating limitations and appropriate entries in the minimum equipment list (MEL); (ii) flight crew composition and experience requirements; (iii) (iv) (v) normal procedures; contingency procedures; monitoring and incident reporting; and 6. electronic navigation data management. The approval will consist of the issue of an operations specification (OPSPEC) or a Letter of Authorization. The OPSPECs would be annotated as shown in the table below to show the individual PBN operational approvals granted. The remarks as noted would also be included on the OPSEC to assist in identifying existing approvals which are equivalent to PBN navigation specifications. For example, it should be noted (as shown) that an RNAV 5 approval is applicable in B-RNAV airspace. This will assist regulators of other states to recognize and accept OPSECS issued in accordance with PBN navigation specifications. However issued the approval will commonly include conditions, as PBN operations may be conducted using a variety of aircraft, systems and procedures which have yet to be universally standardized. It is not necessary to issue separate airworthiness and operational approvals for PBN operations. The operational approval is issued on the basis that an assessment is made or the airworthiness aspects of the operation. 7. Related Material DGCA CAR Section 8 Aircraft Operations Series O Part VI PBN DGCA FOI Manual (Annexure - PBN Operational Approval) ICAO Annexure 6 - Operation of Aircraft ICAO Annexure 10 - Aeronautical Telecommunications

9 ICAO Doc 9613 PBN Manual ICAO Doc 9905 RNP AR Procedure Design Manual ICAO Doc 8168 PANS-OPS FAA AC Airworthiness Approval of Positioning and Navigation Systems FAA AC Acceptance of Data Processes and Associated Navigation Databases FAA AC A US En-route and Terminal RNAV Operations FAA AC A Approval Guidance for RNP Procedures with AR FAA AC Approval Guidance for RNP Operations and Barometric Vertical Navigation in US National Airspace System EASA AMC Airworthiness Approval and Operational Criteria for RNP APCH Operations including APV BARO-VNAV Operations EASA AMC Airworthiness Approval and Operational Criteria for RNP AR Operations JAA TGL 10 Airworthiness Approval and Operational Criteria for P-RNAV in European Airspace JAA TGL 2 Rev 1 Airworthiness Approval and Operational Criteria for Use of Navigation Systems in European Airspace Designated for Basic RNAV Operations

10 OPERATIONS SPECIFICATIONS (subject to the approved conditions in the Operations Manual) Issuing Authority Contact Details. Telephone: ; Fax: ; AOP#: Operator Name: Trading Name Date: Signature: Aircraft Model: Types of operation: Area of operation: Commercial air transportation Passengers; Cargo; Other: Special Limitations: Special Yes No Specific Approvals Remarks Authorizations: Dangerous Goods Low Visibility Operations Approach and Landing CAT. RVR: m DH: ft Take-off RVR: m RVSM N/A ETOPS N/A Maximum Diversion Time: minutes Navigation RNP 10 Specifications for PBN Operations RNAV 5 Also valid for B-RNAV routes RNAV 1 and RNAV 2 RNP 4 Also valid for P-RNAV routes Basic RNP 1 RNP APCH [LNAV, LNAV/VNAV, LPV, LP] 1 RNP AR APCH 1 List approach types approved. RNP APCH [LNAV] also valid for approach procedures designated as RNAV (GNSS) Continuing Airworthiness Others

11 8. Job Aids Job aids have been developed to assist the process of PBN operational approvals. The job aids provide both inspectors and s with guidance on the documentation required to be included in an s application, and the items that must be assessed by the FOI in order for an operational approval to be issued. The job aids also serve as means of recording the documentation process. The job aids summarize the key elements to be assessed, and should be used as a guide to the approval process but frequent reference to the ICAO Doc 9613 PBN Manual and DGCA FOI Manual (Annexure on PBN Operational Approval) will be required to identify detailed requirements for approval. 9. Using the Job Aids Job aids are divided into four sections as follows: Section 1- Information on Aircraft and Operator Identification contains the general information identifying the and aircraft applicable to the particular application. This section should be completed by the applicant. In general a PBN operational approval can be issued according to aircraft type and model and it is not necessary to identify specific aircraft by registration marks or serial number unless there are significant differences in installed equipment in the s fleet. Section 2- Operator Application (Items and Documents) identifies the documentation that the must provide in support of the application. As full documentation is necessary for the FOI to conduct a comprehensive assessment, applications which are not supported by adequate documentation would be referred back to the before the detailed assessment of an application is commenced. The applicant should insert in the column headed Indication of inclusion by the the relevant references in the applicant s supporting documentation that demonstrate compliance. The FOI, after assessing the information provided by the applicant, completes the Comments by the Inspector column by noting as follows: 1) Satisfactory 2) Additional information required, including items which require further action 3) Other comments Section 3- Guide for Determining Aircraft Eligibility provides the FOI with guidance on the basis for establishment of compliance with the PBN Manual aircraft eligibility requirements. The applicant should identify the specific reference(s) in the s documentation that demonstrate compliance with each requirement. Where there are more than one means of compliance the applicant should note Not Applicable where appropriate.

12 The FOI would indicate in the comments column as follows: 1) Compliant 2) Partially compliant, including items which require further action 3) Not compliant 4) Other remarks Where applicable the FOI would attach a statement supporting the assessment including any remarks relevant to the assessment including any alternative means of compliance, conditions related to the approval or reasons for assessing the application as non-compliant. Section 4- Procedures for PBN Operations provides a checklist to identify that the s procedures meet the requirements for the specific PBN operation. The must identify that each requirement is appropriately documented and applied to the conduct of the particular PBN operation. Procedures must be contained in the s Flight Crew Training Manual, Flight Crew Operations Manual, checklists, and instructions to operational personnel or equivalent documents. Where appropriate, reference may be made to manufacturer documentation provided that operational personnel have ready access to relevant documents. All items on the job aid must be identified as satisfactory or compliant (subject to any appropriate conditions or approved exemptions) before an operational approval is issued. 10. Layout of Job Aids The Job Aids have been placed in the form of Annexures as below: Annexure 1 - RNAV 10 (RNP10) Annexure 2 - RNAV 5 Annexure 3 - RNAV 1 and 2 Annexure 4 - RNP 4 Annexure 5 - Basic RNP 1 Annexure 6 - RNP APCH Annexure 7 - APV/Baro-VNAV Annexure 8 - RNP AR APCH

13 ANNEXURE 1 APPENDIX TO CAR SECTION 8 SERIES O PART VI, ISSUE I, 01ST AUG 2011 RNAV 10 JOB AID APPLICATION TO CONDUCT RNAV 10 (RNP 10) 1. Introduction This Job Aid was developed to provide guidance on the process to be followed in order to obtain an RNAV 10 (RNP 10) approval. It should be used as an aid for the approval process but frequent reference to the ICAO Doc 9613 PBN Manual and DGCA FOI Manual (Annexure - PBN Operational Approval) will be required. PBN Manual Volume II, Part B, Chapter 1 contains detailed guidance on the implementation of RNAV 10 (Designated and Authorized as RNP 10). 2. Purpose of the Job Aid 2.1 To give information on the main RNAV 10 reference documents. 2.2 To provide tables showing the contents of the application, the associated reference paragraphs, the place in the application of the where RNAV 10 elements are mentioned and columns for inspector comments and follow-up on the status of various elements of RNAV Actions Recommended for the Inspector and Operator 3.1 At the pre-application meeting with the, the inspector reviews the basic events of the RNAV 10 approval process described in Section 1 of this Job Aid, in order to provide an overview of the approval process events. 3.2 The inspector reviews this Job Aid with the in order to establish the form and content of the RNAV 10 approval application. 3.3 The uses this Job Aid as a guide to collect the documents of the RNAV 10 application. 3.4 The inserts in the Job Aid references showing in what part of its documents are the RNAV 10 elements located. 3.5 The submits the Job Aid and the application to the inspector (with the required documents). 3.6 The inspector indicates in the Job Aid whether an item is in compliance or needs corrective action. 3.7 The inspector informs the as soon as possible when a corrective action by the is required. 3.8 The provides the inspector with the revised material when so requested. 3.9 DGCA provides the with the operational specification (air s) or a letter of authorization (others), as applicable, when the tasks and documents have been completed.

14 SECTION 1 - INFORMATION ON THE IDENTIFICATION OF AIRCRAFT AND OPERATORS NAME OF THE OPERATOR: is applying for RNAV 10 (RNP 10) Operations Approval. Aircraft Aircraft Registration List relevant make and model manufacturer, (required only if installed of related navigation model, and series equipment varies equipment between model and series) DATE OF PRE-APPLICATION MEETING DATE ON WHICH THE APPLICATION WAS RECEIVED DATE ON WHICH THE OPERATOR INTENDS TO BEGIN RNAV 10 (RNP 10) OPERATIONS

15 SECTION 2 - OPERATOR APPLICATION (ITEMS AND DOCUMENTS) Indication of Item Title of document inclusion by the Comments by the Inspector Airworthiness documents showing aircraft eligibility for RNAV 10 (RNP 10). 1 AFM, AFM revision, AFM supplement, or Type certificate data sheet (TCDS) showing that the LRNS is eligible for RNAV 10 (RNP 10). Aircraft modified to meet RNAV 10 (RNP 10) standards. 2 Documentation on aircraft inspection and/or modification, if applicable. Maintenance program For aircraft with established LRNS maintenance practices, the list of references of 3 the document or program. 4 For newly installed LRNS provide LRNS maintenance practices for review. Minimum Equipment List (MEL) if applicable showing provisions for LRNS Training programme for flight crews, flight 5 dispatchers, and maintenance personnel as applicable. 6 Operating policies and procedures including relevant section of Operations Manuals and checklists attached to the application, applicable to RNAV 10 Navigation database (if carried) 7 Details of the navigation data validation programme.

16 SECTION 3 - GUIDE FOR DETERMINING RNAV 10 (RNP 10) AIRCRAFT ELIGIBILITY Reference Location in paragraphs the Item Topics ICAO Doc Documents Comments 9613 of the Vol II Part B 1 Eligibility Method 1 - Eligibility of aircraft 1 through RNP certification. (RNP compliance documented in the AFM). Eligibility Method 2 - Eligibility of aircraft 2 through previous certification of the navigation system. Eligibility Method 3 - Eligibility of aircraft 3 through data collection Aircraft Equipment Dual Long Range Navigation Systems Dual GNSS GNSS approved as primary means of avigation (AC or equivalent) Multi-sensor systems into which the GNSS is integrated (AC or equivalent) Complies with regulations/advisory information for use of GNSS for primary oceanic/remote performance Approved FDE prediction programme Dual INS or IRS INSs or IRUs approved according to 14 CFR, Part 121, Appendix G (time limit hours). INSs or IRUs approved for MNPS operations in the North Atlantic or RNAV operation in Australia (time limit 6.2 hours)

17 Reference Location in paragraphs the Item Topics ICAO Doc Documents Comments 9613 of the Vol II Part B 1 Application for extended time limit Operator route evaluation conducted Single IRS or IRU and Single GNSS INS/IRU approved to 14 CFR Part 121 Appendix G or equivalent GNSS authorized for oceanic/remote (TSO C129a with FDE, TSO C145a/146a, or equivalent) Approved FDE prediction programme

18 SECTION 4 - PROCEDURES FOR RNAV 10 (RNP 10) OPERATIONS Item Operating Procedures Reference paragraphs ICAO Doc 9613 Vol II Part B 1 Location in the Documents of the Comments 1 Flight planning Verify that aircraft has been approved for RNAV 10 (RNP 10) operations Verify that two LRNS are operational Verify that the RNAV 10 (RNP 10) time limit has been taken into account (aircraft (a) equipped with only INS/IRU). Verify requirements for GNSS, such as FDE, if applicable to the operation. Insert the letter R in Box 10 of the ICAO flight plan If required, take into account any operational restriction related to RNAV 10 (RNP 10) approval for a specific navigation system. 2 Pre-flight procedures Review of maintenance logs and forms for LRNS status (b) (c) (a) Review the emergency procedures for operations in RVAV 10 (RNP 10) airspace or routes (c) 3 En-route procedures Before oceanic point of entry verify at least two LRNS capable of navigating in RNAV 10 (RNP 10). If not consider using an alternate route or initiating a deviation. Before entering oceanic airspace, check aircraft position as accurately as possible

19 Item Operating Procedures Reference paragraphs ICAO Doc 9613 Vol II Part B 1 Location in the Documents of the Comments using external navigation aids. Cross-check procedures in order to identify navigation errors in advance and prevent the aircraft from inadvertently deviating from the routes authorized by the ATC. Notify the ATC of any degradation or failure of the navigation equipment below the navigation performance requirements, or of any deviation required for a contingency procedure. Operator procedures for use of a lateral deviation indicator, an FD or an AP in lateral navigation mode (LNAV) for RNP 10 operations. Operator procedures for limiting FTE to +/- ½ navigation accuracy Operator procedures for manual updating of position (if approved)

20 ANNEXURE 2 TO APPENDIX TO CAR SECTION 8 SERIES O PART VI, ISSUE I, 01ST AUG 2011 RNAV 5 JOB AID APPLICATION TO CONDUCT RNAV 5 1. Introduction This Job Aid was developed to provide s, and inspectors with guidance on the process to be followed in order to obtain an RNAV 5 approval. It should be used as an aid for the approval process but frequent reference to the ICAO Doc 9613 PBN Manual and DGCA FOI Manual (Annexure - PBN Operational Approval) will be required. Volume II, Part B, Chapter 2 contains detailed guidance on the implementation of RNAV Purpose of the Job Aid 2.1 To give s and inspectors information on the main RNAV 5 reference documents. 2.2 To provide tables showing the contents of the application, the associated reference paragraphs, the place in the application of the where RNAV 5 elements are mentioned and columns for inspector comments and follow-up on the status of various elements of RNAV Actions Recommended for the Inspector and Operator 3.1 At the pre-application meeting with the, the inspector reviews the basic events of the RNAV 5 approval process described in Section 1 of this Job Aid, in order to provide an overview of the approval process events. 3.2 The inspector reviews this Job Aid with the in order to establish the form and content of the RNAV 5 approval application. 3.3 The uses this Job Aid as a guide to collect the documents of the RNAV 5 application. 3.4 The inserts in the Job Aid references showing in what part of its documents are the RNAV 5 elements located. 3.5 The submits the Job Aid and the application to the inspector (with the required documents). 3.6 The inspector indicates in the Job Aid whether an item is in compliance or needs corrective action. 3.7 The inspector informs the as soon as possible when a corrective action by the is required. 3.8 The provides the inspector with the revised material when so requested. 3.9 DGCA provides the with the operational specification (air s) or a letter of authorization (others), as applicable, when the tasks and documents have been completed.

21 SECTION 1 - INFORMATION ON THE IDENTIFICATION OF AIRCRAFT AND OPERATORS NAME OF THE OPERATOR: is applying for RNAV 5 Operations Approval. Aircraft Aircraft Registration List relevant make and model of manufacturer, (required only if related navigation equipment model, and series installed equipment varies between model and series) DATE OF PRE-APPLICATION MEETING DATE ON WHICH THE APPLICATION WAS RECEIVED DATE ON WHICH THE OPERATOR INTENDS TO BEGIN RNAV 5 OPERATIONS

22 SECTION 2 - OPERATOR APPLICATION (ITEMS AND DOCUMENTS) Indication of Item Title of document inclusion by the Comments by the Inspector Airworthiness documents to determine aircraft eligibility 1 Airworthiness documents that establish the aircraft and the navigation system have been approved for RNAV 5 operations. 2 3 RNAV 5 system requirements Documents that show the aircraft equipment One (1) RNAV system comprising of: one or a combination of the following navigation sensors: VOR/DME, DME/DME, INS or IRS, and GNSS; an Area Navigation (RNAV) computer; a Control Display Unit (CDU); and a navigation display(s) or instrument(s) e. g., Navigation Display (ND), Heading Situation Indicator (HSI) or Course Deviation Indicator (CDI). Maintenance program 1. For Aircraft with established RNAV or GPS stand-alone maintenance practices provide document references. 2. For newly installed RNAV or GPS stand-alone provide maintenance practices for review Minimum equipment list (MEL) if applicable showing provisions for RNAV 5 systems. Training Training program for flight crews, flight dispatchers, and maintenance personnel as applicable Operational policies and procedures Operations manual and checklists or sections to be attached to the application, corresponding to RNAV 5 operating procedures and policies.

23 Indication of Item Title of document inclusion by the Comments by the Inspector Navigation database (if carried) 7 Details of the navigation data validation programme. SECTION 3 - GUIDE FOR DETERMINING RNAV 5 AIRCRAFT ELIGIBILITY Reference paragraphs Location in Item Topics ICAO Doc Documents Comments 1 Aircraft eligibility 2 the 9613 of the Vol II Part B 2 Aircraft approved for B-RNAV Aircraft with an approved statement of compliance Aircraft with statement by the manufacturer Aircraft and System requirements - one of the following VOR/DME or DME/DME system INS or IRS GNSS a) TSO C129 with pseudo range step detection and health word checking; or b) TSO C129 (a) or TSO C145 ( ) or TSO C146( ) or equivalent Availability of conventional navigation 3 equipment as a back-up in the event of loss of GNSS, if required by the State. 4 RNAV 5 system functional requirements

24 SECTION 4 - PROCEDURES FOR RNAV 5 OPERATIONS Item Operating Procedures Reference paragraphs ICAO Doc 9613 Vol II Part B 2 Location in the Documents of the Comments 1 Flight planning Verify aircraft is approved for RNAV operation File appropriate flight plan suffixes for RNAV 5 Verify that GNSS or ground-based navigation aids required for RNAV 5 operations are available for the route and period of operations, including any contingencies Verify that database is current and appropriate for the route (if carried) Confirm availability of GNSS (if carried). Revise flight planning if a continuous loss of integrity of more than 5 minutes is predicted 2 General operating procedures Operator procedures to ensure flight crew do not request, or file a flight plan for RNAV 5 routes unless they meet all the criteria in the relevant State documents Operator procedures to ensure any manufacturer requirements, to meet the RNAV 5 performance requirements For RNAV 5 routes - procedures for the use of a lateral deviation indicator, a FD or an AP in the lateral navigation mode. Operator procedures for setting lateral deviation scale (where applicable)

25 Item Operating Procedures Reference paragraphs ICAO Doc 9613 Vol II Part B 2 Location in the Documents of the Comments Operator procedures for limiting FTE to +/- ½ navigation accuracy Operator procedures for rejoining route following ATC course assignment Contingency Procedures Notification of ATC when RNAV performance ceases to meet the requirements for RNAV 5 Operator procedures for use of GNSS; a) Loss of integrity monitoring function b) Integrity alert a) b)

26 ANNEXURE 3 TO APPENDIX TO CAR SECTION 8 SERIES O PART VI, ISSUE I, 01ST AUG 2011 RNAV 1 AND RNAV 2 JOB AID APPLICATION TO CONDUCT RNAV 1 AND RNAV 2 OPERATIONS 1. Introduction This Job Aid was developed to provide guidance on the process to be followed in order to obtain an RNAV 1 and RNAV 2 approval. It should be used as an aid for the approval process but frequent reference to the ICAO Doc 9613 PBN Manual and DGCA FOI Manual (Annexure - PBN Operational Approval) will be required. Volume II, Part B, Chapter 3 contains detailed guidance on the implementation of RNAV 1 and RNAV Purpose of the Job Aid 2.1 To give s and inspectors information on the main RNAV 1 and RNAV 2 reference documents. 2.2 To provide tables showing the contents of the application, the associated reference paragraphs, the place in the application of the where RNAV 1 and RNAV 2 elements are mentioned and columns for inspector comments and follow-up on the status of various elements of RNAV 1 and RNAV Actions Recommended for the Inspector and Operator 3.1 At the pre-application meeting with the, the inspector reviews the basic events of the RNAV 1 and RNAV 2 approval process described in Section 1 of this Job Aid, in order to provide an overview of the approval process events. 3.2 The inspector reviews this Job Aid with the in order to establish the form and content of the RNAV 1 and RNAV 2 approval application. 3.3 The uses this Job Aid as a guide to collect the documents of the RNAV 1 and RNAV 2 application. 3.4 The inserts in the Job Aid references showing in what part of its documents are the RNAV 1 and RNAV 2 elements located. 3.5 The submits the Job Aid and the application to the inspector (with the required documents). 3.6 The inspector indicates in the Job Aid whether an item is in compliance or needs corrective action. 3.7 The inspector informs the as soon as possible when a corrective action by the is required. 3.8 The provides the inspector with the revised material when so requested. 3.9 DGCA provides the with the operational specifications (air s) or a letter of authorization (others), as applicable, when the tasks and documents have been completed.

27 SECTION 1 - INFORMATION ON AIRCRAFT AND OPERATOR IDENTIFICATION NAME OF THE OPERATOR: is applying for RNAV 1 and RNAV 2 Operations Approval. Aircraft Aircraft Registration List relevant make and model manufacturer, (required only if of related navigation model, and series installed equipment equipment varies between model and series DATE OF PRE-APPLICATION MEETING DATE ON WHICH THE APPLICATION WAS RECEIVED DATE ON WHICH THE OPERATOR INTENDS TO BEGIN RNAV 1 AND RNAV 2 OPERATIONS

28 SECTION 2 - OPERATOR APPLICATION (ITEMS AND DOCUMENTS) Indication of Item Title of document inclusion by the Comments by the Inspector Airworthiness documents showing aircraft eligibility for RNAV 1 and RNAV 2. AFM, AFM revision, AFM supplement, or Type certificate data sheet (TCDS) showing that the RNAV navigation system is eligible for RNAV 1 and RNAV 2 or RNP 1 or above. or Manufacturer statement.- Aircraft with a manufacturer statement documenting compliance with RNAV 1 and RNAV 2, or P-RNAV (TGL-10) or FAA AC ( ) or equivalent. Note: Approvals in accordance with P-RNAV only or FAA AC ( ) only require additional documentation to meet RNAV 1 and RNAV 2 requirements Aircraft modified to meet RNAV 1 and RNAV 2 standards. Documentation on aircraft inspection and/or modification, if applicable. Maintenance records documenting the installation or modification of aircraft systems Maintenance programme For aircraft with established maintenance procedures for RNAV 1 and RNAV 2 systems, the list of references of the document or programme. For recently installed RNAV 1 and RNAV 2 systems, the maintenance procedures for review. 4 5 Minimum equipment list (MEL) if applicable showing provisions for RNAV 1 and RNAV 2. Training Training programme for flight crews, flight dispatchers, and maintenance personnel as applicable.

29 Indication of Item Title of document inclusion by the Comments by the Inspector 6 Operating policies and procedures including relevant section of Operations Manuals and checklists attached to the application, applicable to RNAV 1 and RNAV 2 Navigation database 7 Details of the navigation data validation programme.

30 SECTION 3 - GUIDE FOR DETERMINING RNAV 1 AND RNAV 2 AIRCRAFT ELIGIBILITY Reference Location in paragraphs the ICAO Doc Item Topics Documents Comments 9613 of the Vol II Part B 3 System eligibility for RNAV 1 and RNAV 2 operations 1 Aircraft with a statement of compliance with at least one of the following: a) Aircraft approved under TGL-10 and AC A b) Aircraft approved under TGL-10 (P- RNAV) and additional requirements in Table II-B-3-1 c) Aircraft that comply with AC A and additional requirements in Table II-B-3-2 d) Aircraft with a statement by the manufacturer demonstrating compliance with RNAV 1 and RNAV 2 requirements (b) (b) (b) 2 Aircraft and system requirements (as applicable) a) FMS with TSO-C129() GNSS (a) b) FMS with TSO-C145() GNSS (b) c) Stand-alone TSO C129 ( ) Class A1 GNSS (c) d) Stand-alone TSO C146 ( ) GNSS (d) e) DME/DME RNAV equipment DME/DME/IRU RNAV equipment

31 Reference Location in paragraphs the ICAO Doc Item Topics Documents Comments 9613 of the Vol II Part B 3 3 Functional requirements

32 SECTION 4 - PROCEDURES FOR RNAV 1 AND RNAV 2 OPERATIONS Item Operating Procedures Reference paragraphs ICAO Doc 9613 Vol II Part B 3 Location in the Documents of the Comments 1 Pre-flight planning File appropriate flight plan suffix Ensure on-board navigation data current and appropriate for the region of intended operation Use all the information available, to confirm the availability of the required navigation infrastructure for the projected routes, including any non-rnav contingency, for the intended operation. Check GNSS integrity prediction (for GNSS equipped aircraft) For navigation relying on DME, check NOTAMs to verify the condition of critical DMEs. Assess capability to navigate (potentially to an alternate destination) in case of failure of critical DME while airborne General operating procedures Operator procedures to ensure flight crew do not request, or file a flight plan for RNAV 1 and RNAV 2 routes unless they meet all the criteria in the relevant State documents Operator procedures to ensure any manufacturer requirements, to meet the performance requirements of this section are met

33 Item Operating Procedures Reference paragraphs ICAO Doc 9613 Vol II Part B 3 Location in the Documents of the Comments At system initialization, pilots must: a) confirm the validity of the navigation database; b) verify the current position of the aircraft; c) verify the proper entry of the assigned ATC route once the initial clearance is received, and of any subsequent route changes; and d) Ensure that the WPT sequence displayed on the navigation system coincides with the route shown in the appropriate charts and with the assigned route. Operator procedures to ensure SID/STARs are retrieved from the on-board navigation database using the procedure name are consistent with the charted procedure and only modified as outlined in the PBN Manual RNAV 1 or RNAV 2 routes to be obtained from the database and only modified as per approved procedures Operator procedures for verifying navigation system text display Operator procedures for confirming reasonableness of navigation

34 Item Operating Procedures Reference paragraphs ICAO Doc 9613 Vol II Part B 3 Location in the Documents of the Comments For RNAV 2 Routes - recommended procedures for the use of a lateral deviation indicator, flight director or autopilot in lateral navigation mode For RNAV 1 routes - requirements for the use of a lateral deviation indicator, a FD or an AP in the lateral navigation mode. Operator procedures for setting lateral deviation scale (where applicable) Operator procedures for limiting FTE to +/- ½ navigation accuracy Operator procedures for rejoining route following ATC course assignment Operator procedures for setting bank angle limitations Specific RNAV SID requirements Operator procedures for determining system availability and pre-departure setup Operator procedures/requirements for equipment use to ensure meeting RNAV performance. For DME/DME/IRU aircraft. - Requirements for position confirmation For aircraft utilizing GNSS requirements for acquiring signal and flight plan loading to ensure the appropriate navigation system monitoring and sensitivity

35 Item Operating Procedures Reference paragraphs ICAO Doc 9613 Vol II Part B 3 Location in the Documents of the Comments 4 Specific RNAV STAR requirements Operator procedures for loading/checking route Operator procedures related to restriction on waypoint creation Operator procedures for contingency procedures to revert to a conventional arrival route Operator procedures for accepting radar headings or direct to tracking Operator procedures for verifying system operation and selection of procedures Operator procedures for observing published altitude and speed constraints 5 Contingency procedures Operators contingency procedures for loss of navigation capability

36 ANNEXURE 4 TO APPENDIX TO CAR SECTION 8 SERIES O PART VI, ISSUE I, 01ST AUG 2011 RNP 4 JOB AID APPLICATION TO CONDUCT RNP 4 1. Introduction This Job Aid was developed to provide guidance on the process to be followed in order to obtain an RNP 4 approval. It should be used as an aid for the approval process but frequent reference to the ICAO Doc 9613 PBN Manual and DGCA FOI Manual (Annexure - PBN Operational Approval) will be required. Volume II, Part C, Chapter 1 contains detailed guidance on the implementation of RNP Purpose of the Job Aid 2.1 To give s and inspectors information on the main RNP 4 reference documents. 2.2 To provide tables showing the contents of the application, the associated reference paragraphs, the place in the application of the where RNP 4 elements are mentioned and columns for inspector comments and follow-up on the status of various elements of RNP Actions Recommended for the Inspector and Operator 3.1 At the pre-application meeting with the, the inspector reviews the basic events of the RNP 4 approval process described in Section 1 of this Job Aid, in order to provide an overview of the approval process events. 3.2 The inspector reviews this Job Aid with the in order to establish the form and content of the RNP 4 approval application. 3.3 The uses this Job Aid as a guide to collect the documents of the RNP 4 application. 3.4 The inserts in the Job Aid references showing in what part of its documents are the RNP 4 elements located. 3.5 The submits the Job Aid and the application to the inspector (with the required documents). 3.6 The inspector indicates in the Job Aid whether an item is in compliance or needs corrective action. 3.7 The inspector informs the as soon as possible when a corrective action by the is required. 3.8 The provides the inspector with the revised material when so requested. 3.9 DGCA provides the with the operational specification (air s) or a letter of authorization (others) as applicable, when the tasks and documents have been completed.

37 SECTION 1 - INFORMATION ON THE IDENTIFICATION OF AIRCRAFT AND OPERATORS NAME OF THE OPERATOR: is applying for RNP 4 Operations Approval. Aircraft Aircraft Registration List relevant make and model manufacturer, (required only if of related navigation model, and series installed equipment equipment varies between model and series) DATE OF PRE-APPLICATION MEETING DATE ON WHICH THE APPLICATION WAS RECEIVED DATE ON WHICH THE OPERATOR INTENDS TO BEGIN RNP 4 OPERATIONS

38 SECTION 2 - OPERATOR APPLICATION (ITEMS AND DOCUMENTS) Indication of Item Title of document inclusion by the Comments by the Inspector Aircraft airworthiness documents showing RNP 4 compliance per ICAO PBN Manual, e.g., 1 AFM, AFM Revision, AFM Supplement or Type Certificate Data Sheet (TCDS) showing that aircraft LRNS are RNP 4 eligible. Aircraft Modified To Meet RNP 4 Standards Documentation of aircraft inspection and/or 2 modification. If applicable, maintenance records 3 4 documenting installation or modification of aircraft/lrns. Maintenance Program: For aircraft with established LRNS maintenance practices, provide list of document or program references. For newly installed LRNS, provide LRNS maintenance practices for review. Minimum Equipment List (MEL) if applicable showing provisions for LRNS Training programme for flight crews, and flight 5 dispatchers, and maintenance personnel as applicable. 6 Operating policies and procedures including relevant section of Operations Manuals and checklists attached to the application, applicable to RNP 4 Navigation database 7 Details of the navigation data validation programme.

39 SECTION 3 - GUIDE FOR DETERMINING RNP 4 AIRCRAFT ELIGIBILITY Reference Location in paragraphs the ICAO Doc Item Topics Documents Comments 9613 of the Vol II Part C 1 Eligibility Group 1 - RNP Certification 1 (RNP compliance documented in Airplane Flight Manual (AFM) (a) Eligibility Group 2 - Prior Navigation 2 System Certification (b) Aircraft fitted with GNSS only: a) Approved long-range navigation systems for oceanic and remote airspace (with FDE) b) Approved dispatch FDE availability programme (b)(i) Multi-sensor Systems Integrating GNSS with integrity provided by RAIM (b)(ii) Multi-sensor Systems Integrating GNSS with integrity provided by AAIM (b)(iii) 3 Eligibility Group 3 - New Technology (c) Requirement for at least dual Long Range 4 Navigation System equipage including GNSS 5 Functional Requirements

40 SECTION 4 - PROCEDURES FOR RNP 4 OPERATIONS Reference Location in paragraphs the ICAO Doc Item Operating Procedures Documents Comments 9613 of the Vol II Part C 1 1 Pre-flight Planning Verify aircraft long-range navigation systems (LRNS) required to meet minimum Navigation Specification (RNP) specified for the route or area is operational. Annotate ICAO Flight Plan block 10 (Equipment) with R and Z and annotate Item 18 with NAV/RNP Note: CPDLC and ADS-C will also be required when separation standard is 30 NM lateral and/or longitudinal. Review applicable contingency procedures Ensure navigation capability available including availability of FDE s applicable 2 Pre-flight Procedures (c) Review of maintenance logs and forms for LRNS status Confirm Navigation Database currency (a) (Note) 3 En route Procedures Before oceanic entry point, verify two LRNS meeting the minimum RNP specified are operating. If not, notify ATC and operate in accordance with policy applicable to the airspace. Before entering oceanic airspace, perform navigation accuracy check and