1. FPL 2012 FPL Vendor Conference Mona Annaddaf Scotland, 7-8/12/2011
Presented by:
Mona Annaddaf
7/12/2011

2. Presentation Outline Background Issues regarding use of FPL data
Regional Variation
State Variation
7/12/2011

3. Background Sudan 7/12/2011 Ready for FPL Signed contract with a vendor
Evaluation of current systems
No Progress 3
7/12/2011

4. Issues regarding use of FPL data
The MID states will adopt the FPL guidance material developed by APAC Region.
2. The MID transition period from 1 January 2012 until 14 November 2012, comprising;
- Before 31 March ANSPs software delivery and internal testing.
- 1 April to 30 June 2012 – ANSPs external testing and
- 1 July to 14 November 2012 – airspace users testing.
7/12/2011

5. Issues regarding use of FPL data
When a converter can be a viable alternative
7/12/2011

6. Issues regarding use of FPL data
For a state does not wish to upgrade legacy system that approaching end of its lifetime.
For end system is not capable of handling both formats in parallel during the transition period.
When a state does not need an end system (ATM) supporting new capabilities in new FPL like (ADS, PBN, Data link,… etc) as those technologies are not yet implemented there, the national CNS/ATM plan for each state can determine its current and future need.
To support Interoperability with other states that will not comply with the transition date.
The cost should not be the criteria
7/12/2011

7. Issues regarding use of FPL data
All Converter vendors offer a manual Intervention position:
-> The operator should not append/ correct any data inside the text of FPL. (AFTN principle)
-> The manual Intervention position should be used to request repetition or to contact the originator in any way.
7/12/2011

8. Issues regarding use of FPL data
Handling erroneous or unrecognized FPL format:
CFMU use “REJ” message to inform the originator about the rejected flight plan, same procedure could be used to request resubmitting an erroneous or unrecognized FPL message when no direct contact is possible with that message originator.
7/12/2011

9. Issues regarding use of FPL data
AFTN Limitations
1- Line Length 69 characters
AMHS Migration ( unlimited line length)
At MTCU, any line more then 69 will be folded.
2- Max message size 2100 characters
AMHS Migration (Unlimited message size)
7/12/2011

10. Regional Variation
ICAO MID office has developed a Proposal For Amendment (PFA) of the SUPPs Doc 7030 to delete “STS/NONRNAV”.
Our concern is how the European special requirements will affect our Region???
7/12/2011

11. State Variation
All MID states are requested to cater any variation in the new FPL and delete any special requirement and updated the regional PFF accordingly.
7/12/2011