(Appendix E to the NAT IMG/44 Summary of Discussions NAT IMG Decision 44/02 refers)

Transcription

1 TASK LIST FOR THE TRANSITION FROM MNPS TO PBN AS ENDORSED BY NAT IMG/44 (Appendix E to the NAT IMG/44 Summary of Discussions NAT IMG Decision 44/02 refers) Editorial Note Compared to the last published version, text proposed to be deleted uses strikeout (text to be deleted), and text proposed to be added is with grey shading (text to be inserted). Completed tasks or sub-tasks are shown with greyed out background, with white background kept on the part of the task where changes have been made compared to the last published version. NAT MNPS TO PBN TRANSITION MILESTONES TABLE 1 1 Milestone Task Completed Task considered complete (subject to confirmation) No. Timeline Milestone Comments An aircraft that is approved (certified) for RNAV10 (RNP10) and/or RNP4 can be issued an MNPS operational authorization without further examination of the navigation specification component. The indicator X will still be required in item 10 of the ICAO FPL For new MNPS operational approvals, discontinue the use of MNPS navigation specification (6.3 NM standard deviation). New MNPS operational approvals will be based on RNAV10 (RNP10) or RNP4 navigation specifications. Existing aircraft having MNPS approvals based on the 6.3 NM standard deviation will be allowed to continue operating in the NAT MNPS airspace Modify the definition of the NAT airspace such that the NAT MNPS airspace will be replaced with that of the NAT High Level Airspace. That airspace will be defined in such a way that MNPS, RNAV10 and RNP4 aircraft are deemed to satisfy the prescribed NAT PBN operation requirements All aircraft operating in the NAT High Level Airspace shall have an operational approval based on the RNAV10 (RNP10) or RNP4 navigation specification requirements. Aircraft having MNPS approvals based on the 6.3 NM standard deviation will not be allowed anymore Allow applying 50NM lateral separation between a mix of MNPS, RNAV10 and RNP4 approved aircraft on intersecting and non-intersecting tracks in the NAT High Level airspace. The timing of this depends on the time that is needed to prepare and process a Doc7030 amendment. This is concurrent with 3 and it is assumed that document changes will take account of both s This is concurrent with 2 and it is assumed that document changes will take account of both s The timeline applies to specific portions of the NAT Regions (where the benefits would be tangible) 1 Each implementation phase of RLatSM shall be harmonized to an appropriate step or benchmark (as determined by the NAT IMG) contained in this Plan. According to the Summary of actions planned or initiated to address the RLatSM Task List, as endorsed by NAT IMG/38 (Refer to NAT IMG/38 SD Appendix H), the RLatSM Phase 1 implementation date is to be in the 2014/2015 time frame, harmonized to the NAT MNPS to PBN Transition Plan. May 2014 Page 1 of 8

2 NAT MNPS to PBN Transition Task List Table 1.1 Milestone An aircraft that is approved (certified) for RNAV10 (RNP10) and/or RNP4 can be issued an MNPS operational authorization without further examination of the navigation specification component. The indicator X will still be required in item 10 of the ICAO FPL. The timing of this depends on the time that is needed to prepare and process a Doc7030 amendment Notify States of the change and plans to facilitate necessary regulatory actions, update of approval/authorization, procedures, training of staff etc and request that operators be notified. Complete as soon as possible in the form of a state letter when authorized by the NAT IMG/SPG Modify document Modify the MNPS operations manual (NAT DOC007). ; NAT SARSIG (OPS/AIR) Modify NAT State documents Appropriate IMG working group(s) to propose wording for AIPs Modify NAT ATS unit documentation and ATS operations manuals. A draft DOC7030 amendment has been prepared by SARSIG and forwarded to the IMG for approval. PfA (EUR/NAT-S12/16 - NAT 4-2 in progress - awaiting final approval by Council) - proposed effective date 10 January 2013 OPS-AIR will work with the DMO on this task. Try to harmonize text in State documents as much as possible. CLOSED CLOSED CLOSED May 2014 Page 2 of 8

3 NAT MNPS to PBN Transition Task List Table 1.2 Milestone For new MNPS operational approvals, discontinue the use of MNPS navigation specification (6.3 NM standard deviation). New MNPS operational approvals will be based on RNAV10 (RNP10) or RNP4 navigation specifications. Existing aircraft having MNPS approvals based on the 6.3 NM standard deviation will be allowed to continue operating in the NAT MNPS airspace. This is concurrent with 3 and it is assumed that document changes will take account of both s Effect global coordination. Complete as soon as possible in the form of a state letter when authorized by the NAT IMG/SPG Notify States of the change and plans to facilitate necessary regulatory actions, update of approval/authorization, procedures, training of staff etc and request that operators be notified. ICAO RO; NAT CNSG (OPS/AIR) Should be done in the form of a state letter when authorized by the NAT IMG/SPG. PfA notification (task 2.4 refers) Initiate an Annex 6 amendment. SARSIG has determined that an Annex 6 amendment is not required Modify DOC ; NAT CNSG (OPS/AIR) Modify NAT Operations and Airspace Manual (NAT Doc 007) ; NAT SARSIG; NAT CNSG (OPS/AIR) Modify NAT State documents. ; NAT CNSG (OPS/AIR) This will require states to modify regulations and certification documents. Iceland to present draft PfA to /41 PfA 13/33 (SL ) to work with NAT DMO Try to harmonize text in State documents as much as possible Appropriate IMG working group(s) to propose wording for AIPs Modify NAT ATS unit documentation and ATS operations manuals. May 2014 Page 3 of 8

4 NAT MNPS to PBN Transition Task List Table 1.3 Milestone Modify the definition of the NAT airspace such that the NAT MNPS airspace will be replaced with that of the NAT High Level Airspace. That airspace will be defined in such a way that MNPS, RNAV10 and RNP4 aircraft are deemed to satisfy the prescribed NAT PBN operation requirements. This is concurrent with 2 and it is assumed that document changes will take account of both s Effect global coordination. Complete as soon as possible in the form of a state letter when authorized by the NAT IMG/SPG Notify States of the change and plans to facilitate necessary regulatory actions, update of approval/authorization, procedures, training of staff etc and request that operators be notified. Should be done in the form of a state letter when authorized by the NAT IMG/SPG. PfA notification Initiate an Annex 6 amendment if required. SARSIG has determined that an Annex 6 amendment is not required Modify the NAT Air Navigation Plan Determine vertical and horizontal limits of the NAT High Level Airspace., NAT SOG (NAT MWG input) Modify Doc Develop/agree flight plan indication for approval to fly in the NAT High Level Airspace Modify state documents (list) Appropriate IMG working group(s) to propose wording for AIPs. Airspace definition will need to take account of requirement to monitor safety performance - currently defined as within NAT MNPS airspace This will require states to modify regulations and certification documents. Determine whether it would be possible to redefine the Item 10 X descriptor Try to harmonize text in State documents as much as possible. This material to include detailed guidance for operators on how to indicate navigational capability and how to indicate approval to fly in the NAT airspace where PBO will be applied May 2014 Page 4 of 8

5 Milestone Modify the definition of the NAT airspace such that the NAT MNPS airspace will be replaced with that of the NAT High Level Airspace. That airspace will be defined in such a way that MNPS, RNAV10 and RNP4 aircraft are deemed to satisfy the prescribed NAT PBN operation requirements. This is concurrent with 2 and it is assumed that document changes will take account of both s Initiate consequential amendments to NAT SPG documents to take account of the name change Modify NAT ATS unit documentation and ATS operations manuals. NAT MNPS to PBN Transition Task List Table 1.4 Milestone All aircraft operating in the NAT High Level Airspace shall have an operational approval based on the RNAV10 (RNP10) or RNP4 navigation specification requirements. Aircraft having MNPS approvals based on the 6.3 NM standard deviation will not be allowed anymore Effect global coordination. Complete as soon as possible in the form of a state letter when authorized by the NAT IMG/SPG Notify States of the change and plans to facilitate necessary regulatory actions, update of approval/authorization, procedures, training of staff etc. and request that operators be notified Determine which crew and operator procedures, in addition to navigational performance requirements, should be required to support a NAT MNPS approval such requirements would then be specified for approval to operate in the NAT High Level Airspace ; NAT SARSIG (NAT OPS/AIR) Should be done in the form of a state letter when authorized by the NAT IMG/SPG. PfA Notification NAT OPS/AIR sub-group will initiate this work at December 2012 meeting NAT IMG/43 SoD para 4.27 and Decision 43/07 refer) May 2014 Page 5 of 8

6 Milestone All aircraft operating in the NAT High Level Airspace shall have an operational approval based on the RNAV10 (RNP10) or RNP4 navigation specification requirements. Aircraft having MNPS approvals based on the 6.3 NM standard deviation will not be allowed anymore Modify DOC Modify NAT Operations and Airspace Manual (NAT Doc 007) ; NAT SARSIG Modify NAT State documents. This will require states to modify regulations and certification documents. Based on outcome of will work with NAT DMO Try to harmonize text in State documents as much as possible Appropriate IMG working group(s) to propose wording for AIPs Modify NAT ATS unit documentation and ATS operations manuals. May 2014 Page 6 of 8

7 NAT MNPS to PBN Transition Task List Table 1.5 Milestone Allow applying 50NM lateral separation between a mix of MNPS, RNAV10 and RNP4 approved aircraft on intersecting and non-intersecting tracks in the NAT High Level airspace. The timeline applies to specific portions of the NAT Regions (where the benefits would be tangible) 5.1 TBD Assess the equipment mix of the aircraft fleet operating in the whole of the NAT MNPS airspace (MNPS, RNAV10, RNP4, GNSS). 5.2 TBD Develop a set of system performance criteria for the application of 50 NM lateral separation using a Target Level of Safety (TLS) of 5x10-9 FAPFH applicable to the lateral dimension. 5.3 TBD Determine whether the navigation performance of the population of the fleet of aircraft operating in the NAT is satisfying the criteria specified in task TBD If the result of 5.3 is positive then determine when the change from 60 NM/gentle slope rules to 50 NM separation between aircraft on intersecting and non-intersecting tracks shall take place. 5.5 TBD Notify States of the change and plans to facilitate necessary regulatory actions, update of approval/authorization, procedures, training of staff etc and request that operators be notified. 5.6 TBD Modify Doc7030. An assessment of the equipment mix has been provided for Reykjavik and New York airspaces. Canada and United Kingdom indicate this is not a short term priority (updating GAATS and SAATS); assessing potential benefit to determine whether to initiate this task Iceland considering whether to initiate this task; requires data from other ANSPs. Canada and United Kingdom indicate this is not a short term priority (updating GAATS and SAATS); assessing potential benefit to determine whether to initiate this task. Portugal assessing potential interface issues; foresees shorter term benefits. United States will likely not modify until appropriate ICAO documents amended. Should be done in the form of a state letter when authorized by the NAT IMG/SPG. PfA notification May 2014 Page 7 of 8

8 Milestone Allow applying 50NM lateral separation between a mix of MNPS, RNAV10 and RNP4 approved aircraft on intersecting and non-intersecting tracks in the NAT High Level airspace. The timeline applies to specific portions of the NAT Regions (where the benefits would be tangible) 5.7 TBD Modify the NAT ASM. 5.8 TBD Modify FDPS systems for different FPL processing. Iceland s system already modified; Portugal able to modify in short time frame, United States would be able to modify in short time-frame; Canada and United Kingdom assessing. 5.9 TBD Modify unit documentation and operations manuals. END May 2014 Page 8 of 8