aeronautical information services to aeronautical ... meeting metadata/ais-aimsg... · (6 pages)...

(6 pages)

AERONAUTICAL INFORMATION SERVICES TO AERONAUTICAL INFORMATION MANAGEMENT STUDY GROUP (AIS-AIMSG)

FIFTH MEETING

Montréal, 7 to 11 November 2011

Agenda Item 9: Other Business

Report on IFPP Activities which Impact on Annex 4, Annex 15 and related manuals

(Prepared by R. Luccioli)

SUMMARY

This information paper reports on the activities carried out by the ICAO Instrument Flight Procedure Panel (IFPP) relating the development of Amendment 57 Material for Annex 4 (Date of applicability: 14/11/2013) and Amendment 37 Material for Annex 15 (Date of applicability: 14/11/2013). The IFPP is also progressing material for the Doc 8126 (AIS Manual) and Doc 8697 (Charting Manual), whether these are involved. The group is invited to note the content of this document.

1. INTRODUCTION

The Information Paper presents a report on the activities of the Instrument Flight Procedure Panel, in relation to charting, publication issues and navigation data requirements, and how this has an impact on Annex 4, Annex 15 and related manuals.

2. MATERIAL DEVELOPED FOR INCLUSION IN ANNEX 4 AND 15

2.1 SBAS Charting and Publication. Document 8168 recognizes APV I/II - SBAS Approach Procedures. For these procedures to be charted and encoded in navigation databases intended for on-board use. There is a minimum amount of information required for publication by the States. Specific aspects of charting SBAS procedures have been discussed.

a) SBAS procedures should be charted as RNAV (GNSS) procedures (e.g. RNAV (GNSS) Z RWY 17L, where the trailing alpha character “Z” indicates this is the first of multiple GNSS procedures to runway 17 L). The procedure title remains

AIS-AIMSG/5-IP/3 02/11/11

AIS-AIMSG/5-IP/3

- 2 -

the same, “RNAV (GNSS) RWY XX”, regardless of SBAS LPV minima. This permits a standardized ATS phraseology for all the procedure types that are supported with SBAS;

b) SBAS procedures may be selected either with entry of a channel number or via a menu driven process; The channel number is a five digit number that must be regionally unique. The SBAS channel number range is from 40,000 to 99,999. Channel number assignments are required for LPV and LP procedures.

c) In order to confirm procedure identification and selection, RPI (Reference Path Identifier) is charted. The SBAS RPI is a three or four character field in the SBAS FAS data block. For a WAAS procedure, the leading alpha character is “W”. The middle two characters are numeric characters representing the runway number. Annex 10 suggests that the leading alpha character for an EGNOS procedure is “E”.

d) Since SBAS avionics may be used to fly different procedure types, it is necessary

to standardize how these various lines of minima are charted; LPV and LP procedures, if they exist to the same runway, are charted separately. The separate charting is required since the VAL in the FAS data block, the RPI and channel numbers will be different.

2.2 Material relating SBAS Charting and Publication, developed for Annex 4, Annex 15 is presented in Appendix A.

2.3 GLS Procedure Publication. ICAO Document 8168 recognizes GBAS GLS-type Approach Procedures. For these procedures to be adequately promulgated through charting and encoded in navigation databases intended for on-board use there is a minimum amount of information required for publication by the States. The minimum information to be published with a GLS procedure has been identified and are hereafter listed:

a) Reference Path Identifier (RPI) b) Channel Number

c) GBAS Reference Point information, to include: latitude/longitude, identifier, service volume radius, MSL elevation, and ellipsoid height.

2.4 Material relating GLS Procedure Publication developed for Annex 4, Annex 15 is presented in Appendix A

2.5 Publication of magnetic bearings on RNAV Routes. Several ICAO Annexes and Documents contain a dedicated Appendix outlining aeronautical data quality requirements i.e. accuracy, resolution and integrity classification for main aviation data.

Magnetic bearing data for RNAV Routes should be classified within the ‘Bearing’ type of data and treated as airway segment related information. Therefore, consideration was given for including magnetic bearing in the corresponding ‘Bearing’ Table of Appendixes to Annex 4, 11, 15, applying the same integrity, publication/charting resolution and accuracy level as determined for airway segment (conventional) bearing. A specific explanatory text on how States should apply publication of magnetic bearing for RNAV Route segments for addition to Annex 15 and Doc. 8126 should be provided.

2.6 Material relating Publication of magnetic bearings on RNAV Routes developed for Annex 4, Annex 15 is presented in attachment to this document (Appendix B).

AIS-AIMSG/5-IP/3

- 3 -

2.7 Charting concepts of Point-in-Space (PinS) approach manoeuvring visual segments (VS). Proposals for Annex 4 charting requirements for helicopter PinS approach procedures that contain a maneuvering visual segment have been developed.

Inset or Continuation Sheet. For Proceed Visually procedures there will always be either a Direct VS inset, or a Maneuvering VS inset, or a combination of the two in a single inset (if simple enough to depict), or separate Direct and Maneuvering VS insets. Information in the insets will be charted to scale including obstacles. If an inset is too cluttered, it can be charted on the reverse side of the chart or continuation chart.

The minimum elements that need to be depicted in the inset include:

a) obstacles that penetrate the OIS; b) final approach course to the MAPt c) text for either “Proceed VFR from (MAPt)”, “Proceed Visually from (MAPt)”, or “Maneuver Visually from MAPt”, as appropriate; d) for “Proceed Visually” PinS procedures with a direct visual segment, the descent point (DP), if established, and bearings and distances from MAPt to DP and from MAPt or DP to the heliport/landing location; e) for “Manoeuvre Visually” PinS procedures with a maneuvering visual segment(s), the centreline(s) of the approach surface(s) and the boundary of the maneuvering area without dimensions are charted; f) for “Proceed Visually” PinS” procedures with a “No Fly” area, the text “No Fly ” will be shown, along with the boundary of the “No Fly” area. The “No Fly” area shall be shaded. g) for “Maneuver Proceed Visually” PinS procedures where over flight of the heliport or landing location is prohibited, the bearing and distance, from the MAPt to the heliport or landing location, on a line from the MAPt to the boundary of the prohibited over flight area; and, h) for “Proceed VFR” procedures, only a height above surface (HAS) diagram, which shall include the difference in height between the OCA and the elevation of the highest terrain or water surface within 1.5 km (0.8 NM) of the MAPt and any significant obstacles.

Charting No Fly Areas. When “No Fly” areas are established, the no fly area boundaries will be shown but without dimensions. Plan View. The Direct VS, if one exists, is charted in the plan view. If it doesn’t exist, the bearing and distance from the MAPt to the heliport or landing location is charted. No other information from the inset is charted on the plan view. The plan view includes:

a) heliport/landing location name and elevation to the nearest metre or foot; b) bearing to the nearest degree, and distance to the nearest two-tenths of a kilometre or tenth of a nautical mile from the missed approach point (MAPt) to the heliport/landinglocation;

AIS-AIMSG/5-IP/3

- 4 -

c) textual instructions to “Proceed VFR from xxxx” (MAPt identifier) or “Proceed visually from xxxx” (MAPt identifier) or “Maneuver Visually from xxxx” (MAPt identifier), as appropriate; and, d)obstacles, if not included, in an inset.

Profile View. The profile view contains the information relating to the instrument procedure profile and the Direct VS centreline of the approach surface. The profile view of the chart will include:

a) Fixes, altitudes and distances up to the MAPt b) The profile and track from the MAPt to the heliport or landing location c) The descent point, if established d) The descent angle from the MAPt or DP e) The heliport crossing height (HCH) f) The text “Proceed Visually” is located under the visual segment profile

Profiles of maneuvering VS centreline(s) of the approach surface(s) are not charted since the maneuvering VS centreline(s) of the approach surface(s) will always conform to the Annex 14, Volume II heliport OLS. The visual segment descent angle (VSDA) of 8.3° (14.6%) provides a 1.2° buffer above the sloping OLS. Additionally, the profile from the MAPt of PinS approach maneuvering visual segment to the centreline of the approach surface is not defined.

2.8 Material relating Charting concepts of Point-in-Space (PinS) approach manoeuvring visual segments (VS) developed for Annex 4 is presented is presented in Appendix C.

2.9 Charting concepts of Point-in-Space (PinS) departure manoeuvring visual segments (VS). Charting concepts of Point-in-Space (PinS) departure maneuvering visual segments (VS) have been developed and material for Annex 4 developed.

Using the departure maneuvering visual segment (VS) procedure design criteria previously developed, the discussions have led to the identification of principles for the charting of the subject procedures

Maneuvering VS Procedure Charting. The heliport, the departure VS maneuvering area and the IDF shall be charted on the departure maneuvering VS inset. The information in the departure maneuvering VS inset shall be depicted to scale. Other items included on the inset or departure chart are:

a) Centreline(s) of the take-off climb surface(s) and direction(s). b) The IDF MCA. c) Maneuvering area boundaries. d) The track of the first instrument segment originating from the IDF. e) All penetrations of the OIS. f) “No Fly” areas and their boundaries.

Departure Procedure with Maneuvering VS Inset on a Continuation Sheet. If the departure maneuvering VS inset is depicted on a continuation sheet or the verso of the departure procedure chart, the departure procedure chart shall be annotated directing the pilot to a continuation sheet or reverse side of the chart.

2.10 Material relating Charting concepts of Point-in-Space (PinS) departure manoeuvring visual segments (VS) developed for Annex 4 is presented in Appendix D.

AIS-AIMSG/5-IP/3

- 5 -

2.11 Development of charting, data capturing and publication criteria for PinS operations for helicopters . It has been proposed to introduce aeronautical data quality requirements (accuracy, integrity classification, publication & charting resolution) associated to HCH (Helicopter Crossing Height).

Definitions, abbreviations and the numerical requirements for HCH to be included in ICAO Annex 4 and Annex 15 have been developed.

For defining the HCH data quality elements, the supporting material related to chart/publication resolution and integrity class contained in industry standards DO-201A/ ED-77A ‘Standards for Aeronautical Information’ has been used as recommended by Annex 4 ‘Aeronautical Charts’, Chapter 2, paragraph 2.17 ‘Aeronautical data’.

The proposed definition for HCH also references the term “Heliport Reference Point” (HRP). However, some of the ICAO documents have already considered the term HRP (acronym and/or definition) together with its assigned quality data numerical requirements. Where missing, for consistency reason, inclusion of HRP definition & acronym in these documents has also been considered in the amendment proposal presented in Appendix E.

2.12 Material relating charting, data capturing and publication criteria for PinS operations for helicopters developed for Annex 4, Annex 15 is presented Appendix E.

2.13 Depiction of RNP Navigation Accuracies on RNP Route Segments. It was agreed that amendments to Annex 15, Annex 4, Annex 4 Appendix 2, Doc 8697 and, Doc 8168 would be required to standardize the depiction of route segment RNP Navigation Specification accuracy requirements. Four different RNP Navigation Specification accuracy requirement depiction methods have been discussed. The following criteria, named “Charting by Exception” has been recognized to be the best methodology to follow:

a) Charting by Exception: Charting of the route segment RNP Navigation Specification accuracy requirement by exception. In this case, there is a general statement in the State’s AIP and/or the chart legend such as, “All route segment Navigation Specification accuracy requirements are RNP x.x, except where otherwise noted.” If a specific route segment RNP Navigation Specification accuracy requirement differs from x.x, the RNP Navigation Specification accuracy requirement will be charted in the route segment data.

This charting methodology reduces chart clutter. It involves statements of the RNP Navigation Specification accuracy requirements in the State AIP for specific air space and in the chart legend note citing the accuracy requirement for the RNP route segments on the chart. When the required RNP Navigation Specification accuracy requirement differs from the standard value, information is charted by exception in the route segment data.

2.14 Material relating the depiction of RNP Navigation Accuracies on RNP Route Segments developed for Annex 4, Annex 15 is presented in Appendix F.

3. MATERIAL DEVELOPED FOR INCLUSION IN DOC 8697 (CHARTING MANUAL)

3.1 GLS Procedure Publication : Material developed for DOC 8697 is presented in Appendix A. The material is considered finalized.

3.2 SBAS Charting and Publication: Material developed for DOC 8697 is presented in Appendix A. The material is considered finalized.

AIS-AIMSG/5-IP/3

- 6 -

3.3 Charting concepts of Point-in-Space (PinS) approach maneuvering visual segments (VS): Material developed for DOC 8697 is presented in Appendix C. The material is under discussion.

3.4 Charting concepts of Point-in-Space (PinS) departure maneuvering visual segments (VS): Material developed for DOC 8697 is presented in Appendix D. The material is under discussion.

3.5 Depiction of RNP Navigation Accuracies on RNP Route Segments: Material developed for DOC 8697 is presented in Appendix F. The material is considered finalized.

4. MATERIAL DEVELOPED FOR INCLUSION IN DOC 8126 (AIS MANUAL)

4.1 Publication of magnetic bearings on RNAV Routes. This addresses publication of magnetic bearings on RNAV routes in DOC 8126. Material developed for DOC 8126 is presented in Appendix B.

5. ACTION BY THE AIS-AIMSG

5.1 The AIS-AIMSG is invited to:

a) Note the contents of the Information Paper.

— — — — — — — —

AIS-AIMSG/5-IP/3 Appendix A

02/11/11

APPENDIX A

GLS PROCEDURE PUBLICATION, SBAS CHARTING AND PUBLICATION.

ICAO ANNEX 4 - AERONAUTICAL CHARTS

1. Text to be deleted is shown with a line through it. text to be deleted

2. New text to be inserted is highlighted with grey shading. new text to be inserted

3. Text to be deleted is shown with a line through it followed by the replacement text which is highlighted with grey shading.

new text to replace existing text

Add the following to Annex 4, Chapter 11 Paragraph 8 Supplementary Data. 11.10.8.9 SBAS Supplementary Information. For SBAS procedures, the SBAS Service Provider, the SBAS Procedure Channel Number and Reference Path Identifier shall be shown. Note: The SBAS Reference Path Identifier is defined in Procedures for Air Navigation Services – Aircraft Operations (PANS-OPS, Doc 8168), Volume II, Part III, Section 3, chapter 5. The SBAS procedure Channel Number range is defined in Doc 8168, Volume II Part III, Chapter 5, Paragraph 7.5 a). 11.10.8.10 For GBAS procedures, the Reference Path Identifier as defined Procedures

for Air Navigation Services – Aircraft Operations (PANS-OPS, Doc 8168), Volume II, Part III, Section 2, Chapter 6, Appendix B, paragraph 2.5 shall be shown. 11.10.8.11 For GBAS procedures, the GBAS Channel Number as defined in Annex 10,

Volume I, Attachment D, paragraph 7.7 shall be shown.

ICAO ANNEX 15 - AERONAUTICAL INFORMATION SERVICES





Amend Annex 15, Appendix 1, Section AD 2.19, as follows: 3) frequency(ies) channel numbers(s), Service Provider, and Reference Path Identifier(s) (RPI), as appropriate. 6) elevation of the transmitting antenna of DME to the nearest 30 m (100 ft) and of DME/P to the nearest 3 m (10 ft); elevation of GBAS Reference Point to the nearest metre or foot and the ellipsoid height of the point to the nearest metre or foot. For SBAS, the ellipsoid height of the landing threshold point (LTP) or the fictitious threshold point (FTP) to the nearest metre or foot, 7) service volume radius from the GBAS Reference Point to the nearest kilometre or nautical mile, and 8) remarks

ICAO DOC 8697 - AERONAUTICAL CHARTING MANUAL





Add a new element in the Instrument Approach Procedure Chart Table of Doc 8697:

Annex 4 Reference

Details Draughting Illustration

11.10.8.9 Depiction of SBAS Supplemental Information. The Service Provider, SBAS Channel Number and the Reference Path Identifier (RPI) shall be shown.

EGNOS (Service Provider) CH 45513 (Channel Number) E17A (Reference Path Identifier)

Add a new element in the Instrument Approach Procedure Chart Table of Doc 8697: Annex 4 Reference


11.10.8.10 Depiction of GBAS Supplemental Information. The GBAS Channel Number and the Reference Path Identifier (RPI) shall be shown.

CH 25513 (Channel Number) G17A (Reference Path Identifier) or AFTG (Reference Path Identifier)

AIS-AIMSG/5-IP/3 Appendix B

02/11/11

APPENDIX B

PUBLICATION OF MAGNETIC BEARINGS ON RNAV ROUTE


Add the following in Annex 4 ‘Aeronautical Charts’, Appendix 6 ‘Aeronautical Data Quality Requirements’, Table 4: Table 4 Bearing

Bearing Chart Integrity Resolution Classification

Airway segments (including RNAV)…….……………. 1 degree 1 x 10-3 routine . .

ICAO ANNEX 15 - AERONAUTICAL INFORMATION SERVICES Add the following in Annex 15 ‘Aeronautical Information Services’, Appendix 1 ‘Contents of Aeronautical Information Publication (AIP). ENR 3.3 Area navigation routes Detailed description of area navigation (RNAV) routes, including: . . 3) Magnetic bearing to the nearest degree, Ggeodesic distance to the nearest tenth of a

kilometer or tenth of a nautical mile between defined end points and distance between each successive designated significant point;

…. Add the following in Annex 15 ‘Aeronautical Information Services’, Appendix 7 ‘Aeronautical Data Quality Requirements’, Table A7-4: Table A7-4 Bearing

Bearing Publication Integrity Resolution Classification

Airway segments (including RNAV)………………….. 1 degree 1 x 10-3 Routine . .

ICAO DOC 8126 - AERONAUTICAL INFORMATION SERVICES MANUAL Insert the following text in Doc. 8126 ‘AIS Manual’, Appendix to Chapter 5 ‘Explanatory Notes on the Specimen AIP’: ENR 3.3 AREA NAVIGATION ROUTES Detailed description of area navigation (RNAV) routes, including: . . 3) Magnetic bearing to the nearest degree, Ggeodesic distance to the nearest tenth of a

kilometer or tenth of a nautical mile between defined end points and distance between each successive designated significant point.

The magnetic bearing is calculated by applying the magnetic variation at a significant point to the calculated true course to another significant point and is published to the nearest degree. When an RNAV route overlays an existing conventional airway, tracks or VOR radials to the nearest degree are published. Magnetic bearings for each segment are published depending on the direction of the cruising levels i.e. bidirectional or one- way airway only.

. Replace respective ENR 3.3-1 page in the Specimen AIP of Doc. 8126 ‘AIS Manual’:

AIS-AIMSG/5-IP/3 Appendix C

02/11/11

APPENDIX C

CHARTING CONCEPTS OF POINT-IN-SPACE APPROACH MANEUVERING VISUAL SEGMENTS (VS)

ICAO ANNEX 4 - AERONAUTICAL CHARTS Amend Annex 4, Chapter 11, Section 11.11 as follows. CHAPTER 11. INSTRUMENT APPROACH CHART — ICAO 11.11 Helicopter point-in-space (PinS) approach procedures Note. — The provisions of Chapter 11, outside the scope of this paragraph, also apply to charts depicting helicopter (PinS) approach procedures unless otherwise specifically addressed within this paragraph. 11.11.1 The plan view shall include: a) heliport/landing location name and elevation to the nearest metre or foot; b) bearing to the nearest degree, and distance to the nearest two-tenths of a kilometre or tenth of a nautical mile from the missed approach point (MAPt) to the heliport/landing location; c) textual instructions to “Proceed VFR from xxxx” (MAPt identifier) or “Proceed visually from xxxx” (MAPt identifier) or “Maneuver Visually from xxxx” (MAPt identifier), as appropriate; and, d) obstacles, if not included, in an inset. Note. — Appropriate obstacles to be charted are provided by the procedure designer. 11.11.2 An inset shall be used to show the following: a) obstacles that penetrate the OIS; b) final approach course to the MAPt c) text for either “Proceed VFR from (MAPt)”, “Proceed Visually from (MAPt)”, or “Maneuver Visually from MAPt”, as appropriate; d) for “Proceed Visually” PinS procedures with a direct visual segment, the descent point (DP), if established, and bearings and distances from MAPt to DP and from MAPt or DP to the

heliport/landing location; e) for “Manoeuvre Visually” PinS procedures with a maneuvering visual segment(s), the centreline(s) of the approach surface(s) and the boundary of the maneuvering area without dimensions are charted; f) for “Proceed Visually” PinS” procedures with a “No Fly” area, the text “No Fly” will be shown, along with the boundary of the “No Fly” area. The “No Fly” area shall be shaded. g) for “Maneuver Proceed Visually” PinS procedures where over flight of the heliport or landing location is prohibited, the bearing and distance, from the MAPt to the heliport or landing location, on a line from the MAPt to the boundary of the prohibited over flight area, and the boundary of the prohibited over flight area; and h) for “Proceed VFR” procedures, only a height above surface (HAS) diagram, which shall include the difference in height between the OCA and the elevation of the highest terrain or water surface within 1.5 km (0.8 NM) of the MAPt and any significant obstacles. Note 1. — The inset specified above is a separate framed diagram located on the plan view or on a the verso of the chart or continuation sheet, which is charted to scale and is used to show pertinent information “close-in” to the heliport or landing location. Note 2. — Appropriate obstacles are provided by the procedure designer. 11.11.3 The inset for either type of PinS procedure shall not be used to depict instructions, non-operational notes, descent gradients/angles, or missed approach track or instructions. 11.11.4 The profile view shall contain information relating to the instrument procedure profile and the direct visual segment profile, if it exists, with the text “Proceed VFR”, “Proceed Visually” or “Maneuver Visually”, as appropriate. There is no profile view information for either “Proceed VFR” or “Maneuver Visually” procedures because there is no defined visual segment vertical profile for these procedures. The profile view of the direct visual chart shall include: a) Fixes, altitudes and distances up to the MAPt b) The profile and track from the MAPt to the heliport or landing location c) The descent point if established d) The descent angle from the MAPt or DP e) The heliport crossing height (HCH) f) The text “Proceed Visually” is located under the visual segment profile

11.11.5 Recommendation.— A descent table should be shown indicating descent angle and descent rate in metres per minute (feet per minute) for appropriate speeds for applicable segments, i.e. final approach fix (FAF) to step down fix (SDF), SDF to missed approach point (MAPt), and descent point (DP) to heliport reference point (HRP). Note. — The descent table may be placed in the lower left or right corner of the plan view directly above the profile view. 11.11.6 Airspeed restrictions shall be depicted on the chart textually as “Maximum airspeed xxx km/h (xxx KIAS)” when less than 165 km/h (90 KIAS).

ICAO DOC 8697 - AERONAUTICAL CHARTING MANUAL Amend Doc 8697, Chapter 11as follows. Annex 4 Reference

General

11.11.2 An inset shall be used to show the following: a) obstacles; b) final approach course to the MAPt; bc) text to either “Proceed VFR from (MAPt)”or to, “Proceed visually from (MAPt)”, or “Manoeuvre visually from (MAPt), as appropriate; cd) for all “Proceed visually PinS” procedures only, the visual segment, the descent point (if established) and bearings and distances from MAPt to DP and from MAPt or DP to the heliport/landing location; and e) for “Proceed visually PinS” procedures with approach manoeuvring visual segment(s) only, the centreline(s) of the approach surface(s), shown with a dotted line and an arrowhead, and the boundary of the approach manoeuvring area without dimensions; f) for “Proceed visually PinS” procedures with approach manoeuvring visual segment(s) and a “No fly” area only, the text “NO FLY” is depicted. The boundary of the “No fly” area shall be shown. g) for “Proceed visually PinS” procedures with approach manoeuvring visual segment(s) and over flight of the heliport/landing location is prohibited, the bearing and distance and a line from the MAPt to short of the heliport/landing location and the boundary of the prohibited over flight area; and dh) for “Proceed VFR” procedures only, a height above surface (HAS) shall include the difference in height between the OCA and the elevation of the highest terrain or water surface within 1.5 km (0.8 NM) of the MAPt and any significant obstacles.

11.11.4 c) the text “Proceed VFR” or, “Proceed visually” or “Manoeuvre visually”, as appropriate; and d) the descent angle from the MAPt or DP, if established.

11.11.2 Maneovering Area Insets

Add the following illustrations to Chapter 11 Section 11.2. Annex 4 Reference

Details Draft Illustration

11.11.2 Maneovering Area without a “No Fly” Area. If there is not a “no fly area” the approach maneuver area can shall be established, depending on the approach maneovering VS centerline(s) of the approach surface(s) and extension of the maneovering area may be on one or both sides of the direct VS track or of the track from the MAPt direct to the heliport if a direct VS does not exist.

11.11.2. Maneovering Area with a “No Fly” Area. If there is a “no fly area”, the boundary limit of the approach maneuver area shall be charted as the approach maneovering VS centerline of the approach surface. The boundary of the “No Fly” area shall be depicted and the no fly area shaded.

11.11.2 Maneovering Area with Heliport Over flight Prohibited. When there is no direct VS there is usually an obstacle that prevents over flying the heliport or landing location. When over flight of the heliport is prohibited, there is a minor adjustment to the boundaries of the “no fly” area. The boundary shall arc around the heliport terminating prior to the approach maneovering VS centreline(s) of the approach surface (s).

11.11.2 Maneovering Area with Heli- Port Over Flight Prohibited and a “No Fly”area. The charting of the approach maneovering area is a combination of the charting depicted in the previous two figures.

AIS-AIMSG/5-IP/3 Appendix D

02/11/11

APPENDIX D

CHARTING CONCEPTS OF POINT-IN-SPACE DEPARTURE MANEUVERING VISUAL SEGMENTS (VS)


Add a new section 9.11 to Annex 4 Chapter 9 Standard Departure Chart.

9.11 Helicopter Point-in-Space (PinS) Departure Maneuvering Visual Segment (VS) 9.11.1 General. The charting of the departure maneuvering VS includes a maneuvering area and at least one maneuvering VS centreline of the take-off climb surface. The departure maneuvering VS area is charted either in an inset on the departure procedure plan view or on a continuation sheet or the verso of the chart. Information depicted in the departure maneuvering VS inset is charted to scale. 9.11.2 Annotation on Departure Procedure Chart. If the departure maneuvering VS area is not depicted in an inset on the plan view, then the instrument departure chart shall contain an annotation directing the pilot to the continuation sheet or the verso of the chart. 9.11.3 Maneuvering Area Variations. Departure maneuvering areas are established with or without a “No Fly”. “No Fly” area boundaries are charted. The only depiction in the “No Fly” area is the text “No Fly”. 9.11.4 Additional Items to be charted. The following shall also be charted.

a) Centreline(s) of the take-off climb surface(s) and direction(s). b) The IDF MCA. c) Maneuvering area boundaries. d) The track of the first instrument segment originating from the IDF. e) All penetrations of the OIS. f) “No Fly” areas and their boundaries.

ICAO DOC 8697 - AERONAUTICAL CHARTING MANUAL Add a new section 9.11 to Doc 8697. Annex 4 Reference

General

9.11.1 9.11.4

The departure maneovering visual segment (VS) area may be charted on a chart separate from the departure procedure chart. The heliport and the initial departure fix (IDF) shall be charted on the departure maneovering segment inset. Other items included on the chart are:

a) Centreline(s) of the take-off climb surface, which shall be charted with a dotted line with an arrowhead. The centreline of the take-off climb surface direction shall be charted.

b) The IDF minimum crossing altitude (MCA) shall be charted. c) Maneovering area boundaries without dimensions. The boundaries

shall be charted as light lines. d) The track of the first segment in the instrument phase of the

departure procedure shall be charted. e) All penetrations of the obstacle identification surface (OIS) shall

be charted. The information in the inset shall be depicted to scale.

Annex 4 Reference

Details Drafting Illustration

9.11.2 Annotation on the Departure Procedure Chart. If the departure maneovering visual area inset for VS departures is depicted on a separate chart, the departure procedure chart shall contain a box note directing the pilot to the verso of the chart or a continuation sheet.

See Details of the Departure Maneovering Visual Area

On the Following Chart

Annex 4 Reference

9.11.3 Types of Departure Maneovering VS Areas There are two types of Departure Maneovering VS Areas. They are:

a) Departure maneovering VS area without a “No Fly” area. b) Departure maneovering VS area with a “No Fly” area.

Annex 4 Referenc

e

Details Drafting Illustration

9.11.3 Maneovering Area Types

Depiction of Departure Maneovering VS Chart without a “No Fly” Area. Without a “No Fly” area the departure maneovering area is centered on the Heliport Reference Point (HRP) with no restriction as to the direction of turn.

Depiction of Departure

Maneovering VS Chart with a “No Fly” Area. The boundaries of the departure maneovering area shall be depicted along with the heliport centerline of the take-off climb surface including the direct VS departure track if one exists.

AIS-AIMSG/5-IP/3 Appendix E

02/11/11

APPENDIX E

DEVELOPMENT OF CHARTING, DATA CAPTURING and PUBLICATION

CRITERIA FOR PinS OPERATIONS FOR HELICOPTERS ICAO ANNEX 4 - AERONAUTICAL CHARTS Insert the following definition in the appropriate location in Annex 4 “Aeronautical Charts”, Chapter 1, paragraph 1.1” Definitions”. …. Heliport reference point – The designated location of the heliport or landing location. ….

Insert the following aeronautical data requirements for heliport crossing height related to chart resolution and data integrity classification in the appropriate location in Annex 4 “Aeronautical Charts”, Appendix 6, Table 2. Table 2. Elevation/altitude/height

Elevation/altitude/height Chart resolution Integrity/Classification

.… Heliport crossing height, PinS approaches………1 m or 1 ft 1 x 10-5/essential ….


Insert the following aeronautical data quality requirements for heliport crossing height related to the order of publication resolution and data integrity classification in the appropriate location in Annex 15 ‘Aeronautical Information Services’, Appendix 7, Table A7-2. Table A7-2 Elevation/altitude/height

Elevation/altitude/height Publication Integrity resolution classification

…… Heliport crossing height, PinS approaches……………1 m or 1 ft 1 x 10-5 essential ……

AIS-AIMSG/5-IP/3 Appendix F

02/11/11

APPENDIX F


Add the following to Chapter 7.9.3.1.1:

m) The route segment RNP Navigation Specification accuracy requirements shall be published on a route segment basis in the State’s AIP and a designated standard RNP Navigation Specification accuracy requirements may shall be depicted in the chart legend. When the RNP Navigation Specification accuracy requirement for a specificied route segment differs from a designated standard RNP Navigation Specification in the State’s AIP or the chart legend RNP Navigation Specification accuracy requirement, it shall be depicted in the route segment data.

-----

Add the following to Chapter 9.9.4.1.1. a):

7) The departure route segment RNP Navigation Specification accuracy requirements shall be published on a route segment basis in the State’s AIP and a designated standard RNP Navigation Specification accuracy requirements may shall be depicted on the departure chart legend. When an RNP Navigation Specification accuracy requirement for a specificed departure route segment differs from a designated standard RNP Navigation Specification that in the State’s AIP or the chart legend RNP Navigation Specification accuracy requirement, it shall be depicted in the specific departure route segment data.

----- Add the following to Chapter10.9.4.1.1 a):

7) Arrival route segment RNP Navigation Specification accuracy requirements shall be published on a route segment basis in the State’s AIP and the designated standard RNP Navigation Specification accuracy requirement may shall be depicted in the arrival chart legend. When an RNP Navigation Specification accuracy requirement for a specificed arrival route segment differs from a designated standard RNP Navigation Specification that in the State’s AIP or the chart legend RNP Navigation Specification accuracy requirement, it shall be depicted in the specific arrival route segment data.


Add the following to Annex 15 Appendix 1 ENR 3.1 Lower ATS routes:

7) the RNP Navigation Specification accuracy requirement for the RNP route segment.

---

Add the following to Annex 15 Appendix 1 ENR 3.2 Upper ATS routes:


---

Add the following to Annex 15 Appendix 1ENR 3.3 Area navigation routes:


--- Add the following to Annex 15 Appendix 1 ENR 3.4 Helicopter routes:


----

Add a new paragraph to Annex 15 Appendix 1 as ENR 6.1 as follows.

ENR 6.1 En Route Charting by Exception

The State shall establish standard Navigation Specification RNP route segment accuracy requirements for specified airspace in its AIP and/or on the appropriate chart legends. Specific RNP route segment Navigation Specification RNP route segment accuracy requirements that differ from the standard in the State’s AIP and/or on the chart legend shall be charted by exception by depicting the Navigation Specification RNP accuracy requirement for that RNP route segment in the route segment data.

ICAO DOC 8697 - AERONAUTICAL CHARTING MANUAL

Add new paragraphs as follow: 7.9.3.1.1

m) Route Segment RNP Accuracies. The chart legend may shall include the note, “All RNP route segment RNP Navigation Specification accuracy requirements are 2.0, except where otherwise noted”. When the route segment RNP Navigation Specification accuracy requirement differs from 2.0, the RNP Navigation Specification accuracy requirement shall be depicted in the route segment data.

----- 9.9.4.1.1 a)

7) Departure Route Segment RNP Accuracies. The chart legend may shall include the note, “All RNP departure route segment RNP Navigation Specification accuracy requirements are 1.0, except where otherwise noted”. When the route segment RNP Navigation Specification accuracy requirement differs from 1.0 the RNP Navigation Specification accuracy requirement shall be depicted in the departure route segment data.

----- 10.9.4.1.1 a)

7) Arrival Route Segment RNP accuracies. The chart legend may shall include the note, “All RNP arrival route segment RNP Navigation specification accuracy requirements are 1.0, except where otherwise noted”. When a route segment RNP Navigation Specification accuracy requirement differs from 1.0 the RNP Navigation Specification accuracy requirement shall be depicted in the route segment data.

-----

Add a new element in the En Route Chart Table of Doc 8697: Annex 4 Reference


7.9.3.1.1m)

Depiction of Route Segment RNP Navigation Specifications. When different than the chart legend accuracy, or the standard published in the AIP, the RNP Navigation Specification accuracy requirement shall be depicted in the Route Segment Data.

----- Add a new element in the Departure Chart Table of Doc 8697:

Annex 4 Reference


9.9.4.1.1a) 7)

Depiction of Departure Route Segment RNP Navigation Specification accuracies. When different than the chart legend value or the standard published in the AIP, the RNP Navigation Specification accuracy requirement shall be depicted in the Departure

Route Segment Data.

----- Add a new element in the Arrival Chart Table of Doc 8697:

Annex 4 Reference


10.9.4.1.1a) 7)

Depiction of Arrival Route Segment RNP Navigation Specification Accuracies. When different than the chart legend value or the standard published in the AIP, the RNP Navigation Specification accuracy requirement shall be depicted in the Arrival Route Segment Data.

— END —