1.10.2.1.1.1  Flight plan personally submitted at an ARO

The flight plan form will be confirmed to the submitter after the reception of an “Acknowledge Message - ACK” from IFPS. A copy of the “ACK” will be handed over to the submitter together with the flight plan form. If any changes have been made in the flight plan by IFPS, the “ACK” message comprises the copy of the whole flight plan including the changes made by IFPS (the “-MSGTXT” field). This is the flight plan message that will be distributed to the ATS centres en-route.

1.10.2.1.1.2  The flight plan submitted by means of telephone

The submitter shall check the status acceptance or rejection of the flight plan before the departure. He/She shall check the reception of a time slot as well.

1.10.2.1.1.3  Flight plan submission by means of AFTN or SITA network

Flight plan can be submitted by means of AFTN to the following addresses:

SITA address - to be defined.

1. If a flight plan is submitted by means of AFTN or SITA the operator shall file the flight plan including the field 19. Syntax in accordance with ICAO Doc 4444.

2. If a flight plan is submitted by means of AFTN or SITA the following “IFPS-Operational Reply Messages (ACK, MAN, REJ)” will be re-distributed to the address of the flight plan originator.

3. If this re-distribution is requested to an address different from the originator´s address or, if the distribution is requested to an additional address, the operator will announce the details to:

   Post:

   Air Navigation Services of the Czech RepublicTORG_AUTH;TXT_NAME;1742
   Air Navigation Services Planning and Development Division
   Navigační 787
   252 61 Jeneč

   Telephone:  +420 727 373 262

   Telefax:  +420 727 372 011

1.10.2.1.1.4  The submission of FPL by means of e-mail

A flight plan can be submitted by means of e-mail at the following address:

After it is sent, it is needed to verify by phone that the FPL is filled correctly. Only after verification will the FPL be submitted.

An acknowledge Message - ACK or Rejection Message - REJ will be sent to the email address from which the submitted IFR or combined flight plan was sent.

1.10.2.1.1.5  The submission of FPL via web application IBS

The IBS (Integrated Flight Briefing System) is a web application which provides users services for filing FPL and pre-flight briefing:

1.10.2.1.3.1  Flight fully inside the IFPS-Zone

A flight plan for a flight fully inside the IFPS Zone as defined by the Network Operations Handbook shall only be addressed to both “IFPS Units - IFPU”.

1.10.2.1.3.2  The flights outside the space of interest of IFPS

1. The flights from the inside of the IFPS-ZONE to the outside of the IFPS ZONE

   The flight plan will be addressed to both of the IFPUs. The addresses of the ATC Units outside the IFPS-Zone involved in the flight will be adduced to the additional line beneath the originator’s data, before the opening bracket of the message itself. The IFPS will distribute the message to these addresses. Each line of address shall be introduced by an “AD” abbreviation and it shall contain not more than 7 addresses.

2. Combined VFR/IFR, IFR/VFR, GAT/OAT, OAT/GAT flights

   The addressing rules adduced above apply to the combined flights as well. The addresses of the units involved in VFR or OAT portion of the flight will be adduced to the additional line beneath the originator’s data before the opening bracket of the message itself. These addresses shall be inserted in accordance with the table adduced in frame of item ENR 1.11.2.

1.10.2.1.3.3  Addressing of the next leg flight plans

1. All legs inside the IFPS - Zone

   The flight plans for all legs of the flight will be addressed directly to both IFPUs. No flight plan will be sent to an ARO of an intermediate airport for further distribution.

2. Next leg of a flight leads from the inside of the IFPS - Zone to the outside of the IFPS zone.

   Both flight plans shall be filed directly with both IFPUs. The addresses of the ATC units outside the IFPS involved in the next stage flight plan will be adduced on the additional line beneath the originator’s data before the opening bracket of the message itself. The IFPS will distribute the flight plan to these addresses.

3. The flight plan for the next leg of a flight departing outside the IFPS zone shall be sent to the ARO of the intermediate airport for further distribution notwithstanding the fact that the flight is returning to the IFPS - Zone or not.

1.10.2.1.3.4  IFPS Validation System

Before the flight plan is sent to the addresses adduced in ENR 1.10 para 2.1.3.1, its correctness can be checked by sending it to the following addresses:

The ACK message received indicates that the flight plan will be accepted without manual intervention after it is sent to the addresses adduced in ENR 1.10 para 2.1.3.1. The REJ message received indicates mistakes in the FPL message. After the ACK reception the flight plan is not considered as accepted. Subsequently it must be sent to the addresses adduced in ENR 1.10 para 2.1.3.1

1. The first point in the route description shall be the last point of departure route which is simultaneously the first published en-route point.

2. If no departure routes are published for the airport in question the “DCT” shall be used before the first point in route description. Syntax N0480F350 DCT - point - route. The maximum distance between the departure airport and the filed point shall be 50 NM.

3. The last point in the route description shall be the last published en-route point which is simultaneously the first point of the arrival route.

4. If no arrival routes are published for the airport in question the last point in route description will be the last published en-route point followed by “DCT”. Syntax: route - point - DCT. The maximum distance between the airport of arrival and the filed point shall be 50 NM or shorter.

5. The system can process the route description given in geographical coordinates in compliance with ICAO rules.

1. Objective: To enable time delays associated with certain special en-route activities such as training flights, air to air refuelling, photographic missions etc. to be entered in the Route Field of a FPL.

2. Description: To indicate the time spent on the route of the flight in the area (STAY area) where special activities are planned a STAY indicator shall be inserted in Field 15 of the FPL between the point of entry of the STAY area and the point of exit from the STAY area.

   Example: ... BODAL STAY1/0100 TIBLA ...

3. The entry point of the STAY area and the exit point from the STAY area can be identical.

   Example: ... BODAL STAY1/0030 BODAL ...

4. To allow several STAY indicators to be inserted in the route of a flight a sequence number from 1 to 9 shall be attached to a STAY indicator.

   Example: ... BODAL STAY1/0030 BODAL A152 TIBLA
   STAY2/0030 TIBLA A152 ...

5. The planned time spent in the STAY area shall be indicated in hours and minutes. It is possible to indicate speed/flight level changes, flight rules changes (IFR/VFR) and flight type changes (GAT/OAT) on the point of entry in the STAY area and/or on the point of exit from the STAY area.

   Example:
   ... BODAL VFR STAY1/0030 BODAL/N0420F330 IFR ...

6. To indicate the reason for STAY, a free text STAYINFO indicator shall be inserted in Field 18 of the FPL.

   Example:

   ... Field 15: ... BODAL STAY1/0030 BODAL ...

   ... Field 18: ... STAYINFO1/CALIBRATION OF BNO VOR

   The sequence number attached to the STAYINFO indicator shall be identical with the number attached to the corresponding STAY indicator.

7. A STAY indicator can only be used for en-route special activities of otherwise standard flights.

8. A STAY indicator can only be used for flights that are completely within the IFPS Zone and if so published in AIPs of the states concerned.

1. State flights not equipped for 8.33 kHz channel spacing and data to be filed in filed flight plan:

   1. State flights not equipped for 8.33 kHz channel spacing and operating in 8.33 airspace and equipped for communication in UHF band shall file “U” and “Z” in frame of the field 10a.

   2. The same flights shall not file “Y” (indicating equipment for 8.33 kHz channel spacing) in frame of the field 10.

   3. The field 18, item “COM/…” shall subsequently comprise “EXM833”.

   Note: With regard to the fact that the field 10a contains common data on communication and navigation equipment, it is not possible to use letter “S” and the data on navigation shall be adduced individually in compliance with ICAO Doc4444 for the flights mentioned above.

2. For the flights not equipped for PBN - RNAV 5 or better in compliance with ICAO Doc 7030 the following shall be applied:

   1. The field 10 shall not comprise the letter “R” indicating PBN-RNP ability.

   2. The field 10 shall comprise the letter “Z” indicating other equipment.

   3. The field 10 shall comprise individual navigational equipment data in compliance with ICAO Doc 4444.

   4. The field 18, item “NAV/…” shall comprise “RNAVX”.

   Note: For the case of forced climbing above the lower limit of the RNAV airspace, where this equipment is required the rules mentioned above apply even for the flights planned below the lower limit of this RNAV airspace.

3. Operators conducting flights wholly or partly in the Single European Sky airspace where ATN B1 CPDLC is required, but for which Commission Regulation (EC) 29/2009 is not applicable in accordance with Article 3(3), or which aircraft types/models are exempted by Commission Implementing Decision 2019/2012, should include the letter “Z” in item 10 and the indicator “DAT/CPDLCX” in item 18 of each flight plan.

   Note: Operators which voluntarily equip their aircraft in compliance with Commission Regulation (EC) 29/2009 and intend to use the CPDLC capability do not need indicate in their flight plan the status as exempted.

"0" | "STS/" | "PBN/"| “EUR/” | "NAV/" | "COM/" | "DAT/" | "SUR/" | "DEP/" | "DEST/" | "DOF/" | "REG/" | "EET/" | "SEL/" | "TYP/" | "CODE/" | "RVR/" | "DLE/" |"OPR/" | "ORGN/" | "PER/" | "ALTN/" | "RALT/" | "TALT/" | "RIF/" | "RMK/" | "STAYINFOn/" | "RFP/"

The rules:

1. If no data are to be filed, file „0“ (zero).

The rules to file the data in frame of other items of the field 18 are in compliance with ICAO Doc 4444 with following information specification:

1. The item “EUR/…” is not mentioned in ICAO Doc 4444 but used in EUR Region. The FPL submitter will file “EUR/ PROTECTED” in case of safety sensitive flights.

2. The item “NAV/…” shall comprise “RNAVX” if the letter “R” is not filed in frame of the field 10 (PBN equipment for RNP5 or better is missing).

3. The item “COM/…” shall comprise “EXM833” in case of the State flights not equipped for 8.33 kHz channel spacing and “U” and “Z” is filed in frame of the field 10.

4. The flight plans filed in the Czech Republic shall always comprise the item “DOF/…”. In this case “0” (zero) will not be filed.

5. The item “RVR/…” is not mentioned in ICAO Doc.4444 but it is used in EUR Region. The RVR minima of the crew and aircraft in meters are filed.

   Example: “RVR/250”

6. The item “STAYINFOn/...” is not mentioned in ICAO Doc.4444 but it is used in EUR Region. File the data in compliance with ENR 1.10 para 2.1.4.6; bullet 6. above. The sequence number of the indicator and the reason in open speech shall be filed.

   Example:

   The field 15: “... BODAL STAY1/0030 BODAL ...“

   The field 18: “….STAYINFO1/CALIBRATION OF BNO VOR….“

7. The item “RMK/…” is the only item in frame of which the open speech may be used. If the FPL submitter accepts route changes initiated by IFPS the abbreviation “IFPSRA” shall be used instead of open speech remark.

8. The item “RFP/…” plus sequence number of the replacement flight plan.

The rules: If a change of the route occurs between the unchanged departure airport and unchanged destination during the period from EOBT-4 hours until EOBT- 30 minutes and FPL exist, it is possible to change the route by means of a CHG message or, the existing flight plan may be cancelled and a new one may be filed.

Adduce the “RVR = the crew’s minimum in meters” element as the second last in the field 18 before “DOF”.

Objective: If reduced visibility condition occurred at the destination airport, the “FLS” message would only be sent to the flights with the higher minima than the visibility expected at the arrival time, and to the flights not having the RVR element adduced in the flight plan.

Syntax: RVR/300 = crew minimum in meters.

1. FBZ are established for IFR flight planning purposes only. Flight plans can be filed up to the boundary of the FBZ when active.

2. The route described in field 15, shall consider the nominal track between two points on the great circle.

3. Reserved/restricted airspace and the FBZ are notified when active by AUP.

1.10.2.2.1.1  The format of the “ACK” message after the modification in the IFPS

1.10.2.2.1.2  The format of the “ACK” message after the acceptance without modification.

1. TITLE ACK

2. MSGTYP FPL

3. ORIGINTD 9706090645

4. BEGIN ADDR

   1. FAC LKPRZPZX LKPRCSAO

5. END ADDR

6. IFPLID AA00245327

7. EXTADDR -NUM001

8. BEGIN MSGSUM

   1. ARCID CSA001

   2. ADEP LKPR

   3. ADES EDDF

   4. EOBD 0810

   5. EOBT 970609

   6. ORGN LKPRZPZX

9. END MSGSUM

1.10.2.2.1.3  Meaning of the message

Confirmation of successful processing and announcement of the format after the processing in the IFPS.

A flight plan in ICAO format after the processing in IFPS is sent in the field “MSGTXT” of an ACK message. One of the modification made by IFPS can be the mistake indicator inclusion in the field 18.

1.10.2.2.1.4  Distribution

1. If the flight plan has been submitted manually to an ARO, a copy of the “ACK” message will be handed over to the submitter together with the confirmed flight plan form.

2. If the flight plan has been submitted by means of telephone, an “ACK” message reception will be announced to the submitter together with possible changes when checking the flight plan status in compliance with ENR 1.10 para 2.1.1.2

3. If the flight plan has been submitted by means of AFTN or SITA network, the message will be re-distributed to the address of the flight plan originator or to the addresses in compliance with ENR 1.10 para 2.1.1.3 item 3.

1.10.2.2.1.5  The submitter’s further actions

The submitter shall consider the field “MSGTXT” contents or changes to the original flight plan announced by telephone to be the official form of his/her flight plan.

1.10.2.2.2.1  Format

1.10.2.2.2.2  Meaning

Hang on, your message is or will be corrected manually.

1.10.2.2.2.3  Distribution

1. If the “MAN” message is related to a flight plan received by means of the AFTN or SITA network, the message will be re-distributed to the address of the flight plan originator or to the addresses in compliance with ENR 1.10 para 2.1.1.3 item 3.

2. If any other way of flight plan submission has been used, the message will not be re-distributed.

1.10.2.2.2.4  The submitter’s further actions

The submitter will stand by for further “ACK” or “REJ” message reception.

1.10.2.2.3.1  Format

1.10.2.2.3.2  Meaning

“Your message has been rejected because of the mistakes that IFPS has no right to or is not able to remove”.

1.10.2.2.3.3  Distribution

1. If the “REJ” message is related to a flight plan that has been submitted by means of the AFTN or SITA network, the message will be re-distributed to the address of the flight plan originator or to the addresses in compliance with ENR 1.10 para 2.1.1.3 item 3.

2. If the “REJ” message is related to a flight plan that has been submitted manually, the flight plan form will not be confirmed to the submitter and a “REJ” message reception will be announced to him/her.

3. If the “REJ” message is related to the flight plan that has been submitted by means of the telephone, the “REJ” message reception will be announced to him/her when checking the flight plan status in compliance with ENR 1.10 para 2.1.1.2

1.10.2.2.3.4  The submitter’s further action

The submitter shall file a new flight plan.

Example: EOBT in accordance with the flight plan - 0900, CTOT in accordance with SAM - 1000. If the flight is able to start taxiing at 0915, the DLA message shall be sent.