1 / 30

FLIGHT PLAN 2012 PREPARED BY:DYLAN KEMLO

FLIGHT PLAN 2012 PREPARED BY:DYLAN KEMLO. TRANSITION – 15 NOVEMBER 2012 Note – This presentation does not incorporate the additional changes related to PBN and GNSS. For more detailed information on these changes please email your query to: dylan.kemlo@43airschool.com. FLIGHT PLAN 2012.

neva
Download Presentation

FLIGHT PLAN 2012 PREPARED BY:DYLAN KEMLO

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. FLIGHT PLAN 2012PREPARED BY:DYLAN KEMLO TRANSITION – 15 NOVEMBER 2012 Note – This presentation does not incorporate the additional changes related to PBN and GNSS. For more detailed information on these changes please email your query to: dylan.kemlo@43airschool.com

  2. FLIGHT PLAN 2012 REASONS FOR THIS TRANSITION • To update the ICAO model flight plan form in order to meet the needs of aircraft with advanced capabilities incorporating automated air traffic management systems (ATM). • To identify the compatibility with existing systems, human factors, training, costs and transition aspects. • To ensure that one standard of Flight planning is identified and managed by all users affiliated to ICAO. • To ultimately avoid ambiguity and misunderstanding with the decoding of flightplan entries.

  3. FLIGHT PLAN 2012 FLIGHT PLAN CHANGES IN NUMERIC ORDER • ITEM 7– AIRCRAFT REGISTRATION • ITEM 8– FLIGHT RULES • ITEM 10a – RADIO/COMMUNICATION/NAVIGATION AND APPROACH AID EQUIPMENT CAPABILITIES • ITEM 10b – SURVEILLANCE EQUIPMENT AND CAPABILITIES • ITEM 13 – DEPARTURE AERODROME • ITEM 15 – CRUISING SPEED/FLIGHT LEVEL AND ROUTING • ITEM 16 – DESTINATION AERODROME • ITEM 18 – OTHER INFORMATION

  4. FLIGHT PLAN 2012 FILING OF A FLIGHT PLAN AIC 42.1 NOTE:This will be amended to incorporate the relevant changes to be implemented as of 15th November 2012 and promulgated in accordance with the AIRAC cycle. CURRENT NOTIFICATION OF FPL TRANSITION AIC18.67 AIC 42.4

  5. FLIGHT PLAN 2012 ITEM 7 (CALLSIGN) NEW FORMAT: (No Hyphens) i.e. ZS-ABC will now be written as ZSABC

  6. FLIGHT PLAN 2012 ITEM 7 / CONTINUED When the callsign has more than 7 indicators in it then the portion of the callsign will be entered in Item 7 and the full callsign will be entered as a RMK/`Remark` entry in Item 18.

  7. FLIGHT PLAN 2012 ITEM 8 – FLIGHT RULES IF THE FLIGHT RULE IS Y THEN ENTER IN ITEM 15 AS FOLLOWS: N0230F090 DCT ITBAN DCT EVALA/N0400F095 VFR DCT IF THE FLIGHT RULE IS Z THEN ENTER IN ITEM 15 AS FOLLOWS: N0230F095 DCT ITBAN DCT EVALA/N0400F290 IFR DCT NOTE:There are no changes to the existing format if you enter I or V in ITEM 8.

  8. FLIGHT PLAN 2012 ITEM 8 – TYPE OF FLIGHT WHEN INDICATOR ‘X’ IS USED IN ITEM 8 THEN INDICATE THE STATUS (STS) IN ITEM 18 USING ONE OF THE SELECTIONS AVAILABLE AS FOLLOWS: MEDEVAC – for a life critical medical emergency evacuation; HOSP – for a medical flight declared by medical authorities; FFR – fire fighting; SAR – for a flight engaged in a search and rescue mission.

  9. FLIGHT PLAN 2012 ITEM 10a – EQUIPMENT SUMMARISED If ‘G’ is present under this field then the types of GNSS augmentation will be entered in Item 18.If ‘R’ is present under this field then `PBN` is entered in Item 18 along with the associated list of ICAO indicators.If ‘Z’ is present under this field then at least one of COM/NAV or DAT are entered in Item 18. COM-Communications equipment not accommodated in Item 10a and 10b NAV-Navigation equipment not accommodated in Item 10a. DAT-Data link equipment not accommodated in Item 10a. NOTE: A GPS alone does not amount to GNSS, and if the aircraft is equipped with only a GPS then this will still be depicted as ‘Z’ in Item 10a and ‘NAV/GPS’ in Item 18.

  10. FLIGHT PLAN 2012 ITEM 10a – EQUIPMENT SUMMARISED If ‘S’ is present under this field then it includes the following: VHF = (V) / VOR = (O) / ILS = (L) BUTNOW EXCLUDES ADF (F) IF YOU ARE ALSO CARRYING ADF IN ADDITION TO THE EQUIPMENT MENTIONED ABOVE THENTHIS WILL NOW BE INDICATED ON THE FLIGHT PLAN AS FOLLOWS: SF

  11. FLIGHT PLAN 2012 ITEM 10b – EQUIPMENT A/C/E/H/L/S TRANSPONDER`S – THEY MAY BE USED IN A COMBINATION ENTRY UNDER THIS ITEM ON THE FLIGHT PLAN. I/P/X – THESE ARE MUTUALLY EXCLUSIVE TRANSPONDERS AND ONLY ONE OF THEM MAY BE PRESENT ON THE FLIGHT PLAN. NOTE: ITEM ‘Z’ IS NO LONGER PLACED IN ITEM 10b.

  12. FLIGHT PLAN 2012 ITEM 13 – DEPARTURE AERODROME IF YOU ENTER ZZZZIN ITEM 13 THEN YOU WILL ENTER THE FOLLOWING INFORMATION IN ITEM 18 18. Other Information NAME DEP/AMATHUBA2324S02526E OR BEARING AND DISTANCE FROM NAVAID DEP/GRV280015 OR BEARING AND DISTANCE FROM WAYPOINT DEP/OVALA310022 NOTE: The name that is written down must not have any spaces between the letters and may not contain more than 50 characters.

  13. FLIGHT PLAN 2012 ITEM 15 - ROUTE GENERAL: IF A PILOT WISHES TO ROUTE LOW LEVEL (Below 1500 feet AGL) THEN THEY WILL ENTER IN ITEM 15 & 18 AS FOLLOWS: ITEM 15: ITEM 18: ITEM18 RMK/VFR500FTAGL

  14. FLIGHT PLAN 2012 ITEM 15 - ROUTE GENERAL: IF A PILOT WISHES TO ROUTE AT AN ALTITUDE THEN THEY WILL ENTER THIS IN ITEM 15 AS FOLLOWS: ITEM 15:2500 feet will be written as;

  15. FLIGHT PLAN 2012 NOTE 3. If you initially start out as a VFR flight which is specified in ITEM 18 as a VFR flight below 1500 feet AGL and then continue to a IFR Flight Level en-route, later changing back to a VFR flight below 1500 feet then you will make this entry on the Flight Plan as follows: N0120A010 DCT POINT/N0120F060 DCT POINT/N0120VFR DCT In Item 18. you would then enter under RMK RMK/VFR1000FTAGL

  16. FLIGHT PLAN 2012 ITEM 15 - ROUTE GENERAL: THE ROUTE ELEMENTS CAN CONTAIN A COMBINATION OF ANY OF THE FOLLOWING: • LATITUDE / LONGITUDE e.g. – S2715E02314 2. A NAVAID, WAYPOINT, or a BEARING and DISTANCE from it e.g. WB135015 (bearing 135 deg. At 15nm from Navaid `WB`) OVALA270015 (bearing 270 deg. At 15nm from waypoint `OVALA`)

  17. FLIGHT PLAN 2012 ITEM 15 – ROUTE When changing Flight Levels on a particular flight plan route NOTE how this is entered on the flightplan to include the forward slash between the relevant point and the indicated change in Level i.e. DCT FPL2012/N0140F0090 DCT

  18. FLIGHT PLAN 2012 ITEM 15 – ROUTE NOTE: • You may not enter a bearing and a distance from an Aerodrome locator. DCT FABW DCT FAKM28515 DCT 2. You may however enter a bearing and distance from a Latitude/Longitude reference. DCT FAOH DCT 2635S02507E285050 Broken up as LAT-LONG-BRG-DISTANCE NOTE: 1. Latitude and Longitude only needs to include Degrees and Minutes for all related entries. 2. You do not enter the name of the non-registered point or airfield along with the co-ordinates; i.e. DCT 2833S02145E DCT FALY DCT

  19. FLIGHT PLAN 2012 ITEM 15 – ROUTE NOTE: • You may no longer enter the term ABEAM or a reference SYMBOL to it such as: DCT SUNRISE RIVER 2. A Pilot may not enter only `DCT` on a FPL. In other words, at least one Geographical reference/Navaid or Waypoint entry must follow the DCT entry in this Item. 3. A Pilot must enter the next reporting point for that flight at least every 30 minutes or inside of every 200 Nm of that planned flight.

  20. FLIGHT PLAN 2012 ITEM 16 – DESTINATION IF YOU ENTER ZZZZIN ITEM 16 THEN YOU WILL ENTER THE FOLLOWING INFORMATION IN ITEM 18 18. Other Information NAME DEST/ORION2415S02628E OR BEARING AND DISTANCE FROM NAVAID DEST/HGV280015 OR BEARING AND DISTANCE FROM WAYPOINT DEST/OVALA310022 NOTE: The name that is written down must not have any spaces between the letters and may not contain more than 50 characters.

  21. FLIGHT PLAN 2012 ITEM 18 – OTHER INFORMATION CHANGES: New Indicators as follows: STS – Status PBN – Performance Based Navigation GNSS – Global navigation Satellite Surveillance TALT – Take Off Alternate (1st. Alternate Aerodrome) RALT – En-route Alternate (2nd. Alternate Aerodrome) REQ – Request

  22. FLIGHT PLAN 2012 ITEM 18 – OTHER INFORMATION (CONTINUED) 1st ALTERNATE = TALT/NAMELAT.LONG. If ZZZZ is entered 2nd ALTERNATE = RALT/NAMELAT.LONG. If ZZZZ is entered TOUCH AND GO REQUEST = 1XTGL VOR LETDOWN REQUEST = 1XPVD ILS LETDOWN REQUEST = 1XPVDI NDB LETDOWN REQUEST = 1XNDB

  23. FLIGHT PLAN 2012 ITEM 18 – OTHER INFORMATION (CONTINUED) Missed Approach – entered on the flightplan as MISSEDAPCH (followed by the relevant airfield designator where the missed approach will be taking place) Initial request for a VOR ILS Letdown followed by a Missed Approach for a VOR letdown will be entered as follows: RMK/PVDIMAPVDFAEL

  24. FLIGHT PLAN 2012 ITEM 18 – OTHER INFORMATION ALL HEADERS ONLY TO BE USED ONCE e.g. RMK/SARNML STUDENTSOLONAVEX REQ1XTGL NOTEthe spaces between each related entry under RMK when referring to a new sub-section for that particular Section entry.

  25. FLIGHT PLAN 2012 ITEM 18 – OTHER INFORMATION (CONTINUED) EETSignificant points or FIR boundary designators and accumulated estimated elapsed times from take-off to such points or FIR boundaries, when so prescribed on the basis of regional air navigation agreements, or by the appropriate ATS authority. Example: EET/FAJS0130 NOTE: You may only enter the EET as the approximate duration calculated for that portion of the flight and not use the time that is indicated on your watch converted to ZULU time.

  26. FLIGHT PLAN 2012 ITEM 18 – OTHER INFORMATION (CONTINUED) IMPORTANT NOTE FOR SAR SAR requirement must be the very first remark in this Item, and it, (like all the other entries listed under this field) may not have any spaces between its entry. The reason for this is that the Flight Data Processing system looks at the first string under RMK/ to find the SAR requirements for the flight and then highlights it to the ATC. If SAR is not the first remark, the flightplan may be rejected. a) SAR FACT ETA + 1HR will now be entered as RMK/SARFACTETA1HR b) SAR NORMAL will now be entered as RMK/SARNML c) SAR NIL will be entered as RMK/SARNIL

  27. FLIGHT PLAN 2012 ITEM 18 – OTHER INFORMATION (CONTINUED) OPR Indicates who the Operator / owner of the registered aircraft is. DOF Indicates the actual Date Of Flight of that particular aircraft. Note that Advance Flight Plan filing will now be accepted up to 5 days (120 hours) in advance. Entered as YEAR/MONTH/DAY e.g. – 2012/10/02.This entry must always be entered on any filed flight plan. RMK Indicates additional Remarks under this field. Note that the user may enter this entry only once in this field (with additional sub-sections to this item if required), and this indicator must be entered at the beginning of Item 18.

  28. FLIGHT PLAN 2012 ITEM 18 – OTHER INFORMATION (CONTINUED) COASTWISE ROUTING – Should you wish to route coastwise you may no longer enter this in ITEM 15 and must instead follow the procedure as listed below: ITEM 15 – Enter the co-ordinates OR a bearing and distance from any significant point for the coastwise routing ITEM 18 – Under RMK enter the following RTECOASTWISE

  29. FLIGHT PLAN 2012 ITEM 18 – OTHER INFORMATION (CONTINUED) REQUESTING IFR TRAINING ITEM 18 – Under RMK enter the following IFTRNG OR Enter under RMK as follows: VDIFAELPVDIFAPA

  30. FLIGHT PLAN 2012 NOTE • All coastal stations in South Africa will require pilots who fly between coastal stations to file separate flightplans for all cross country flights that include a touch and go at another station en-route to final destination. 2. A pilot can include their personal cell number with that of the school details under Operator as follows: OPR/FTC 0448769055 0832352598

More Related