1. INTRODUCTION
On 10th March 2011 Latvia will delegate responsibility for the provision of flight planning services within the Riga FIR to the Integrated Initial Flight Plan Processing System (IFPS).
Latvia will therefore become part of the IFPS Zone on 10 March 2011.
The following paragraphs describe the flight plan filing procedures that will come into effect on 10 March 2011 for flights which are intending to operate within the Riga FIR.
2. GENERAL
2.1 With effect from 10 March 2011 flight plan and associated messages for IFR/GAT flights intending to operate within the Riga FIR shall no longer be addressed to ATS Units within the Riga FIR. The only addresses which need to be entered for the portion of the flight within the Riga FIR are those of the two IFPS Units at Haren (Brussels) and Brétigny (Paris), as detailed below. Guidance is given below for the addressing of flight plans and associated messages in respect of flights which proceed beyond the boundaries of the IFPS Zone.
Note: The abbreviation GAT stands for “General Air Traffic” and is defined within Europe as “flights conducted in accordance with the regulations and procedures promulgated by State civil aviation authorities and operating under control or authority of the civil ATS organisation”.
2.2 With effect from 10 March 2011 Aircraft Operators may submit flight plans directly to IFPS for all IFR/GAT flights, or portions thereof, departing from within the Riga FIR. Flight plans for flights departing outside the Riga FIR and operating into or overflying the Riga FIR shall be submitted in accordance with the procedures published by the State within which the aerodrome of departure is located.
2.3 With effect from 10 March 2011 Aircraft Operators which make use of Repetitive Flight Plans (RPLs) are requested to ensure that RPL data for flights into, departing from or overflying the Riga FIR are submitted to the RPL Section of the CFMU.RPLs shall be submitted in the CFMU RPL format as an attachment to an email addressed to
There is a free application which enables the creation of RPL submissions in this format, this can be obtained via the link below
and complete the form.
Under the header REQUESTED TYPE OF APPLICATION, please tick RPL Application.
Under the header REQUESTED TYPE OF APPLICATION, please tick RPL Application.
Under the header REQUESTED TYPE OF APPLICATION, please tick RPL Application.
When an RPLO (RPL originator) sends their first RPL submission, the following information required:
- Full postal address and name of Air Company - also including the Aircraft Operators ICAO 3-letter code.
- Fax, telephone numbers (including country code).
- 24-hour contact.
- The name of the person responsible for RPLs.
Further information can be obtained by contacting the RPL Supervisor at:
3. FLIGHT PLAN MESSAGE ADDRESSING
3.1 Flights departing an aerodrome within the Riga FIR and remaining wholly within the IFPS Zone
3.1.1 Flight plan and associated messages need ONLY be addressed to the two IFPS Units as follows:
For AFTN - EUCHZMFP and EUCBZMFP
For SITA - BRUEP7X and PAREP7X
Note 1: Both IFPUs must be addressed for all flight plans and associated messages.
Note 2: Specific addresses for any VFR flight shall be added by the originator preferably by using the Re-addressing function described in paragraph 3.4 below.
3.2 Flights entering or overflying the Riga FIR
3.2.1 For that portion of the flight within the Riga FIR, only the two IFPUs need to be addressed as indicated in paragraph 3.1.1 above.
3.3 Flights departing an aerodrome within the Riga FIR and then exiting the IFPS Zone
3.3.1 For that portion of the flight within the Riga FIR, only the two IFPUs need to be addressed as indicated in paragraph 3.1.1 above.
3.3.2 For any portion of the flight outside the IFPS Zone, the flight plan message originator is responsible for having the flight plan and associated messages addressed to all appropriate ATSUs in accordance with ICAO procedures. The procedure below describes the preferred way of addressing as it ensures consistency between messages distributed within and outside the IFPS Zone. This procedure will enable the IFPS to distribute a validated flight plan or associated message to any additional AFTN address which is included in the address line as described below.
3.4 Re-addressing function
3.4.1 Any additional addresses to be included should be placed after the originator information line and immediately before the open bracket which indicates the beginning of the message. An example of an AFTN message with such additional addresses is given below:
ZCZC BOC548 250925 MB
FF EBBDZMFP LFPYZMFP
250920 EVRAZPZX
AD ADDRESS1 ADDRESS2 ADDRESS3 ADDRESS4 ADDRESS5 ADDRESS6 ADDRESS7 AD ADDRESS8
(FPL-BTI480-IS
-B735/M-SXYR/C
-EVRA1430
-……….
-………
The following rules apply:
- The extra address lines must begin with the keyword AD to distinguish them from other comment lines which may be present.
- The extra address lines must be consecutive (no other comment lines between them), and they must be immediately before the line containing the open bracket.
- There must be no more than 7 additional addresses per line, and each must be of 8 characters.
4. IFPS VALIDATION SYSTEM (IFPUV)
4.1 Flight plan originators wishing to test FPLs with the IFPUV, prior to their submission to the operational IFPS, may submit them via either AFTN or SITA to one of the following addresses:
AFTN : EUCHZMFV
SITA : BRUEY7X
4.2 Test flight plans may be submitted with a DATE OF FLIGHT (DOF) up to 120 hours (5 days) in advance by means of DOF/ in Item 18, in the format DOF/yymmdd where “yy” is the year indicator, “mm” is the month and “dd” is the day. The system will respond to flight plan submission by means of a Reply Message in the form of either an ACKNOWLEDGEMENT (ACK) which indicates that if the FPL is submitted to IFPS, the FPL would pass automatic processing or a REJECT (REJ) which indicates a failure. In the case of REJ the Reply Message will contain a system generated indication of the reason for failure. The IFPUV therefore does not generate MANUAL (MAN) messages.
4.3 Every Reply Message from the IFPUV contains the phrase “This message has been sent by a test system and must not be used operationally”. This message is added to ensure that there is no confusion between submissions to the test system and those to the operational IFPS.
4.4 The IFPUV is not connected to the operational IFPS and test messages are neither distributed nor stored in the system. Since FPLs are not stored in the IFPUV, flight plan associated messages (i.e. CHG, DLA, CNL, RQP, etc.) are rejected by the IFPUV with the message: “ERROR: no existing filed flight plan matches this message”.
