Improving Error Messaging in IFPS for Flight Plan Rejections

Proposal to enhance error messages in the Integrated Initial Flight Plan Processing System (IFPS) to differentiate between lateral rerouting and vertical constraint infringements, aiming to increase efficiency and reduce unnecessary costs for airlines. The current status indicates a system change request with a high cost estimate under assessment for future implementation.

• Flight Plan
• Error Messaging
• Efficiency Improvement
• Airspace Design
• System Change

draven Follow

Uploaded on Jul 30, 2024 | 0 Views

Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

Presentation Transcript

1. IFPS Error Messages in Flight Plan Rejections Status report Tihomir Todorov Head of Section Airspace Design 29 JAN 2018

2. Problem Statement Today, in case a flight plan is on a correct (lateral) routing, but does not respect a certain type of vertical constraint (normally coming from LoA restrictions), an error message generated by IFPS sometimes wrongfully contains the phrase: "on forbidden route". This is misleading and may be perceived as a request for lateral rerouting, potentially causing unnecessary costs due to increased fuel burn and delay, instead of correctly, indicating the infringement of a vertical constraint. PROPOSED SOLUTION In order to improve IFPS error messaging and also RAD efficiency, a distinction needs to be made in error messages between infringements of a restricted flight level (or level band) and infringements of a restricted route (e.g. for selected destinations). Document Confidentiality Classification: Green

3. Example Invalid FPL in IFPS that reports the error IS ON FORBIDDEN ROUTE . (FPL-TEST-IN -GALX/M-SDFGHM3RWXY/H -LEPA1130 -N0467F360 MEROS UN853 KINES -LSGG0118 LFLL -PBN/A1B2B3B4D2D3) PROF204: RS: TRAFFIC VIA IRMAR IS ON FORBIDDEN ROUTE REF:[LSLF1113K] IRMAR Document Confidentiality Classification: Green 3

4. Example LSLF1113K requires the flight below FL305 at IRMAR IRMAR Not available for traffic 7. ARR BERN_GROUP, GENEVA_GROUP,GENE VA_AREA a. Above FL305 LUSOL IRMAR KINES Document Confidentiality Classification: Green 4

5. Example The insertion of a flight level change makes the FPL valid: (FPL-TEST-IN -GALX/M-SDFGHM3RWXY/H -LEPA1130 -N0467F360 MEROS UN853 LUSOL/N0470F300 UN853 KINES -LSGG0118 LFLL -PBN/A1B2B3B4D2D3) Document Confidentiality Classification: Green 5

6. Current Status The request for system change has been made (CR_035910). The initial assessment of the change resulted in an estimate of a high cost to implement. The change is in the queue for implementation in a future NM release with no concrete release identified. Document Confidentiality Classification: Green 6

7. QUESTIONS and COMMENTS Document Confidentiality Classification: Green