![\"\"](\"https:\/\/greekhelicopters.gr\/helos\/wp-content\/uploads\/2019\/07\/supinfo.png\")
<\/p>\n<\/p>\n
When departing or arriving from heliports or landing sites in the vicinity of airports especially within their CTR or ATZ, pilots filing flight plans using EuroFPL or other similar applications are advised to include in the remarks (RMK\/) the supplementary information of their flight.<\/p>\n
For a helicopter this can be added with the following format in ITEM 18 of ICAO flight plan form:<\/p>\n
(Note that the \/ is replaced with a dot . or else the system will reject it).<\/em><\/p>\n This is because the supplementary information is not passed to the ATC of the airport if it is NOT set as origin or destination.<\/p>\n In Greece, although we address the correct AFTN messages for the flight,\u00a0<\/span>the ATC controlling the airspace of the landing site, usually wants to send again AFTN messages but misses supplementary information. Although this is not a common practice for Europe in order to overcome unnecessary communications we can use the above addition in remarks.<\/p>\n <\/p>\n In some occasions we were told by ATC to add as departure the airport although the takeoff was outside the airport but within the CTR in order for them to receive the supplementary information. This is violating regulations and should not be accepted by the crews.<\/strong><\/p>\n When not departing\/arriving from airdromes with ICAO code, you should always use ZZZZ<\/strong> with the appropriate DEP\/<\/strong> or DEST\/<\/strong> in\u00a0ITEM 18. OTHER INFORMATION<\/strong> like: DEST\/KITHNOS 3726N02426E<\/strong> with any remarks under RMK\/<\/strong> required as mentioned above.<\/p>\n <\/p>\n More information for correctly filing the ICAO flight plan: RMK\/HELICOPTER SUPPLEMENTARY E.0230 P.002 R.E J.L A.RED C.PILOTNAME +306932XXXXXX<\/code><\/p>\nTechnically speaking, ICAO spec prohibits the inclusion of Item 19 Supplementary Information in FPL messages (as seen at the ICAO flight plan form on ITEM 19 SUPPLEMENTARY INFORMATION – NOT TO BE TRANSMITTED IN FPL MESSAGES<\/strong>). However, there are authorities like Greece, that welcome the inclusion of Item 19 Supplementary Information so they don’t have to make separate RQS queries<\/strong>, and have flight management systems that accept long-form FPLs of that nature.<\/div>\nIt is strongly advised to use\u00a0the inclusion of 7 or 11-character coordinates for DEP\/ and DEST\/ entries<\/strong><\/div>\n