ICAO Amendment 1 - Australian Flight Planning Guidance

Transcription

1 ICAO Amendment 1 - Australian Flight Planning Guidance Amendment 1 to the 15 th Edition of ICAO Doc introduces changes to useable identifiers and codes within the ICAO flight plan, specifically in Items 10 and 18. Alpha-numeric codes have been introduced for use in Item 10a and 10b and for use in the New Item 18 indicator, PBN. The PBN indicator is limited to 8 alpha-numeric entries i.e. 16 characters. Advice from filers around the world is that this is not adequate to capture the equipage of some modern aircraft. To enable the best utilisation of the flight plan fields the following filing guidance will be included in to prioritise and clarify code meanings and their filing. Below is a list of the Item 18 PBN indicator codes promulgated within Amendment 1: Note that there is no provision for other PBN codes (in the form of placeholders) within this indicator. PBN CODE RNAV/RNP Specification A1 RNAV 10 (RNP 10) B1 RNAV 5 all permitted sensors B2 RNAV 5 GNSS B3 RNAV 5 DME/DME B4 RNAV 5 VOR/DME B5 RNAV 5 INS or IRS B6 RNAV 5 LORANC C1 RNAV 2 all permitted sensors C2 RNAV 2 GNSS C3 RNAV 2 DME/DME C4 RNAV 2 DME/DME/IRU D1 RNAV 1 all permitted sensors D2 RNAV 1 GNSS D3 RNAV 1 DME/DME D4 RNAV 1 DME/DME/IRU L1 RNP4 O1 Basic RNP 1 all permitted sensors O2 Basic RNP 1 GNSS O3 Basic RNP 1 DME/DME O4 Basic RNP 1 DME/DME/IRU S1 RNP APCH S2 RNP APCH with BARO-VNAV T1 RNP AR APCH with RF (special authorization required) T2 RNP AR APCH without RF (special authorization required) Due to the limitation of only 8 allowable filed codes, dispatches and filers will need to decide which codes best represent the aircraft s capabilities. For example, the RNAV specification RNAV5 lists six RNAV5 codes which define the specification and the sensor reliance relationship. Many aircraft will be RNAV5 capable using DME, INS/IRS and but very few will utilise LORANC. Flight planning of RNAV5 for Aircraft that utilise all sensors except LORANC would require use of the codes B2, B3, B4 and B5. Given the limited and declining use of LORAN filers and despatchers should, for 1/ FPL - Guidance Material to be incorporated in AIP

2 aircraft able to use all sensors, except LORANC, plan B1 i.e. RNAV5 all permitted sensors. Where aircraft also carry LORANC, this should be flight planned using both B1 and B6. This is one example of why flight planning guidance is expected to be beneficial. The following table details the flight planning guidance for the 2012 NEW flight plan: Flight Plan Item 10 Surveillance (10b) Item 10b should not exceed 11 characters use the following guidelines: 1. If no surveillance equipment for the route to be flown or if equipment is unserviceable insert N otherwise; 2. For SSR Modes A, C or S use only one of the following codes that represents the highest level of surveillance for the route to be flown: L, E, H, S, I, P, X, C and A 3. For ADS-B use the following (up to a maximum of three codes): Either B1 or B2 (for Australian compliant ADSB equipment) and/or Either U1 or U2 and/or Either V1 or V2 4. For ADS-C use the following (up to a maximum of two codes): One or both of D1 and/or G1 Flight Plan Item 18 PBN/ Flight Planning in ITEM 18 PBN/ allows a maximum of 8 alpha numeric codes (16 characters) from a list of 24 allowable codes. For some operators this will require interpolation of the crew training/aircraft certification and regulator authorisation combination in order to best represent the aircraft capabilities within this limitation. The following guidance should simplify this process: 1. If one or more PBN codes are filed R must also be filed in Item 10a. 2. If RNAV 5 and B2, B3, B4 and B5 are applicable use B1 (i.e. LORAN is not required for filing of B1). B6 is to be separately filed if applicable. 3. RNAV 2, RNAV 1 and RNP 1 DME/DME/IRU If DME/DME/IRU is applicable then only file the equivalent alpha 4 code i.e. C4, D4 or O4 and do not file the DME/DME alpha 3 code i.e. C3, D3 and O3. In other words filing of; 2/ FPL - Guidance Material to be incorporated in AIP

3 o o C4 = C3 &C4, and D4 = D3 & D4, and o O4 = O3 & O4. 4. RNP APCH file either S1 or S2 depending on capability but not both as these are mutually exclusive 5. RNP AR APCH file either T1 or T2 depending on capability but not both as these are mutually exclusive Flight Plan Item 18 PBN and Item 10 equipment (10a) Dependencies This table indicates the dependencies between filed PBN codes and Item 10a codes i.e. which Item 10a codes must be specified for each filed PBN code. PBN CODE Required 10a Entry(s) R G D I O S A1 R G and/or I B1 R G D I O or S B2 R G B3 R D B4 R D O or S B5 R I B6 R C1 R G D I C2 R G C3 R D C4 R D I D1 R G D I D2 R G D3 R D D4 R D I L1 R G O1 R G D I O2 R G O3 R D O4 R D I S1 R G S2 R G T1 R G T2 R G 3/ FPL - Guidance Material to be incorporated in AIP

4 Flight Plan Item 18 STS/ Amendment 1 changes how special handling is filed within Item 18 STS/. Only 13 specific codes, denoting the reason for special handling, are able be used within this indicator from November They are; 1. ALTRV for a flight operated in accordance with and altitude reservation; 2. ATFMX for a flight approved for exemption from Air Traffic Flow; Management measures by the appropriate ATS authority; 3. FFR fire-fighting; 4. FLTCK flight check for calibration of navaids; 5. HAZMAT for a flight carrying hazardous material; 6. HEAD a flight with Head of State status; 7. HOSP for a medical flight declared by medical authorities; 8. HUM for a flight operating on a humanitarian mission; 9. MARSA for a flight for which a military entity assumes responsibility for separation of military aircraft 10. MEDEVAC for a life critical medical emergency evacuation 11. NONRVSM for a non RVSM-capable flight intending to operate in RVSM airspace; 12. SAR for a flight engaged in a search and rescue mission; and 13. STATE for a flight engaged in military, customs or police services. This means that common abbreviations will no longer be allowed within the STS indicator including SARTIME, GOVGEN, MED 1, MED 2, MIL SPEC REQ, VIP & NOCOM. The following changes will occur as a result: Current Special Handling code Amendment 1 FPL Special Handling code STS/MED 1 STS/MEDEVAC (see note 1) STS/MED 2 STS/HOSP (see note 2) STS/SARTIME 1 RMK/SARTIME 2 STS/GOVGEN or STS/PRIMIN or STS/VIP STS/HEAD RMK/ title of VIP RMK/GOVGEN or RMK/STATEPREM QLD or RMK/PRIMIN Note: When HEAD is filed in STS, VIP is not a valid entry in RMK the title of the VIP shall be specified. 1 Details of SARTIME with DTG and location 2 Details of SARTIME with DTG and location 4/ FPL - Guidance Material to be incorporated in AIP

5 Current Special Handling code STS/MIL SPEC REQ STS/NONRVSM RMK/MARSA with. RMK/NAVAID CALIBRATION STS/NOCOM.(and details) Amendment 1 FPL Special Handling code RMK/MIL SPEC REQ STS/NONRVSM RMK/MIL SPEC REQ as appropriate STS/MARSA RMK/ details of MARSA STS/FLTCK (details in RMK/) RMK/NOCOM.(and details) Note 1: MED 1 changes as follows: MED 1 - Changes to MEDEVAC in the 2012 FPL with the following definition: MEDEVAC - a life critical medical emergency evacuation e.g. an aircraft proceeding to pick up or carrying, a severely ill patient, or one for whom life support measures are being provided Note 2: MED 2 changes as follows: MED 2 Changes to HOSP in the 2012 FPL with the following definition: HOSP - a medical flight declared by medical authorities eg An aircraft transporting or proceeding to pick up medical personnel and/or equipment urgently required for the treatment of a severely ill patient, or returning urgently required medical personnel and/or equipment at the termination of a MEDEVAC flight. 5/ FPL - Guidance Material to be incorporated in AIP