IFPS

IFPS ZONE

THE IFPS REQUIREMENTS

All messages submitted to the IFPS for processing shall be submitted to both IFPS units, regardless of which unit shall be responsible for processing that message

All flight plans and associated messages for IFR/GAT flights or parts thereof operating within the IFPZ should, as far as possible, are submitted to the IFPS for processing at least 3 hours prior to the EOBT of that flight.

For those IFR/GAT flights departing within the IFPZ and proceeding outside, and for those IFR/GAT flights that depart outside the IFPZ and proceed to enter, it shall remain the responsibility of the message originator to ensure that the relevant ATCUs outside the IFPZ are addressed

THE IFPS SHALL

take action to ensure that the flight plan is acceptable to air traffic services

indicate acceptance of the flight plan (or change) to the originator

ensure distribution of accepted flight plans and modifications thereto to all relevant Air Traffic Services Units within its area of responsibility

ensure re-addressing of accepted messages to any additional AFTN addresses as requested by the message originator

process supplementary messages including request flight plan messages and request supplementary flight plan messages

FLIGHT PLANS SUBMISSION

Flight plans and associated update messages for all Instrument Flight Rules/General Air Traffic (IFR/GAT) flights, including the IFR portions of mixed Instrument Flight Rules/Visual Flight Rules (IFR/VFR) flights, entering, overflying or departing the IFPZ shall be addressed only to the two IFPS addresses for that portion of the flight within the IFPZ

RULES FOR FPL SUBMISSION

Basic rules for the submission of flight plan messages and associated updates have been defined in ICAO Annex 2 and Documents 4444 and 7030

These requirements are applicable to flight plans and associated messages handled by the IFPS

FLIGHT DATA MESSAGE FLOWS

AERODROME OF

DEPARTURE WITHIN IFPZ

Flight plans and associated messages for IFR/GAT flights departing from an aerodrome within the IFPZ shall, if authorised by the

State concerned,

be submitted directly to the IFPS and not via the Air Traffic Services Reporting Office (ARO) at the departure aerodrome

AERODROME OF

DEPARTURE WITHIN IFPZ

AOs who are unable (e.g. no AFTN or SITA terminal) to submit their flight plan or associated messages directly to the IFPS shall submit the flight plan messages to the ARO of the departure aerodrome

It shall be the responsibility of the ARO to ensure submission to the IFPS for processing of any flight plans or associated messages relating to IFR/GAT flights or parts thereof intending to operate within the IFPZ submitted to that ARO by the relevant AO or their representative. AOs shall ensure that the flight plan or associated message is always submitted either directly to the IFPS or to the ARO at the departure aerodrome, but not both

AERODROME OF DEPARTURE

OUTSIDE IFPZ

 Flight plans and associated messages for IFR/GAT flights entering the IFPZ from a departure aerodrome outside the IFPZ shall be submitted in accordance with the procedures applicable within the State concerned

AERODROME OF DEPARTURE

OUTSIDE IFPZ

It shall be the responsibility of the ARO to ensure submission to the IFPS for processing of any flight plans or associated messages relating to IFR/GAT flights or parts thereof intending to operate within the

IFPZ submitted to that ARO by the relevant AO or their representative