OI/14-243
Issued on: / Subject / Validity / NOP Portal: Yes
Briefing:: No
17/12/2014
By : HOT / IFPS Users manual: addition to section 157 IFPS ERROR MESSAGES / From: 17/12/2014
To: UFN
Applicability / AD / FCM / NMC / FPL / / RPL /
- Introduction
The following instruction amends section 157 of the IFPS Users Manual by adding two additional warning type errors.
The electronic version of the IFPS Errors (straight access from CHMI and NOP or access via internet) has been updated.
- Amendment
157.XXX. Error Class/Error Id: WARN258
Error Message(s)
WARN258: INVALID AIRCRAFT ADDRESS (CODE) HAS NOT BEEN STORED. PREVIOUS AIRCRAFT ADDRESS HAS BEEN REMOVED
Possible values in Error Message
Code: 24-bit aircraft address of the aircraft.
Can be ignored: NO
Systematic Rejection Catalogue: NO
Reason
Whenever the sub-field CODE is present in a message submitted to the IFPS for processingthat does not contain 6 alphanumeric in the correct format, and the IFPS does hold a CODEvalue from a previously-processed associated message, then the sub-field CODE and itscontents shall be automatically removed from that message and from the previouslyprocessedassociated message.
Requirements
Flightsplanning to use CPDLC over the aeronautical telecommunication network (ATN) shall include in Item 18 of the flight plan the indicator CODE/ followed by the 24-bit aircraft address.
IFPS Procedures
When this warning message is presented in an invalid message, no action shall be taken by the IFPS staff tovalidate the message against that warning message.
Should the warning message be presented at the same time as any other error messages, only those othererrors shall be corrected.
Internal IFPS Procedures
NA
RPL Procedures
NA
Related Sections
105. CODE
157.XXX. Error Class/Error Id: WARN262
Error Message(s)
WARN262: WHAT-IF-REROUTE MESSAGE
Possible values in Error Message
NA
Can be ignored: NO
Systematic Rejection Catalogue: NO
Reason
The message is the result of an action in NOP or CHMI where an aircraft operator chose an alternative routeing and let NOP or CHMI create and send a modification message (CHG)or a cancel (CNL) to IFPS.The AWR/Rn qualifier present in the message prioritizes the invalid message to the top of the invalid queue.
Requirements
NA
IFPS Procedures
The message created as a result of the AOWIR functionality shall be treated in IFPS the same way as any other message.
Therefore on receipt of such a message, the IFPS stall shall apply SCP1.
Note: messages as a result of AOWIR have been checked against IFPS; therefore they should, only in rare cases, come for manual processing.
When the message is an FPL, this means that the originator has used the “Apply” feature in which ETFMS send a CNL message to IFPS.
Subsequently ETFMS send an RRN message containing the new route description. In some cases the re-filing is linked to a slot booking.
The originator is expected to refile a FPL in a specific time window, with the route received in the RRN message and it should be an exact character match between the RRN route and the route field of the FPL (Item 15).
A reason for which the FPL is coming for manual processing in IFPS might be due to the fact that the originator has modified part of the route (thus raising an error in IFPS) resulting in the refiling not matching exactly the RRN routeing and subsequently not matching the slot which had been booked for that flight.
Internal IFPS Procedures
NA
RPL Procedures
NA
Related Sections
27. SCP1
71. AIRCRAFT OPERATOR WHAT-IF RE-ROUTE (AOWIR)
With the addition of the above WARN262 error, section 71.4 Internal Procedure for AOWIR message (only present in NMOC staff version of the manual) has become obsolete.
Current Operations Manager
NOTE: The official electronic version takes precedence over any paper copies (except in the event of contingency)Page 1 of 3