Summary of Discussions Meetings Seminars and Workshops... · SUMMARY OF DISCUSSIONS ... Doc 9997 PBN Operational Approval Manual 2.3 The PBN TF was informed that the following training

PBN TF/8 - SoD

25/01/2013

SoD PBN TF8 final.docx January 2013

SUMMARY OF DISCUSSIONS

ICAO EUR PERFORMANCE BASED NAVIGATION TASK FORCE

(EUR PBN TF)

EIGHTH MEETING

(Paris, 23 –24 January 2013)

1. Introduction

1.1 The Eighth Meeting of the ICAO EUR PBN TF was convened on 23-24 January 2013 in the

EUR/NAT Office of ICAO in Paris, France.

1.2 The Meeting was chaired by Mr Thomas Buchanan (Switzerland) and Mr Elkhan Nahmadov

from the European and North Atlantic (EUR/NAT) Office of ICAO was the Secretary, assisted by Ms

Catherine Daly from the same Office. Lists of participants and contacts are provided at Appendix A and

Appendix B. A list of documentation submitted to and discussed at the Meeting is provided at Appendix C.

2. Review of the latest developments

ICAO update

2.1 The PBN TF was provided with an update on the latest developments in ICAO, namely the

outcomes of the PBN Symposium and the 12th Air Navigation Conference. It was noted that PBN, CDO and

CCO were the ICAO and Global Air Navigation Plan’s immediate priorities and the significance that the

Conference and Symposium seen in the activities of the regional PBN implementation groups; one among

them being the EUR PBN task force.

2.2 The PBN TF noted that the following guidance material was published by ICAO:

a) Doc 9613 PBN Manual Edition 4.0;

b) Doc 9992 Manual on the Use of PBN in Airspace Design;

c) Doc 9993 Continuous Climb Operations (CCO) Manual;

d) Doc 9997 PBN Operational Approval Manual

2.3 The PBN TF was informed that the following training courses were made available on the

http://www.icao.int/safety/pbn/SitePages/PBN%20ikit.aspx:

a) CBT courses on PBN overview, Airspace design and operational approvals; and

b) PBN iLearn and ASBU iLearn Kits.

2.4 Information on the outcomes of the 54th Meeting of the ICAO European Air Navigation

Planning and Implementation Group was provided. The task force noted that the RNP APCH

implementation guidance material was now endorsed as a EUR Document (EUR Doc 025) and was made

available on the ICAO EUR/NAT website.

http://www.icao.int/safety/pbn/SitePages/PBN%20ikit.aspx

-2- PBN TF/8 - SoD


2.5 The task force was informed that in line with another EANPG conclusion a PBN, CDO and

CCO implementation workshop was planned to be organized in April-May 2013 time period in Almaty,

Kazakhstan. The workshop will be run in parallel with a regional Go Team PBN implementation assistance

project for the States in the Central Asia area of the EUR.

2.6 The task force was informed about the outcomes of the EANPG/54 discussion on potential

merging of the EUR PBN task force and Eurocontrol RAISG. The task force agreed that such merge would

be beneficial in terms of reducing travel costs for those participants that attend both meetings. This would

also allow better sharing of information between both groups and consolidate regional efforts on

implementation of PBN in approach area in particular. Having noted that the EUR PBN task force scope was

significantly larger than just approach and was covering all aspects of PBN, the task force felt that further

consolidation of the activities would be even more beneficial.

2.7 In this regard, the task force was presented with a draft Terms of Reference as drafted by the

ICAO Secretariat in follow up to the EANPG conclusion. The task force has agreed in principle to the

presented ToR (Appendix D refers), noting that further coordination will take place between the ICAO

EUR/NAT Secretariat and Eurocontrol. It was agreed that further to the COG and Eurocontrol AAB

discussions and agreement, the next meeting of the EUR PBN TF combined with the RAISG could be held

in the fall 2013 in Paris.

2.8 The PBN TF noted that a proposal for amendment of PANS-OPS provisions was expected

soon addressing:

a) Criteria to support new edition of PBN Manual;

b) Improved Baro-VNAV criteria;

c) Helicopter criteria;

d) Sample charts.

2.9 The task force emphasized that this proposal was to improve the PANS-OPS material and

should not be interpreted as a reason for delaying any ongoing or planned APV implementations.

2.10 The task force noted that based on the ANConf-12 recommendations, the ICAO work

programme includes the development of a Collision Risk Model for PBN obstacle clearance and air-to-air

separation, PBN Procedure Design Safety Assessment Manual, RNP AR for departures and Advanced RNP

support document.

Regional workshops and Go Teams

2.11 The PBN TF noted that a PBN Airspace concept implementation workshop was held on 9-12

July in Georgia. In parallel, a regional Go- Team project was conducted for States in the Southern Caucasus

area. A global Go-Team project was carried out on 4-7 September 2012 in the Russian Federation. The PBN

TF was presented with the outcomes and recommendations of both projects and also feedback from the

beneficiary States, namely Azerbaijan, Armenia, Georgia and the Russian Federation. The task force noted

that the Go Team projects proved to be very effective in promoting PBN and assisting national authorities to

speed up the progress of PBN implementation. It was also helpful in identifying gaps and recommending

solution for implementation by States and industry. Further updates will be provided to the next meeting by

ICAO and States. The task force discussed a proposal made by the Russian Federation seeking a support to

the need for ICAO to consider a number of issues related to expansion of GBAS capabilities for transferring

TAP data blocks, for further inclusion into SARPs. There were conflicting views on this proposal. The

Secretary agreed to clarify this issue with the NSP Secretary noting that this issue would be probably better

fitted for a discussion in the NSP.

-3- PBN TF/8- SoD


EASA update

2.12 The PBN TF was provided with the status and foreseen evolution of the EASA regulatory

and support material for PBN. Regarding the forthcoming Rule making tasks 445/446 and 447/448 related to

“Technical requirements and operational procedures for airspace design including instrument procedure

design” (RMT 445/446) and “technical requirements and operational procedures for AIS/AIM” (447/448, it

was noted that the ToRs for these two RMT are to be issued in March/April 2013.

2.13 A discussion took place on whether it was necessary to certify the use of GNSS by national

authorities. It was noted that by ICAO Annex 10 GNSS was a standard navigation systems and any

prohibition in using of GNSS would be a subject to notifying a difference versus Annex 10. It was also

recalled that EASA in certifying EGNOS left certification of GNSS to the providing authority and didn’t

undertake any additional actions on certification. The task force also note the AN.Conf-12 recommendation

urging States to refrain from prohibiting the GNSS components.

EC PBN IR

2.14 The PBN TF was presented with an update on the development of the PBN Implementing

Rule by Eurocontrol as mandated by the EC. It was noted that a consultation workshop will take place on 5

February 2013 in Brussels and the task force members were invited to register for participation.

EGNOS status update

2.15 An update was provided by the EGNOS service provider on the EGNOS system and services

status, EGNOS SoL Service issues, EGNOS Services Roadmap and EGNOS SoL Service introduction

Status. The current status of LPV implementation in Europe was also provided. Further information could be

found http://egnos-user-support.essp-sas.eu and www.essp-sas.eu. The task force noted a comment by

Portugal that a clarification on mitigation measures needs to be provided in Annex 10 with regards to the

cases where continuity requirements of SBAS are not met. The Secretary agreed to coordinate this issue with

the NSP Secretariat and report to the next meeting.

3. Status of PBN implementation in the EUR region

Status of PBN in the EUR Region

3.1 The PBN TF was presented with statistics on the progress of PBN implementation in the EUR

based on the data available to ICAO through updates of the CNS4b Table of the EUR Air Navigation Plan and

the PBN implementation status reports. Update was also provided using data available through the

Eurocontrol implementation status map tool and LSSIP mechanism. It was noted that 17 out of 56

EUR States have developed their national plans and another 10 informed they are advancing in this

work. There was information available from 5 States. These 5 States will be addressed as part of the

regional Go Team project for the States in the Central Asia area in 2013.

3.2 The task force noted that currently about 30% of runway ends in the EUR were

provided with RNP type of approaches. Based on the current planning information in CNS4b Table

the 50 % value would be achieved by 2016. Although there was a good progress (almost 50%)

compare to the data provided in June 2012, these numbers are still not meeting the ICAO Assembly

Resolution targets. In this regard, the task force discussed the need for additional clarification on the

scope concerned by Assembly Resolution 37-11. It was felt that text of the Resolution could be

further clarified to be aligned with performance oriented approach and with the latest work on

approach classification. In this vein, it should be highlighted that the first priority for RNP APCH

implementation should be runway ends without precision approach, then as a backup to precision

approaches. The scope of the Resolution should also allow for consideration of ILS/MLS/GLS

solutions and aiming at improving safety, accessibility and resilience. In view of the above and

http://egnos-user-support.essp-sas.eu/

http://www.essp-sas.eu/

-4- PBN TF/8 - SoD


taking into account that the next Assembly will be in September 2013, the task force agreed that a

working paper reinforcing Resolution 37-11 and providing additional clarifications in line with the

discussion above should be drafted and presented by the Chairman on behalf of the task force.

3.3 The task force also discussed potential improvements to Table CNS4b to allow

more clarity and less ambiguity. The revised version of the Table as discussed at the meeting is

provided at Appendix E. It was agreed that ICAO and Eurocontrol would complete the refinement

of the Table and circulate the final version by e-mail for the approval of the task force. The final

version would be used to merge data from the current table and map-tool in order to present to the

EANPG for approval. The new format could be then used for collecting data using the Eurocontrol

map-tool and for circulation by ICAO to States for validation.

Presentations by States

3.4 The PBN TF was presented with the status of the national PBN planning and implementation

in Azerbaijan, Italy, Latvia, Romania, the Russian Federation, Switzerland and the United Kingdom.

3.5 In particular a statement by Romania was noted that within the context of SES regulatory

framework (as defined by regulation 549/2004), the appropriate bodies should establish an approach for the

authorization of use for GNSS systems at European level. Romania is currently not able to establish an

implementation calendar for the implementation of APV procedures as per Assembly Resolution 37/11 due

to the lack of coverage of EGNOS system over Eastern Europe. Clarifications are needed with regard to the

maintenance of competence of staff conducting oversight activities, especially those related to procedure

design. There is a need to improve/facilitate access to pan-European programmes in support of PBN

implementation.”

3.6 The task force noted that the lack of procedure designers and in general deficiencies in the

States oversight capabilities with regards to the provision of PANS-OPS related services was one of the

challenges to PBN. It was noted that cooperative efforts could be a way forward to overcome this challenge.

The task force noted positive experience of the ICAO APAC Region where a regional procedure design

office was established. The task felt that something similar could be undertaken in the EUR whereby some

States could agree on providing independent procedures reviews for each other. This could be a solution with

no expense for everyone, could allow address on of the PANS –OPS requirements for independent reviews

of the procedures and contribute to the improvements in safety and progress implementation of PBN. It was

agreed that the Secretary would bring this proposal to the attention of the EANPG and solicit proposal from

States willing to join the proposed schema.

3.7 The Russian Federation presented their PBN position paper that was originally submitted for

the 12th AN-Conf discussions and the status of GLONASS implementation. In response to the questions from

the audience, the Russian Federation explained that the recently adopted GLONASS equipment carriage

requirements were applicable only to the aircraft operators registered in the Russian Federation.

3.8 The PBN TF encouraged States to continue providing reports on the PBN status and plans at

future meetings.

Frequently Asked Questions leaflet

3.9 The task force agreed to develop a Frequently Asked Question leaflet based on information

provided during the PBN TF meetings that could be useful for the participants and PBN implementers. The

first material for insertion in the leaflet is provided at Appendix F.

-5- PBN TF/8- SoD


4. EUR PBN advisory circulars

4.1 The PBN TF was provided with draft Advisory Circulars to facilitate PBN operational

approvals for RNAV5, RNAV 1, RNAV 2 and APV Baro-VNAV operations. The advisory circulars were

drafted on the basis of the ICAO circulars approved for use by the SAM Region and in compliance with the

appropriate FAA and EASA material. These Advisory Circulars are proposed for use as guidance material,

specifically for States outside the EASA area. Such Advisory Circulars would provide assistance to the

aforementioned States in facilitating the process of PBN approval and contribute to the progress of PBN

implementation.

4.2 The task force noted that Para 2.5.1 od Doc 9997 stated the following:

“Individual States must publish national regulatory material which addresses the PBN applications relevant

to their airspace or relevant to operations conducted in another State by the State’s operators or by aircraft on

their Registry. The regulations may be categorized by operation, flight phase, area of operation and/or

navigation specification. Approvals for commercial operations should require specific authorization.

Example regulatory text is provided at Annex C.

Note. — The EASA AMCs and the FAA ACs mentioned above also address operational approval. The

ICAO South American Office (SAM) has published a set of PBN Advisory Circulars covering operational

approval for PBN applications for use within the region. Many other States publish similar ACs or refer to

existing ACs or AMCs in their national regulations. Table 3 lists the operational approval material published

by ICAO (SAM) and Australia for PBN applications (each document may reference additional standards

including ACs, TSOs and RTCA/EUROCAE documents):”

4.3 It was recalled that this material was presented to the 6th Meeting of the PBN TF (24-25

January 2012) where it was agreed that the material presented would be cleaned up to remove the SAM

specific references and submitted to the EANPG for approval. In line with this agreement, the ICAO

Secretariat prepared the advisory circulars for the currently most demanded PBN operations for the review

and approval by the task force.

4.4 The task force noted the agreement of the Russian Federation to translate the currently

prepared circulars and future to be completed to Russian and agreed that the advisory circulars would be

presented to the EANPG for endorsement in English and Russian. The task force provided comments on para

6.1 l) of the AC on RNAV1 and also agreed to include a note in the APV AC clarifying that the criteria used

in this circular are based on the FAA document. The revised circulars are provided at Appendix G, H and I.

5. AOB

Next meeting

5.1 The next meeting of the PBN TF will take place on 11-13 September 2013 in Paris.

A-1 Appendix A to

PBN TF/8 SoD

APPENDIX A

List of Participants


ARMENIA

Gurgen HAKOBYAN

Artur GASPARYAN

AUSTRIA

Florian BUCHMANN

AZERBAIJAN

Aleksandr ESTROV

Bala MIRZAYEV

Rovshan SULTANOV

ESTONIA

Aleksei SHISHOV

FINLAND

Mika SAALASTI

FRANCE

Sophie BARANES

Richard AMY

Philppe BIZET

Bertrand FOUCHER

Philippe NOTRY

GEORGIA

Zviad KHITARISHVILI

David CHKHIKVISHVILI

IRELAND

James GAVIN

Donal LAMONT

ITALY

Stefano FELICI

Vasco LOCCI

Carmelo LOPIS

LATVIA

Inese LIEGE

Érika NEIMANE

Vadim TUMARKIN

NORWAY

Arne HEGGE

Arne LINDBERG

PORTUGAL

Victor ESTRELA

ROMANIA

Valentin STOIAN

RUSSIAN FEDERATION

Elmar ALEKSANDROV

Mikhail DANILIN

Vladimir KORCHAGIN

Vladlen KOROVKIN

Sergey LEGCHENKOV

Alexander LOSEV

Dmitry STEPANKO

SPAIN

Francisco-Javier DE BLAS

SWITZERLAND

Marc TROLLER Dr

Thomas BUCHANAN

Laurent DELETRAZ

Peter IMHOF

UKRAINE

Bogdan SUVEIKA

Pavlo KUD

UNITED KINGDOM

Geoffrey BURTENSHAW

AVIACONSULT

Frank LUMNITZER

EASA

Bryan JOLLY

EUROCONTROL

Richard FARNWORTH

Sasho NESHEVSKI

Aline TROADEC

LUFTHANSA

Josef ANSCHAU

LUFTHANSA SYSTEMS FLIGHTNAV INC

Jordan MEEK

A-2 Appendix A to

PBN TF/8-SoD


TRANSAERO AIRLINES

Viacheslav CHISTOV

ICAO

Elkhan NAHMADOV

Sven HALLE

C-1 Appendix C to

PBN TF/8-SoD

APPENDIX C

STATUS OF DOCUMENTATION


ICAO EUR PBN TF/8 (Paris, 23 to 24 January 2013)

STATUS OF DOCUMENTATION

List of working papers

WP Agenda

item Title

Presented by

1 1 Provisional Agenda Secretariat

2 4 ICAO EUR PBN Advisory Circulars Secretariat

2 Att A 4 Advisory Circular (AC 91-002) EUR RNAV 5 Secretariat

2 Att B 4 Advisory Circular AC EUR RNAV1/2 Secretariat

2 Att C 4 Advisory Circular AC EUR APV/BARO-VNAV Secretariat

3 8 EUR PBN Work Programme Secretariat

4 2 The Russian Federation’s position on PBN implementation presented at 12th AN-conf

Russian Federation

4 Att A 2 AN-Conf/12 – WP/80 – PBN Implementation in Russian Federation

Russian Federation

5 3 Status report on the Eurocontrol PBN Approach Map tool & other related aspects

Eurocontrol

6 3 Accelerating EGNOS adoption for General Aviation Eurocontrol

7 8 EUR PBN TF ToR Secretariat

List of information papers

IP Agenda

item Title

Presented by

1 1 PBN TF/8 Timetable Secretariat

2 1 Summary of Discussions of the EANPG/54 meeting (Paris, France, 3-6 December 2012)

Secretariat

3 - SL AN 7/1.3.101-12/68 Proposals for amendment of Annex 10, Volume I concerning the global navigation satellite system (GNSS)

Secretariat

4 3 Azerbaijan PBN Implementation Plan Secretariat

5 1 Summary of Discussions of the PBN TF/7 meeting (Paris, France, 2-3 July 2012)

Secretariat

6 2 Report of the Committee to the conference on Agenda Item 2 Secretariat

7 2 Report of the Committee to the conference on Agenda Item 5 Secretariat

8 3 RNAV Approaches Eurocontrol

9 3 PBN – Factsheet Eurocontrol

10 3 Introducing Performance Based Navigation (PBN) and Advanced RNP (A-RNP)

Eurocontrol

11 2 PIRGs Annual Report for 2012 to the Council Secretariat

C-2 Appendix C to

PBN TF/8-SoD


List of PowerPoint presentations

PPT Agenda

item Title

Presented by

1 5 EUR PBN TF/8 – PBN Go Teams Secretariat

2 3 EUR PBN TF/8 – Status of PBN planning and implementation Secretariat

3 2 EUR PBN TF/8 – Outcomes of the 12th Air Navigation Conference

Secretariat

4 Rev 3 PBN Implementation status in Romania Romania

5 2 PBN Symposium and Workshops – (What was said) Secretariat

6 2 PBN Implementation (Where we are today) Secretariat

7 3 PBN Implementation Status in Spain Spain

8 3 PBN Rulemaking EASA

9 3 RF Leg test flights Super King Air (Skyguide) Switzerland

10 3 PBN Implementation Plan for the Russian Airspace and its first results

Russian Federation

11 7 PBN IR: Progress Update Eurocontrol

12 3 EGNOS Service Provision Status ESSP

13 3 Questions to ICAO Montreal Switzerland

14 3 UK Performance-based Navigation (PBN) Implementation Status

United Kingdom

15 3 LF IFP Regulation Draft Latvia

FLIMSY Agenda item

Title Presented

by

1 3 Structure of the European PBN working arrangements within ICAO and Eurocontrol overlap of functions

Secretariat

_______________

D-1 Appendix D to

PBN TF/8-SoD


APPENDIX D

ICAO EUR/Eurocontrol joint PBN implementation Project team

TERMS OF REFERENCE

Composition

The PBN IPT is composed of experts nominated by the ICAO contracting/member States and recognized

international organizations and industry. The members of the ICAO EUR PBN TF and Eurocontrol RAISG

will automatically continue their membership with the PBN IPT.

Chairmanship

A Chairman is proposed through nomination by one ICAO Member State and approved by the ICAO EUR

EANPG and Eurocontrol AAB upon the PBN IPT recommendation.

Reporting and Secretariat

The PBN IPT reports in parallel to the ICAO EUR EANPG and Eurocontrol AAB. The ICAO EUR/NAT

and Eurocontrol provide the necessary secretariat support in the conduct of the PBN IPT meetings, as well

preparatory and follow-up activities

Meeting arrangements

The PBN IPT meets twice a year, once in the ICAO EUR/Nat premises and once in Eurocontrol.

Deliverables

Maintain the EUR regional PBN implementation plan and other regional documentation, including

the EUR SUPPS (Doc 7030), EUR Doc 025 RNP APCH implementation guidance material.

Develop necessary guidance material to assist implementation of PBN

Provide a forum to share knowledge, lessons learnt and best practices in the EUR

Monitor the progress of PBN implementation in the EUR and report to the ICAO EANPG and Eurocontrol

AAB

Identify and report to ICAO EANPG and Eurocontrol AAB potential challenges and impediments to the

successful implementation of PBN and develop and implement regional mitigation plans

Assist States in developing and implementation of the national PBN plans

Organize and conduct PBN workshops and seminar to increase awareness

Provide direct assistance to States (preferably groups of States) on the development and implementation of

the national PBN plans

Facilitate implementation of the new PBN specifications and develop necessary guidance material in support

of this work.

Ensure regional harmonization and for possible inclusion in ICAO-developed model

documentation;

D-2 Appendix D to

PBN TF/8-SoD


Address other regional PBN implementation issues as needed.

Working methods

The PBN IPT coordinates its work with other ICAO and Eurocontrol groups as required through mediation

of the Secretariat. The PBN IPT conducts its work as much as practicable through electronic means of

communication.

_______________

E-1 Appendix E to

PBN TF/8-SoD


APPENDIX E

REVISED VERSION OF CNS4b Table

Format for the CNS/4b table proposal SWITZERLAND

BERNE (LSZB) 14 CAT I ILS in service

APV SBAS 2013

LES EPLATURES 24 CAT I ILS in service

(LSGC) APV SBAS in service

GENEVE (LSGG) O5 CAT I ILS in service

APV Baro VNAV 2015/2016

23 CAT III ILS in service

APV Baro VNAV 2015/2016

GRENCHEN 25 APV SBAS 2013

(LSZG)

RWY Type LNAV LNAV/VNAV LP LPV RNP AR

xLS CAT

SWITZERLAND

LSZB BERNE 14 Non Instrument ILS I - - - 2013 -

32 Non Instrument - 2014 - 2014 - -

LSGC LES EPLATURES 6 Non Instrument - 2015 - 2015 - -

24 Non Instrument ILS I - - - In service -

LSGG GENEVE 5 Instrument ILS I - 2015/2016 - - -

23 Instrument ILS III - 2015/2016 - - -

LSGS SION 7 Non Instrument - - - - - -

25 Non Instrument ILS I - - 2018 - -

Precision

F-1 Appendix F to

PBN TF/8-SoD


APPENDIX F

FREQUENTLY ASKED QUESTIONS

1. In your assessment, is there a possibility to exclude RWYs, where no possible design features would allow operations due to topographical constraints? If technically not possible, indeed we can’t implement and hence should be exempted. 2. Possibility to exclude a RWY, such as the 4th Runway in Frankfurt, where it is legally unacceptable to have any other type of approach operation than ILS - hence on failure, the RWY would close? Why would it be legally unacceptable? In any case, the reason for requiring an APV procedure, on ILS RWYS is for back-up purposes. If they are closing the RWY if the ILS is down, i.e. even not allowing LOC only, then basically there is no RWY, and consequently no need for back-up. Although I don’t know the ins and outs of this legal decision, I find it strange because you would always like to have something for contingency. 3. In the situation of Circling, on an approach on RWY14 (example) and circle to land operation to RWY32, does RWY32 become a candidate RWY? Even if one of the two mentioned conditions above applies? In principle we want APV procedures for circling RWYS as they are the least safe. If we have obstacle issue, see answers above. 4. With the consultation of the ACTF outcome, it becomes acceptable to have operations to non-Instrument RWYs, as long as the type is a type A... will this be a candidate for the evaluation? What do you mean a candidate for evaluation? Mind that the resolution also urges States to implement on non-instrument RWY’s where ops occur with A/C>=5700kg: 1. Urges that States include in their PBN implementation plan provisions for implementation of approach

procedures with vertical guidance (APV) to all runway ends serving aircraft with a maximum

certificated take-off mass of 5700kg or more, according to established timelines and intermediate

milestones;

In our opinion, we would recommend that we allow the exclusion of points 1 and 2, that option 3 should also allow exclusion. For the point under 4., I would recommend that we refer to Approaches rather than to the landing surfaces and the related equipage. In summary yes exclusion of 1, on 2 I tend to disagree with the legal issue (you should always have a rwy available for contingency and able to offer an APV). Answer to 3 is consequential to 1 and 2. See answer on 4 although I am not 100% sure what you meant.

_______________

G-1 Appendix G to

PBN TF/8-SoD


APPENDIX G

ADVISORY CIRCULAR AC EUR APV/BARO-VNAV

(Due to its size this Appendix G is provided in a separate document)

AC EUR APV Baro-V

_______________

H-1 Appendix H to

PBN TF/8-SoD


APPENDIX H

ADVISORY CIRCULAR (AC EUR RNAV 5)

(Due to its size this Appendix H is provided in a separate document)

AC EUR RNAV5

I-1 Appendix I to

PBN TF/8-SoD


APPENDIX I

ADVISORY CIRCULAR (AC EUR RNAV 1/2)

(Due to its size Appendix I is provided in a separate document)

AC EUR RNAV 1-2

_______________

J-1 Appendix J to

PBN TF/8 - SoD


APPENDIX J – FOLLOW UP ACTION LIST

ID # TASK ID WHO WHEN

7-1 Submit the EUR PBN ACs on RNAV5, RNAV1/2 and APV for the EANPG endorsement Secretary TF/9

7-2 The Russian Federation provide translation to Russian of the material May2013

7-3 Coordinate the new format of CNS4b and merge information from the Eurocontrol map

tool

ICAO/Eurocontrol TF/9

7-4 Coordinate the draft ToR for approval by COG and AAB ICAO/Eurocontrol TF/9

7-5 Submit a proposal for a regional mechanism for independent IFP reviews Secretary TF/9

7-6 Provide update on equipage statistics IATA TF/9

7-7 Provide update on EGNOS ESSP Tf/9

7-8 Provide updates on planning and implementation States TF/9

7-9 Provide updates on the outcomes and follow up of Go Teams ICAO TF/9

-END-

Documents

Summary of Discussions Meetings Seminars and Workshops... · SUMMARY OF DISCUSSIONS ... Doc 9997 PBN Operational Approval Manual 2.3 The PBN TF was informed that the following training