APV Operations ICAO APV workshop Meetings Seminars and Workshops... · APV Operations ICAO APV workshop ... Title presentation Applicable Regulations Applicable AMC 20 ... supplier

APV Operations

ICAO APV workshop

Bryan Jolly ATM Rulemaking Officer25 May 2011

2

Title presentation

Applicable Regulations

Applicable AMC 20 material

AMC 20-27 Baro-VNAV operations

based on FAA AC 20-129 compliance

Approval for LPV operations

Operational Approval

Regulatory material

3

Applicable Regulations

Annex III to Council Regulation (EEC) No 3922/91 (EU-OPS)

Commission Regulation (EC) No 1702/2003 (Part 21)

4

http://eur-lex.europa.eu/en/index.htm




SES Regulation

Article 2.2(c)

public or private entities providing, for the purposes of this Regulation: (i) services for the origination and provision of survey data; (ii) procedure design services; (iii) electronic terrain data; (iv) electronic obstacle data.

Regulation 73/2010

COMMISSION REGULATION (EU) No 73/2010

of 26 January 2010

laying down requirements on the quality of aeronautical data and

aeronautical information for the single European sky

5





EASA AMCs for APV Operations

AMC Subject EASA ED Decision

AMC 20-26

Airworthiness Approval and Operational Criteria for RNP Authorisation Required (RNP AR) Operations

DECISION 2009/019/R

Effective23 December

2009AMC 20-27

Airworthiness Approval and Operational Criteria for RNPAPPROACH (RNP APCH) Operations including APV BAROVNAVOperations

6

EASA AMCs for APV Operations

AMC Subject NPA CRD EASA ED Decision

20-28

(GNSS

LPV)

Airworthiness Approval and Operational Criteria for RNAV GNSS approach operation to LPV minima using

SBAS)

NPA 2009-04

Planned by mid 2011

Planned by end 2011

7

8

http://easa.europa.eu/regulations/regulations-structure.php

C:/Documents and Settings/jollybr/My Documents/RULEMAKING/ICAO/PBN-TF/TF5/regulations-structure.php

C:/Documents and Settings/jollybr/My Documents/RULEMAKING/ICAO/PBN-TF/agency-measures/acceptable-means-of-compliance-and-guidance-material.php

C:/Documents and Settings/jollybr/My Documents/RULEMAKING/ICAO/PBN-TF/agency-measures/certification-specifications.php

C:/Documents and Settings/jollybr/My Documents/RULEMAKING/ICAO/PBN-TF/agency-measures/acceptable-means-of-compliance-and-guidance-material.php

C:/Documents and Settings/jollybr/My Documents/RULEMAKING/ICAO/PBN-TF/TF5/regulation-EC-2042-2003.php

C:/Documents and Settings/jollybr/My Documents/RULEMAKING/ICAO/PBN-TF/TF5/regulation-EC-1702-2003.php




EASA requirements

OPINION OF THE EUROPEAN AVIATION SAFETY AGENCY

Nr. 01/2005

On the acceptance of Navigation Database Suppliers

EUROPEAN AVIATION SAFETY AGENGY

CONDITIONS FOR THE ISSUANCE OF LETTERS OF ACCEPTANCE FOR

NAVIGATION DATABASE SUPPLIERS BY THE AGENCY

DISCLAIMER: The letter of acceptance does not constitute a mandatory requirement

since it is not a mandatory certification attesting compliance with a binding act. The

conditions and associated guidance are applied on a purely voluntary basis at the

request of the applicant.

A.131 Scope

These Conditions establish:

(a) The procedure for the issuance of a letter of acceptance (LOA) for

organisations that translate, format and/or integrate information that originates from

State aeronautical information services (e.g. AIP) into electronic databases for

airborne navigation systems.

(b) The rights and obligations of the applicant for, and holders of, such letters of

acceptance.

A.132. Definitions

(a) Navigation Database - Data (such as navigation information, flight planning

waypoints, airways, navigation facilities, SID, STAR) that is stored electronically in a

•system that supports an airborne navigation application.

(b) Data Service Provider – An organisation (not including the State AIP

provider), which collects, originates or processes aeronautical data and provides a

navigation database in a generic format (such as ARINC 424). Such organisations are

eligible for a Type 1 LOA under these Conditions (see Guidance Para 5.7) showing

•hat the generic database has been formatted under controlled conditions.

(c) Data Application Integrator - An organisation that incorporates either State

AIP data or a generic database into a format compatible with specific target airborne

navigation equipment with a defined intended function. Such organisations require an

interface with the equipment design organisation, and are eligible for a Type 2 LOA

under these Conditions (see Guidance Para 5.7). This provides a list of equipment

models and part numbers where compatibility has been demonstrated to the Agency,

permitting the supply of navigation databases directly to end users/operators.

(d) Data Quality Requirements - A specification of the characteristics of data to

ensure that data is compatible with its intended use.

(e) Type 1 LOA – Letter of acceptance granted where a Navigation Database

•supplier complies with ED-76/DO-200A with no identified compatibility with an

•aircraft system. A Type 1 LOA confirms that the processes for producing navigation

9

http://easa.europa.eu/agency-measures/opinions.php




AMC 20-27- EASA

10

Interpreting AMC 20-27

Some confusion on the intended use …

…additional guidance on interpretation may be helpful…

11

Remember: AMC 20-27 is ONE acceptable means of compliance, not THE ONLY acceptable MoC


12

1. Purpose

2. Background

3. Scope

4. Reference Documents

5. Assumptions

6. RNP-APCH Airworthiness Criteria

7. Functional Criteria

8. Airworthiness Compliance

9. AFM/POH

10. RNP-APCH Operational Criteria incl. appendices 2, 3, 4 and 5

11. Availability of Documents

Contents of AMC 20-27:

General information.


Airworthiness Criteria.

Operational Criteria.


Airworthiness Criteria (Chapters 6-9)

These criteria are typically being assessed as part of the application for TC/STC approval.

It is not expected that the operator demonstrates compliance with the requirements of these chapters.

13


Airworthiness Criteria:

Chapter 6:

Equipment Qualification (ETSO/TSO)

Accuracy (Horizontal/Vertical FTE, TSE etc.)*

Integrity

Continuity

14

These criteria are very difficult to prove for an operator. In depth knowledge of system design is required.

* There are differences with FAA AC 20-129. See separate slide(s)



Chapter 7:

Functional Criteria for RNP-APCH

Required Functions for BARO VNAV

Recommended Functions for RNP-APCH

Recommended Functions for BARO VNAV

15

Information may be available to operators, but may not have been certified (options).



Chapter 8:

Compliance Statement, Means of Compliance

Specific Installation Criteria & Assessments

Existing Installations

Chapter 9:

Aircraft Flight Manual/Pilot Operational Handbook

Procedures (Normal/Abnormal), Limitations

16

A DOA or similar organisation will have to demonstrate compliance with chapters 8 and 9.


Operational Criteria:

Chapter 10:

Flight OPS Documentation (SOP) – Reference to Appendix 4

Flight Crew Training – Ref. to Appendix 5.

Aerodrome Competence/Operator Verification – Ref. to Appendix 2

Database management.

Reportable Events

17

These aspects are typically expected to be arranged by the operator.


How about FAA AC 20-129?

AMC 20-27 has more stringent requirements for demonstration of vertical FTE (FTEz) and TSE (TSEz) than FAA AC 20-129 .

The reason is an inconsistency between AC 20-129 values and PANS OPS design criteria:

AC 20-129 allowable TSEz values exceed MOC buffer of 246 ft. at altitudes above 5000 ft.

18


19

MOC of 246 Ft.

AMC 20-27 TSEz : 238 ft.

AC 20-129 TSEz: 335 ft.


EASA recognises the additional burden to recertify their aircraft to the new requirements of AMC 20-27.

The potential safety issues resulting from the inconsistence between FAA AC 20-129, Attachment II of the ICAO PBN and the ICAO PANS-OPS manual is recognised .

Aircraft which have previously been demonstrated to comply with the requirements of FAA AC 20-129 may, under certain conditions, be eligible for acceptance without further demonstration of FTE values, albeit with limitations

20


Applicable conditions

The applicant shall provide to the Agency proof that the aircraft has previously been approved to the requirements of AC 20-129.

The applicant shall provide to the Agency a document stating how the requirements of AMC 20-27 have been complied with, with the exception of FTE requirements.

The aircraft shall be equipped with a suitably scaled indicator to enable the flight crews to readily distinguish the +75ft and -75 ftboundaries. Note: +100/-50ft scale markings, alerts or attention getters may not be accepted.

The AFM shall include a limitation that RNP BARO VNAV approaches to airfields at elevations of 5000 ft. or higher are not permitted.

21

Approach Operation to LPV Minima

22

LPV

23

1. Purpose

2. Background

3. Scope

4. Reference Documents

5. Assumptions

6. Airworthiness Criteria

7. Functional Criteria

8. Airworthiness Compliance

9. AFM/POH

10. Operational Criteria incl. appendices 2, 3 and 4

11. Availability of Documents

Contents of AMC 20-28:



Airworthiness Criteria.

Operational Criteria.

LPV

European Aviation

Safety Agency

< Applicant, application>

CRI F- 02-LPV

Airworthiness Approval and Operational

Criteria for RNAV GNSS approach operation

to LPV minima using SBAS

Issue: 1

Certification Review Item Date: 15 May 2009

Page 1 of 2

REQUIREMENT(S): CS/FAR 25.1301, 1302, 1307, 1309, 1316, 1321, 1322, 1329, 1431,

1581

ADVISORY MATERIAL: - PRIMARY GROUP: 06 SECONDARY GROUP(S): 01

CATEGORY: Means of Compliance

APPLICABILITY: - ________________________________________________________________________

Statement of Issue:

<Applicant> has applied for EASA airworthiness approval of RNAV-RNAV systems in

order to enable the <….> aircraft to perform RNAV-GNSS approach operations to

LPV minima procedures (or LPV approaches) within European airspace. Given the

lack of guidance and regulatory material in this area the objective of this CRI is to

establish EASA Acceptable Means of Compliance for the approval of such RNAV-

GNSS system installations, where RNAV-GNSS approach operations to LPV minima

procedures are established.

The navigational solution for an aircraft assisted by GNSS sensors is considered to

be heavily-based on a differential-based determination of the aircraft position in the

3-dimensional airspace. Therefore, the applicability of this CRI assumes that the

Satellite Based Augmentation System (SBAS) in the intended region of aircraft

operation with adequate position determination capability is operationally available1.

This EASA CRI proposes the draft AMC 20-28 attached in the appendix A as means

of compliance for airworthiness approval for RNAV GNSS approach operation to LPV

minima using SBAS.

EASA Position:

Airworthiness approval for the approval of LPV approaches

1 At the time of issuing this CRI (May 2009) the certification process of the European SBAS

(EGNOS) for Civil Aviation use is still under development. Civil Aviation Users should therefore not use the EGNOS or similar systems which are still under development, for safety critical purposes.

EASA has drafted a generic Certification Review Item (CRI):

Based on NPA 2009-04 (AMC 20-28) criteria

Applications for Airworthiness approval can be accepted by the Agency

24

RNP-APCH with SBAS derived Guidance - EASA

25

RNP-APCH with SBAS Guidance

AMC 20-27 assumes that:

Guidance is linear, and;

VNAV is based on BARO

Industry (RTCA DO-229D) assumes that:

Guidance may be angular

VNAV may be based on SBAS (EGNOS).

ICAO PANS OPS accounts for both.

26


EASA has drafted a generic Certification Review Item (CRI):

Based on AMC 20-27 and NPA 2009-04 (AMC 20-28) criteria

Taking into account RTCA DO-229D and PANS OPS provisions

To be applied with specific applications

EASA is considering publication of a Certification Memo

27


Operational Aspects:

Since some of the assumptions made at the time of drafting of AMC 20-27 are invalidated, operational procedures, training, may need adaptation:

Certain procedures cannot be flown, but this is not obvious from the chart:

Angular guidance not accounted for, coded ‘B’ in ARINC 424 data

+/- 75 ft. monitoring requirement invalidated

Temperature compensation not applicable

Etc.

28


29


30

COMMISSION REGULATION (EC) No 859/2008

of 20 August 2008

amending Council Regulation (EEC) No 3922/91 as regards common technical requirements and

administrative procedures applicable to commercial transportation by aeroplane

Commercial Operations


An operator shall ensure that an aeroplane operated in areas, or through portions of airspace, or on routes where navigation performance requirements have been specified, is certified according to these requirements, and, if required, that the Authority has granted the relevant operational approval.

31

EU-OPS 1.243(a)

Operational Approval Required from NAA


Submission to include:

Reference documents used in compiling submission

Airworthiness: navigation system capability compliance statement.

Details of quality control measures for navigation data base

Standard operating procedures

Operations Manual including MEL handling, crew authorisation/validation, training programme

32


Non Commercial Operation

Currently No Common EU requirement

National requirements are applicable

33