NETWORK OPERATIONS HANDBOOK

EUROCONTROL
ANNEX TO THE IFPS USERS MANUAL

ANNEX to the IFPS USERS MANUAL

Generated Errors

Edition N°: 16.1

www.eurocontrol.int/lists/publications/network-operations-library

Amendment date: 15-Nov-2012 EDITION 16.1 ANNEX IFPS MAN i

Edited & produced by EUROCONTROL
©2012 The European Organisation for the Safety of Air Navigation (EUROCONTROL)
 ©2012 The European Organisation for the Safety of Air Navigation
(EUROCONTROL). This document is published by EUROCONTROL
for information purposes. It may be copied in whole or in part,
provided that EUROCONTROL is mentioned as the source and the
extent justified by the non-commercial use (not for sale). The
information in this document may not be modified without prior
written permission from EUROCONTROL.

Edition No. : 16.1

Edition Validity date : 15-Nov-2012
Reference : ANNEX TO THE IFPS USERS MANUAL
File name : Generated Errors
Number of pages : 19

Amendment date: 15-Nov-2012 EDITION 16.1 ANNEX IFPS MAN ii

Edited & produced by EUROCONTROL
©2012 The European Organisation for the Safety of Air Navigation (EUROCONTROL)
 Error Class Error Text Reason Requirements
MESSAGE ASSOCIATES TO The submitted message associates to a stored flight plan It is not always possible to update a stored flight plan
EFPM309 {ARG1/FLTSTATE} FLIGHT that has been off block/activated/terminate/deleted in the when the flight has been activated.
NM systems
FREEZE POINT {ARG1/POINT} NOT ON Errors given when using the route proposals tool in the NOP
RA307
FLIGHT ROUTE Portal or via B2B.
CANNOT IDENTIFY {ARG1/ITEM_A} POINT IN Internal IFPS Error N/A
ROUTE306
THE ROUTE
ROUTE CONTAINS A SYSTEM GENERATED Internal IFPS Error N/A
ROUTE305 PORTION AND FLIGHT TYPE IS MILITARY.
PLEASE CHECK.
CANNOT AUTOMATICALLY GENERATE Internal IFPS Error N/A
ROUTE304
ROUTE WITH VFR OR OAT PORTION
NO VALID ROUTE FOUND TO CONNECT TO Internal IFPS Error N/A
ROUTE303
FLIGHT ROUTE.
CANNOT AUTOMATICALLY GENERATE Internal IFPS Error N/A
ROUTE302
ROUTE WITH IFPSTOP PORTION.
NO VALID CONNECTION POINT FOUND ON Internal IFPS Error N/A
ROUTE301
FLIGHT PLAN ROUTE.
THE AVOID POINT AND VIA POINT CANNOT Errors given when using the route proposals tool in the NOP
RA282
BE THE SAME Portal or via B2B.
NUMBER OF CONSTRAINTS FOR ROUTE Errors given when using the route proposals tool in the NOP
RA281
GENERATION EXCEEDS {ARG1/NUMBER} Portal or via B2B.
DUPLICATE KEYWORD {ARG1/KEYWORD} IN Errors given when using the route proposals tool in the NOP
RA280
ROUTE GENERATION PARAMETERS Portal or via B2B.
ROUTE ENTIRELY FROZEN. NO ROUTE Errors given when using the route proposals tool in the NOP
RA279
GENERATION POSSIBLE Portal or via B2B.
CANNOT FREEZE FROM/TO {ARG1/POINT} Errors given when using the route proposals tool in the NOP
RA278
Portal or via B2B.
INVALID RFL Errors given when using the route proposals tool in the NOP
RA276
Portal or via B2B.
INVALID SPEED Errors given when using the route proposals tool in the NOP
RA275
Portal or via B2B.
/NBROUTE ARGUMENT INVALID Errors given when using the route proposals tool in the NOP
Portal or via B2B.
RA274
The error is given if the user requests an invalid number of
routes - e.g. 0
AERODROMES TOO CLOSE TO EACH OTHER Errors given when using the route proposals tool in the NOP
RA273
Portal or via B2B.
AERODROME OF DESTINATION DOES NOT Errors given when using the route proposals tool in the NOP
RA272
EXIST IN ENV DATABASE Portal or via B2B.
Amendment date: 15-Nov-2012 EDITION 16.1 ANNEX IFPS MAN 3
Edited & produced by EUROCONTROL
©2012 The European Organisation for the Safety of Air Navigation (EUROCONTROL)
 Error Class Error Text Reason Requirements
AERODROME OF DEPARTURE DOES NOT Errors given when using the route proposals tool in the NOP
RA271
EXIST IN ENV DATABASE Portal or via B2B.
UNKNOWN AIRCRAFT TYPE Errors given when using the route proposals tool in the NOP
RA270
Portal or via B2B.
AIRSPACE {ARG1/AIRSPACE} DOES NOT Errors given when using the route proposals tool in the NOP
RA269
EXIST IN ENV DATABASE Portal or via B2B.
POINT {ARG1/POINT} DOES NOT EXIST IN Errors given when using the route proposals tool in the NOP
RA268
ENV DATABASE Portal or via B2B.
ACTUAL DATE AND TIME OF ARRIVAL IS NOT The filed arrival time is more than 10 minutes in the future, Where an ARR message is filed, the arrival time
EFPM250 WITHIN ACCEPTABLE RANGE, AFTER when compared to the current system time. should not be in the future.
RECEPTION TIME.
ACTUAL DATE AND TIME OF DEPARTURE IS The filed departure time is more than 10 minutes in the Where a DEP message is received, the departure time
EFPM249 NOT WITHIN ACCEPTABLE RANGE, AFTER future, when compared to the current system time. should not be in the future.
RECEPTION TIME.
AERODROME IS ZZZZ BUT {ARG1} IS NOT Wide range of applications.
EFPM248
PRESENT
ALTERNATE AERODROME IS ZZZZ BUT ALTN Item 16c contains ZZZZ but no ALTN indicator is present in Where an unclassified alternate aerodrome is
INFO IS NOT PRESENT Item 18. indicated as ZZZZ in Item 16c, it is necessary to
EFPM247
include the Item 18 sub-field ALTN with relevant
details of that aerodrome
AIRCRAFT TYPE AND TYPZ PRESENT The aircraft type is given in Item 9, but TYP/ is also given in Where a known ICAO aircraft type designator is used
Item 18. in F9, the F18 TYP/ subfield should not also be used.
EFPM245
Any further details should be included in the RMK/
subfield.
AIRCRAFT TYPE IS ZZZZ The aircraft type is given in Item 9, but the Item 18 sub-field Where a known ICAO type designator is used in Item
TYP is also present or a message containing TYP/NIL has 9, the Item 18 sub-field TYP should not also be used.
EFPM244
been submitted that has not replaced the Item 9 ZZZZ with Any further details should be included in the sub-field
a known aircraft type designator. RMK.
AIRCRAFT TYPE IS ZZZZ BUT {ARG1} IS NOT The aircraft type is given in Item 9, but the Item 18 sub-field Where a known ICAO type designator is used in Item
PRESENT TYP is also present or a message containing TYP/NIL has 9, the Item 18 sub-field TYP should not also be used.
EFPM243
been submitted that has not replaced the Item 9 ZZZZ with Any further details should be included in the sub-field
a known aircraft type designator. RMK.
Z PRESENT BUT COM/DAT/NAV ABSENT Field 10a contains Z, but no explanation is given in either Either remove the Z from field 10a or add a COM,
EFPM166 (CEQPT) the COM,NAV or DAT sub-fields in field 18. NAV or DAT/ sub-field in field 18.
R PRESENT BUT PBN ABSENT (CEQPT) Field 10a contains R, but no PBN/ is given in field 18. Where R is used in the equipment designators of a flight
plan, it is necessary to specify the performance based
EFPM166 navigation (PBN) levels and/or the required navigation
performance (RNP)levels that can be met by inserting in
item18 PBN/ followed by the relevant descriptors.

Amendment date: 15-Nov-2012 EDITION 16.1 ANNEX IFPS MAN 4

Edited & produced by EUROCONTROL
©2012 The European Organisation for the Safety of Air Navigation (EUROCONTROL)
 Error Class Error Text Reason Requirements
PBN PRESENT BUT R ABSENT (CEQPT) Field 18 contains PBN/ but R is not specified in field 10a. Where PBN/ is used in the item 18 of a flight plan, it
specifies the performance based navigation (PBN)
levels and/or the required navigation performance
EFPM166 (RNP)
levels that can be met. It can only be present if the
aircraft is PBN approved which is notified with the
descriptor R in item 10a.
FILED PBN REQUIRES CEQPT < > The filed PBN in item 18 requires specific equipment not A performance based navigation level is achieved by
specified in item 10a. the carriage of certain equipment. Some equipment(s)
EFPM167 are not
specified in the flight plan whereas the PBN/ indication
in item 18 require that equipment to be present.
DATE GIVEN IS INCONSISTENT WITH {ARG1} In RPL - if a from date is later than a to date or if the period
{ARG2} of operation is not within the activation period for a given
RPL
EFPM240
In IFPS when an ARR message has an ATA that is earlier
than the ATD.
MESSAGE FILED BEFORE MATCHING FILED The message has a filing time earlier than that of an The IFPS shall treat all associated messages in order
EFPM238
FLIGHT PLAN existing flight plan. of filing time.
MESSAGE MATCHES EXISTING INVALID The message associates with another message that has Where any message fails automatic processing and is
MESSAGES failed automatic processing and is awaiting or undergoing moved to the manual treatment queue, all subsequent
manual treatment by the IFPS staff. associated messages shall be linked to that invalid
EFPM237 message and shall not be treated until that invalid
message has been treated by the IFPS staff. This is a
safety check to ensure that messages are treated in
the correct sequence.

Amendment date: 15-Nov-2012 EDITION 16.1 ANNEX IFPS MAN 5

Edited & produced by EUROCONTROL
©2012 The European Organisation for the Safety of Air Navigation (EUROCONTROL)
 Error Class Error Text Reason Requirements
ESTIMATED OFF BLOCK DATE AND TIME NOT For a FPL the filed EOBT and DOF is more than 30 minutes For DLA messages and CHG messages updating an
IN THE ACCEPTABLE RANGE: {ARG1/START} in the past, or more than 144 hours (6 days) in the future, existing EOBT to be accepted by the IFPS, the new
TO {ARG2/END} when compared to current system time. EOBT must not be less than the IFPS time at the time
of processing, or not more than 20 hours in advance of
For a DLA or CHG the filed EOBT and DOF is more than 0 the IFPS time at the time of processing.
minutes in the past, or more than 20 hours in the future, For FPL messages containing a DOF, the IFPS may
when compared to current system time. accept messages with an EOBT up to 12 hours in the
past, and up to 144 hours (6 days) in advance of the
EFPM236 EOBT, but those FPLs with an EOBT more than 30
minutes in the past shall fail automatic processing in
the IFPS.
Those FPL messages not containing a DOF shall be
processed automatically, but shall be considered to
take place in the 24 hour period that starts 30 minutes
in the past when compared to the current time, with
the appropriate DOF being automatically inserted by
the IFPS.
FIELD FORBIDDEN IN THIS TYPE OF The field that is specified in the error message is not Check that the TITLE of the message is correct and
EFPM235 MESSAGE expected for the type of message submitted (e.g. EST that unnecessary field have not been included in the
DATA in a FPL). submitted message.
ESTIMATED OFF BLOCK DATE AND TIME IS The filed DOF is more than 30 minutes in the past, or more For DLA and CHG messages updating an existing
NOT WITHIN ACCEPTABLE RANGE, AFTER than 144 hours (6 days) in the future, when compared to EOBT to be accepted by the IFPS, the new EOBT
FILING TIME. current system time. must not be less tha the IFPS time at the time of
processing, and not more than 20 hours in advance of
the IFPS time at the time of processing. For FPL
messages containing a DOF, the IFPS may accept
messages with an EOBT up to 12 hours in the past,
and up to 144 hours (6 days) in advance of the EOBT,
EFPM234
but those FPLs with an EOBT more than 30 minutes in
the past shall fail automatic processing in the IFPS.
Those FPL messages not containing a DOF shall be
processed automatically, but shall be considered to
take place in the 24 hour period that starts 30 minutes
in the past when compared to the current system time,
with the appropriate DOF being inserted automatically
by the IFPS.
FLIGHT PLAN ALREADY GENERATED FROM A flight plan matching the submitted message has already To submit a FPL, the flight that was generated from
EFPM233
RPL DATA been generated from RPL data. RPL data must first be cancelled.
FLIGHT PLAN ALREADY RECEIVED FROM A flight plan matching the submitted message has already The same flight plan has already been received and
EFPM232
ADDRESS {ARG1} been received from the indicated address. accepted by IFPS from the given address.
CIVIL FORMATION FLIGHT NOT PERMITTED In the submitted message, the flight type is not given as M, Within the EUR RVSM airspace, formation flights are
EFPM231
IN EUR RVSM AIRSPACE and the number of aircraft indicated is more than 1. only allowed for military flights.
ASSOCIATION NO LONGER VALID THE FPD IS Fpd Closed would be raised if whilst processing an
EFPM230
CLOSED associated message - an FPD became closed.
Amendment date: 15-Nov-2012 EDITION 16.1 ANNEX IFPS MAN 6
Edited & produced by EUROCONTROL
©2012 The European Organisation for the Safety of Air Navigation (EUROCONTROL)
 Error Class Error Text Reason Requirements
INVALID FORMAT When the ETO in an AFIL messages is in an incorrect The correct format must be used.
EFPM229
format.
EFPM228 INVALID VALUE {ARG1} Wide range of applications.
MANUAL ADDRESSING REQUIRED. PRESS An internal check for the IFPS staff to add any addresses Following the insertion of IFPSTOP/IFPSTART but the
EFPM227 APPLY TO CONTINUE following the use of IFPSTO/IFPSTART. IFPS staff, it may be necessary for them to manually
add extra distribution addresses.
THIS {ARG1/TITLE} MESSAGE ASSOCIATES Internal IFPS error for when an APL message created from
EFPM226
WITH THE FPD: {ARG2/KEYS} FNM/MFS/AFP partially associates with an existing FPD.
EFPM225 MISSING OR ERRONEOUS FIELD Wide range of applications.
MESSAGE MATCHES MULTIPLE FLIGHT The IFPS holds more than one valid flight plan with which Where there is more than one matching flight plan is
PLANS the invalid message may match. held in the IFPS, the correct message association may
EFPM224
be increased in accuracy by adding the EOBT and
DOF of the submitted message.
EOBT IN THE PAST COMPARED TO IFPS At the time of processing, the EOBT in the submitted The IFPS shall only accept those messages that
SYSTEM TIME: {ARG1} message is in the past compared to the IFPS system time. indicate an EOBT that is not in the past when
EFPM223
compared to the IFPS system time at the time of
processing that message.
NO EXISTING FILED FLIGHT PLAN MATCHES The IFPS does not hold a valid flight plan that matches the The referent flight plan may or may not have been
THIS MESSAGE key fields indicated in the submitted message. filed; it may have been cancelled or closed by another
party, or the key fields in the submitted message do
EFPM220
not match. Also, the referent flight plan may be an RPL
that has not yet been generated in IFPS (this occurs at
20 hours in advance of EOBT).
NON RVSM APPROVED FLIGHT WITHIN EUR In the submitted message, the flight rules are not M, the Flights within the EUR RVSM airspace are required to
RVSM AIRSPACE equipment does not contain W, and STS/NONRVSM is not be suitably equipped (Item 10 includes 'W') or to be a
EFPM219
found in Item 18. military flight (Item 8 flight type is 'M') or the exempted
(STS/NONRVSM in Item 18).
FPL WITH SAME ARC_ID AND OVERLAPPING A valid flight plan exists in the IFPS with a given total flying The IFPS cannot accept a flight plan that has the
FLYING PERIOD EXISTS:{ARG1} time that overlaps with that given in the submitted message. same callsign and a flying time, based on the EOBT
EFPM217
and total estimated elapsed flying time, that overlaps
with an existing valid flight plan.
POSSIBLE DOF SUBFIELD WITH WRONG A possible incorrectly formatted DOF has been identified in The IFPS shall check for a DOF in the correct format
SYNTAX DETECTED IN FIELD18. the flight plan. of DOF/YYMMDD. The IFPS shall also check for any
EFPM216 sequence of the letters D, O and F, even when other
characters may separate those letters, and raise the
error as a warning where this is found.
FLIGHT PLAN DATA HAS RESTRICTED The requested flight plan is not available for unauthorised The requested flight plan has been classified as
EFPM215
ACCESS. access. sensitive and is not available for unauthorised access.
MISSING ROUTE DATA No Item15 (route) data is present in the message. It is mandatory to fill in as much relevant detail as
EFPM214 possible in Item 15 of a flight plan. The minimum
possible is DCT.
UNEXPECTED ROUTE DATA Raised if the route field is found in an unexpected
EFPM213
messaged (e.g. MFS message).
Amendment date: 15-Nov-2012 EDITION 16.1 ANNEX IFPS MAN 7
Edited & produced by EUROCONTROL
©2012 The European Organisation for the Safety of Air Navigation (EUROCONTROL)
 Error Class Error Text
FIELDS 10 AND/OR 18 INCORRECT FOR
STATE FORMATION FLIGHT IN EUR RVSM
EFPM212
AIRSPACE
STS/NONRVSM IS REQUIRED FOR NON
EFPM211 RVSM APPROVED STATE FLIGHT
NON RVSM APPROVED FLIGHT WITHIN EUR
EFPM210 RVSM AIRSPACE AND STS/NONRVSM IS NOT
EXPECTED FOR A CIVIL AIRCRAFT
STS/NONRVSM IS NOT EXPECTED FOR AN
EFPM209 RVSM APPROVED FLIGHT WITHIN EUR RVSM
AIRSPACE
THE DCT SEGMENT <Point A> .. <Point B> IS
NOT AVAILABLE IN FL RANGE <FL_Range>
PROF206
(UNAVAILABLE ROUTE <ROUTE ID>)
RS: TRAFFIC VIA <Ref_Loc_Id> IS OFF
PROF205 MANDATORY ROUTE REF: <Restriction_Id>
<Textual Description>
PROF204: RS: TRAFFIC VIA <Ref_Loc_Id> IS
ON FORBIDDEN ROUTE REF:
<Restriction_Id> <Textual Description> or
PROF204: RS: TRAFFIC VIA
PROF204
<Ref_Loc_Id>:<FL_Range>
[<DDHHMM..DDHHMM>] IS ON FORBIDDEN
ROUTE REF: <Restriction Id> <Textual
Description>
PROFILE ANALYSIS STOPPED
PROF203
{ARG1/POINT1} {ARG2/ROUTE}
{ARG3/POINT2} IS NOT AVAILABLE IN FL
PROF202 RANGE {ARG4/FL_RANGE}
CANNOT CLIMB OR DESCEND ON <Point>
<Route> <Point> IN FL
PROF201
RANGE <FL_Range> BECAUSE OF
UNAVAILABLE LEVELS ON <Route_List>
Amendment date: 15-Nov-2012 EDITION 16.1
©2012 The European Organisation for the Safety of Air Navigation (EUROCONTROL)
Reason
In the submitted message, the flight type is given as M; the
number of aircraft indicated is more than 1, and either W is
included in Item 10 or STS/NONRVSM is not included in
Item 18.
In the submitted message, the flight type is given as M, the
equipment does not contain W, and STS/NONRVSM is in
Item 18.
In the submitted message, the flight type is not given as M,
the equipment does not contain W, and STS/NONRVSM is
in Item 18.
In the submitted message, the equipment contains W, but
Item 18 contains STS/NONRVSM.
The indicated DCT route has been classified as unavailable
at the requested flight level filed and the system is unable to
connect the two points via an airway.
The route detailed in the submitted message does not
comply with the specified mandatory RAD route.
The route detailed in the message follows the listed
forbidden RAD route.
The system is unable to continue creating a profile for the
flight.
The flight has been calculated to fly on a closed CDR-0.
The flight has been calculated to climb or descend on a
route segment, but there are no levels available on this
segment between the previous and current flight level.
ANNEX IFPS MAN
Edited & produced by EUROCONTROL
Requirements
Within the EUR RVSM airspace, State formation
flights shall not include W in Item 10, but must include
STS/NONRVSM in Item 18.
Within the EUR RVSM airspace, military flights shall
contain STS/NONRVSM.
Within the EUR RVSM airspace, civil flights shall not
be given STS/NONRVSM.
Within the EUR RVSM airspace, where a flight
indicates 'W' in Item 10, then Item 18 should not
contain STS/NONRVSM.
The specified direct route in the submitted flight plan is
not available at the requested flight level, so an
available route using the ATS route structure is
required for this segment.
The filed route must comply with all relevant RAD
restrictions.
The filed route must comply with all relevant RAD
restrictions.
Ensure that all information in the message is accurate.
The profile calculation for each flight plan will check
the calculated arrival time and flight level of the flight
for each part of a route, and cross-check this time
against the published availability conditions for that
part of that route at that time.
When building a flight profile, the IFPS must find at
least one available level between the previous and
current flight level on the route segment in which the
climb or descent takes place.
8
 Error Class Error Text Reason Requirements
<Point> <Route> <Point> IS A CLOSED CDR_1 The given route segment is classified as unavailable CDR1 The profile calculation for each flight plan will check
IN FL RANGE <FL_Range> at the calculated time of use by this flight. the calculated arrival time and flight level of the flight
PROF200 for each part of a route, and cross-check this time
against the published availability conditions for that
part of that route at that time.
<Point> <Route> <Point> IS A CLOSED CDR_2 The given route segment is classified as unavailable CDR2 The profile calculation for each flight plan will check
IN FL RANGE <FL_Range> at the calculated time of use by this flight. the calculated arrival time and flight level of the flight
PROF199 for each part of a route, and cross-check this time
against the published availability conditions for that
part of that route at that time.
<Point> <Route> <Point> IS A CDR_3 IN FL The given route segment is classified as unavailable CDR3 The profile calculation for each flight plan will check
RANGE <FL_Range> at the calculated time of use by this flight. the calculated arrival time and flight level of the flight
PROF198 for each part of a route, and cross-check this time
against the published availability conditions for that
part of that route at that time.
RS: CLOSED AT: REF: UNTI: BETWEEN: The route detailed in the submitted message follows the The filed route must comply with all relevant RAD
PROF197
listed closed RAD route. restrictions.
<Point> <Route> <Point> DOES NOT EXIST IN The given route does not exist at the requested flight level The profile calculation for each flight plan will check
FL RANGE <FL_RANGE> between the indicated points. the calculated arrival time and flight level of the flight
PROF195 for each part of a route, and cross-check this time
against the published existence for that part of that
route at that time
(Point> <Route> <Point> IS NOT AVAILABLE The given route is classified as unavailable at the requested The profile calculation for each flight plan will check
IN FL RANGE <FL_Range> flight level between the indicated points. the calculated arrival time and flight level of the flight
PROF194 for each part of a route, and cross-check this time
against the published availability conditions for that
part of that route at that time.
IFR OPERATIONS AT AERODROME The departure/destination aerodrome cannot be accessed The flight should be filed with a VFR segment.
PROF193 {ARG1/AERODROME} ARE NOT PERMITTED under IFR rules
[{ARG2/RESTRICTION_ID}]
TOTAL STAY TIME GREATER THAN TOTAL The submitted message contains an en-route STAY The IFPS shall check the given EET for a submitted
ESTIMATED ELAPSED TIME. indicator with a time greater than the total estimated flight plan, and where a STAY indicator is used in the
elapsed time indicated in Item 16b. route, the associated time is also checked. Where the
PROF192
STAY time is incompatible with the calculated total
EET (including its accepted percentage error), an error
is generated.
TTL_EET DIFFERENCE > (value) %, The total EET given is greater than the accepted maximum The IFPS shall calculate a total estimated flying time
CALCULATED TTL_EET <ADEP> FROM TO calculated by the IFPS for this trajectory. for all flight plans, based on the speed(s) and flight
PROF191 <ADES>= <Time> (HHMM) level(s), and will raise a warning where the total EET of
the submitted message is outside the accepted
percentage error based on this figure.

Amendment date: 15-Nov-2012 EDITION 16.1 ANNEX IFPS MAN 9

Edited & produced by EUROCONTROL
©2012 The European Organisation for the Safety of Air Navigation (EUROCONTROL)
 Error Class Error Text Reason Requirements
NON 8.33 AND NON UHF EQUIPPED The submitted flight plan does not indicate that the flight The indicated sector(s) require that all flights intending
AIRCRAFT IN 8.33 AIRSPACE does not carry the necessary equipage to enter 8.33kHz to use that airspace carry either 8.33kHz equipage (Y
PROF190
airspace. in Item 10) or UHF (U in Item 10), but the submitted
message contains neither.
NON 8.33 BUT UHF EQUIPPED AIRCRAFT IN The indicated equipment contains U, but the flight is The indicated sector(s) require that all flights intending
8.33 AIRSPACE NOT HANDLING UHF calculated to enter a sector(s) that requires Y equipage. to use that airspace carry the full 8.33kHz equipage (Y
PROF189
in Item 10); UHF (U in Item 10) alone as indicated in
the submitted message is not sufficient.
FLIGHT PLAN DOES NOT COMPLY WITH 8.33 The flight does not comply with those mandatory conditions The flight must be compliant with all 8.33kHz
PROF188 CARRIAGE REQUIREMENTS associated with the IFPZ 8.33kHz airspace. conditions in Items 10, 15 & 18 when that flight is
planned to enter the IFPZ 8.33kHz airspace.
ROUTE180 ROUTE ANALYSIS HAS ABORTED Wide range of applications.
CRUISING FLIGHT LEVEL INVALID OR The filed cruising flight level is either incorrect or beyond the The IFPS holds a performance table for each aircraft
INCOMPATIBLE WITH AIRCRAFT known performance of the filed aircraft type. type that includes the maximum known flight level
PERFORMANCE attainable for that type. Where the filed cruising flight
ROUTE179
level is either incorrect or beyond the known
performance of the filed aircraft type, an error is
generated.
CRUISING SPEED IS INVALID OR The filed cruising speed is either incorrect or beyond the The IFPS holds a performance table for each aircraft
INCOMPATIBLE WITH AIRCRAFT known performance of the filed aircraft type. type that includes the maximum known speeds at
PERFORMANCE certain flight levels attainable for that type. Where the
ROUTE178
filed cruising speed is either incorrect or beyond the
known performance of the filed aircraft type at that
level, an error is generated.
FLIGHT LEVEL AT IS INVALID OR The flight level filed at the given point is either incorrect or The IFPS holds a performance table for each aircraft
INCOMPATIBLE WITH AIRCRAFT beyond the known performance of the filed aircraft type. type that includes the maximum known flight level
ROUTE176 PERFORMANCE attainable for that type. Where the filed flight level is
either incorrect or beyond the known performance of
the filed aircraft type, an error is generated.
SPEED AT {ARG1/POINT} IS INVALID OR The speed filed at the given point is either incorrect or The IFPS holds a performance table for each aircraft
INCOMPATIBLE WITH AIRCRAFT beyond the known performance of the filed aircraft type. type that includes the maximum known speeds at
PERFORMANCE certain flight levels attainable for that type. Where the
ROUTE175
filed cruising speed is either incorrect or beyond the
known performance of the filed aircraft type at that
level, an error is generated.
INVALID TIME GIVEN FOR {ARG1} The time given for an EET for a boundary or point is The time given for an EET point must be less than the
ROUTE174 incorrectly formatted or is greater than the total EET for that total EET for the flight in Item 16b and greater than
flight. zero.
MULTIPLE ROUTES BETWEEN AND . More than one available route exists between the indicated Several possible routes exist between the indicated
ROUTE172
POSSIBLE ROUTES ARE: points. points and the appropriate one should be specified.
CANNOT EXPAND THE ROUTE The flight has been calculated to transit an artificial route Such a route segment cannot be used; an alternative
ROUTE171
segment (GAP). route must be used instead.

Amendment date: 15-Nov-2012 EDITION 16.1 ANNEX IFPS MAN 10

Edited & produced by EUROCONTROL
©2012 The European Organisation for the Safety of Air Navigation (EUROCONTROL)
 Error Class Error Text Reason Requirements
CANNOT FIND ENTRY/EXIT POINT ON The IFPS is unable to automatically determine the IFPZ An IFPZ entry or exit point should be included in the
ROUTE170
{ARG1/ROUTE} entry or exit point of the flight. route.
CONSECUTIVE STAY INDICATORS NOT Consecutive STAY indicators have been found associated Each STAY indicator must have a point before and
ROUTE169 ALLOWED with the same point. after that STAY information. It is not possible to have
consecutive STAY indicators at the same point.
INVALID DCT. DCT ARE NOT ALLOWED TO The specified DCT routing is not allowed as it crosses the Each FIR may specify whether or not it will allow DCT
CROSS THE BORDER BETWEEN AND indicated FIR border. routings across its border, so the specified DCT
ROUTE168
routing is not allowed as it crosses the indicated FIR
border.
THE DCT SEGMENT : NM IS TOO LONG FOR The portion of the specified DCT segment within the limits The specified direct route in the submitted flight plan
MAXIMUM IS: NM of an FIR exceeds the ‘en-route DCT limit’ for that FIR and exceeds the given maximum for the indicated
ROUTE165
the system is unable to connect the two points via an airspace, so an available route using the ATS route
airway. structure is required for this segment.
THE POINT FROM ESTIMATE DATA IS NOT IN An estimate is given in Item 18 for a point not on the filed IFPS will compare any estimate points given in Item 18
ROUTE162 THE FLIGHT ROUTE route. against the route, and raise an error for any estimate
point not calculated in the given route.
THE POINT FROM DLE DATA IS NOT IN THE A point specified in the DLE indicator is not on the route. A point specified in the DLE indicator shall be explicitly
ROUTE162
FLIGHT ROUTE or implicitly present on the flight route.
THIS FIELD VALUE IS INCONSISTENT WITH The flight rules are Y or Z, but the IFPS is unable to identify The flight rules and any changes thereto in Item 15
ROUTE161 THE FLIGHT RULES. conditions within Item 15 that are consistent with the given must correspond.
flight rules.
INVALID RFL AT EUR RVSM AIRSPACE The level indication at the RVSM entry/exit point does not The level indicated at the RVSM entry/exit point must
ROUTE159
ENTRY/EXIT correspond to the correct cruise level for that route. comply with the RVSM levels published for that route.
INVALID EUR RVSM AIRSPACE ENTRY/EXIT The level indication at the RVSM entry/exit point and/or the It is required to indicate the speed and level at the
CONDITION RVSM entry/exit point has not been included in the EUR RVSM entry/exit point, and a valid route
ROUTE158
submitted route, or if there is an invalid route given immediately after the RVSM entry/exit point.
immediately after the RVSM entry/exit point.
FLIGHT RULES I WITH VFR PART. The flight rules have been submitted as IFR only, but a If a change to VFR is intended, then the flight rules
ROUTE157
change to VFR is indicated at a point in the route. should be given as Y (IFR then VFR).
MULTIPLE JUNCTIONS BETWEEN AND. More than one possible junction point exists between the A specific point must be given at the junction between
ROUTE155
indicated airways. two airways.
FLIGHT NOT APPLICABLE TO IFPS The submitted message gives no indication of an IFR or Those flights planning to operate within the IFPZ must
ROUTE152 GAT portion of that flight within the IFPZ. have at least an identifiable IFR/GAT portion within the
IFPZ.
THE POINT CANNOT BE USED TO LEAVE OR The indicated point is not the first point of a STAR or the Where a terminal procedure is used in a route, that
JOIN THE TP last point of a SID, and may not be used to connect into or procedure must be followed to the last point if a
ROUTE151
out of the terminal procedure. departure procedure, or from the first point if an arrival
procedure.
MISSING CRUISING FLIGHT LEVEL No flight level has been filed in the route or that filed flight The cruising flight level must be indicated in Item 15.
ROUTE150 level is unrecognisable.
MISSING DESIGNATOR When there is a missing point in an EET or DLE field. All required fields must be present in submitted
ROUTE149
messages.

Amendment date: 15-Nov-2012 EDITION 16.1 ANNEX IFPS MAN 11

Edited & produced by EUROCONTROL
©2012 The European Organisation for the Safety of Air Navigation (EUROCONTROL)
 Error Class Error Text Reason Requirements
NO JUNCTION BETWEEN AND No known junction exists between the indicated airways. No known junction exists between the indicated
ROUTE148
airways, so a route should be built to connect them.
THE NAT TRACK IS NOT ACTIVE. The North Atlantic track indicated is not valid in the IFPS The North Atlantic tracks for that period must be valid
ROUTE147
system. in the IFPS.
A POINT IS EXPECTED AFTER A STAY A STAY indicator has been filed without the required point The STAY indicator is preceded by the point at which
ROUTE145 INDICATOR before and after the indicator. the STAY starts, and is followed by the point a which
the flight resumes the flight planned route.
NO ROUTE BETWEEN AND No route exists between the indicated consecutive points. Where two consecutive points are filed in a route, the
ROUTE144 IFPS can only automatically process them when a
valid available route exists between them.
A POINT DESIGNATOR IS EXPECTED For an AFIL FPL, the first point in the route is an airway. The route must not start with an unknown navigation
BEFORE {ARG1/ITEM} beacon, an airway, a DCT or any designator other
ROUTE143 than a known ICAO designator for a navigation
beacon, a navigation beacon with bearing/range, or a
set of geographical coordinates.
THE POINT {ARG1} IS NOT ON THE ROUTE The indicated point is not part of the given route. Any point filed as part of a route must be recognised
ROUTE141
{ARG2} as being associated with that route.
IS FOLLOWED BY WHICH IS NOT ONE OF ITS The indicated point is not published as a part of the given Any point filed as part of a route must be recognised
ROUTE140
POINTS route. as being associated with that route.
IS PRECEDED BY WHICH IS NOT ONE OF ITS The indicated point is not published as a part of the given Any point filed as part of a route must be recognised
ROUTE139
POINTS route. as being associated with that route
CANNOT HAVE A ROUTE BETWEEN THE It is not possible to file a route from a point to that same The filed route must ensure that the point - route –
ROUTE138
SAME POINT; ROUTE: , POINT: point. point sequence is correct and progressive.
THE SID LIMIT IS EXCEEDED FOR No known departure procedure exists between the There is no known departure procedure that exists to
AERODROME CONNECTING TO aerodrome and the specified first point of the route, and the connect the aerodrome to the specified first point of
ROUTE135
direct distance exceeds the maximum allowed for the route, and the direct distance exceeds the
departures at that aerodrome. maximum allowed for departures at that aerodrome.
THE STAR LIMIT IS EXCEEDED FOR No known arrival procedure exists between the aerodrome Where an arrival procedure exists, it should be used to
AERODROME CONNECTING TO and the specified last point of the route, and the direct connect the route to the arrival aerodrome. Where no
distance exceeds the maximum allowed for arrivals at that known arrival procedure exists, the distance from the
ROUTE134
aerodrome. last point of the route to the arrival aerodrome must be
within the limits for that aerodrome, or, if using DCT,
within DCT limits.
THE STAY PORTION AT POINT IS NOT A STAY indicator has been used for a flight that intends to The STAY indicator is only permitted for use with
ROUTE133 PERMITTED FOR A FLIGHT GOING OUT OF operate outside the IFPZ as well as inside. those flights that remain entirely within the IFPZ.
THE IFPZ
THE <sid or star> IS NOT VALID. <sid or star> IS There are several terminal procedures available at this A correct TP must be used.
SUGGESTED. OTHER POSSIBLE TPS VIA aerodrome and the flight does not comply with the
<List_Of_Points> ARE <TP> parameters of the terminal procedure indicated in the
ROUTE132
message. The first compliant terminal procedure is
assumed by the system. Other possibilities are presented to
the IFPS staff.

Amendment date: 15-Nov-2012 EDITION 16.1 ANNEX IFPS MAN 12

Edited & produced by EUROCONTROL
©2012 The European Organisation for the Safety of Air Navigation (EUROCONTROL)
 Error Class Error Text Reason Requirements
TRUNCATED ROUTE The route as filed has been truncated and is therefore The message should be submitted with the complete
ROUTE131
incomplete. route.
ROUTE130 UNKNOWN DESIGNATOR {ARG1} Wide range of applications.
INSUFFICIENT DATA TO RESOLVE This error is reported when a point that is present in the The message should be submitted with the point name
HOMONYM AT {ARG1/POINT} route field is stored more than once in the NM Environment replaced with the geographical coordinates of the
ROUTE129 database. Due to the proximity of the points associated with point.
the trajectory of the flight, IFPS cannot determine which of
the points to use.
VFR NOT PERMITTED IN OR ABOVE EUR The submitted message indicates that the flight intends to VFR at or above F290 is not permitted in the EUR
ROUTE128
RVSM AIRSPACE change to VFR in or above RVSM airspace. RVSM airspace.
ROUTE127 FLIGHT RULES V WITH IFR PART.
FLIGHT RULES Y WITH NO VFR PART. The flight rules are Y (IFR then VFR), but no VFR indicator The VFR indicator should be given in the route to
ROUTE126 is given in the route. indicate at which point the flight intends to change to
VFR.
FLIGHT RULES Z WITH NO IFR PART. The flight rules are Z (VFR then IFR), but no IFR indicator is The IFR indicator should be given in the route to
ROUTE125 given in the route. indicate at which point the flight intends to change to
IFR.
INVALID COMBINATION OF MODE S The Mode S indication is not unique or ADS-B & ADS-C is When the aircraft is equipped with Mode S surveillance,
SYN153 CAPABILITY AT ROW=x, COL=y notified without any transponder mode indicated (A, being ‘I’,’P’,’X’, only one descriptor is allowed and when
C&S). either E,H,L, S is present it excludes I, P and X.
INCONSISTENT WITH ASSOCIATED The message associates with a flight plan. The stored flight An old format flight plan may be updated by a new
FLIGHTPLAN FORMAT (OLD: <field name(s)>) plan is in new format and the associated message format message and vice versa provided the end
SYN136 (NEW: <field name(s)>) result of the processing is a fully consistent flight plan
is in old format or vice versa and there is inconsistent data
in these 2 messages. either old or new.
SYN124 MISSING OR INVALID CHANGE RULES When the CHGRUL field has been incorrectly defined.
EXPECTED CNA EQUIPMENT DESIGNATOR No communication or navigation equipment indicators are A minimum of 1 communication or navigation
SYN123
given in Item 10. equipment indicator must be given in Item 10.
EXPECTED DATE DESIGNATOR NOT FOUND The format of the DOF field is not correct. Always ensure that the FOF field is submitted in the
SYN122
correct format and that only one ‘/’ separator is used.
DUPLICATE ERROR AT ROW=x, COL=y (sub- There is a duplicate sub-field indicator which is not allowed. The following sub-field indicators DEP/,DEST, DOF/,
SYN121 field name) OPR/, RVR/, SEL/, REG/, PBN/, CODE/, ORGN/, PER/,
RFP/ shall only be specified once.
EQPT FIELD NOT ALLOWED Raised if you get the RPL specific EQPT/ field in an IFPS
SYN119
FPL
EXPECTED END OF MESSAGE A syntax error is causing IFPS to be unable to find the end The correct syntax must be used
SYN118
of the submitted message.
MISSING OR INVALID FLIGHT RULES The flight rules are either missing or using an invalid The flight rules must be present, and must use an
SYN117
designator. approved indicator.
MISSING OR INVALID FLIGHT TYPE The flight type is either missing or using an invalid The flight type must be present, and must use an
SYN116
designator. approved indicator.

Amendment date: 15-Nov-2012 EDITION 16.1 ANNEX IFPS MAN 13

Edited & produced by EUROCONTROL
©2012 The European Organisation for the Safety of Air Navigation (EUROCONTROL)
 Error Class Error Text Reason Requirements
EXPECTED FLIGHT TYPE AND RULES The flight type and flight rules are either missing or using an The flight type and flight rules must be present, and
SYN115
invalid designator. must use an approved indicator.
EXPECTED `/' A '/' is expected for correct formatting, but is missing. Where a '/' is necessary in the format of an item, it
SYN114
must be present in the submitted message.
INVALID MESSAGE LENGTH This is an RPL only error - when a line exceeds the allowed
SYN113
length.
INCORRECT USAGE OF BRACKETS '(' AND ')' The submitted message contains more brackets than just The opening and closing indicators of any message
SYN112 the opening and closing '(' and '). are '(' and ')' respectively, thus they cannot be used
within a message in any way.
MISPLACED INDICATOR. MUST BE AFTER A An indicator (VFR, IFR, GAT, OAT, etc.) in the route field An change of rules, flight type, etc must be put in the
SYN111
POINT does not follow a point. route field after a point designator.
INVALID BEARING DESIGNATOR The indicated bearing designator is outside the range 000 to Any bearing indication must reflect to a maximum
SYN110
360. value of 360º.
FIELD CONTAINS INVALID CHARACTER(S) One or more invalid characters used in the text. Ensure only valid characters are used in the text.
SYN109

INVALID DATE DESIGNATOR For an invalid date - e.g. an Alphabetic character in the The correct syntax must be used
SYN108
DOF
INVALID DISTANCE DESIGNATOR In an ADEXP format message for a badly formed distance The correct syntax must be used
SYN105
field in a reference (REF) point.
SYN104 INVALID FIELD One or more invalid characters used in the text. Ensure only valid characters are used in the text.
INVALID ID USED IN FIELD {ARG1/FIELD} Multiple STAY indicators with the same sequence number Where more than one STAY indicator is used in the
have been used in Item 15. route, each indicator must have a separate and
SYN103
consecutive sequence number, to a maximum value of
9.
INVALID LATITUDE DESIGNATOR The indicated latitude value does not contain either 2 or 4 The IFPS can only accept latitude values given as
SYN102
numbers. either 2 ot 4 numbers.
SYN101 INVALID LEVEL DESIGNATOR Incorrect syntax for the speed/level group has been used. The level indication must use the correct format.
INVALID LIST In an ADEXP format message when you have a -BEGIN The correct syntax must be used
SYN100 followed by an unexpected keyword - i.e. one that isn't
ADDR, RTE_PTS, EQCST
INVALID LONGITUDE DESIGNATOR The indicated longitude value does not contain either 3 or 5 The IFPS can only accept latitude values given as
SYN99
numbers. either 3 ot 5 numbers.
INVALID POINT In an ADEXP format message for problems with points in
SYN98
fields e.g. missing PTID in a REF point.
INVALID SEPARATOR The flight plan message has errors that cause the IFPS The correct syntax must be used
SYN97 system to be unable to distinguish between the expected
fields.
SYN96 INVALID SOURCE The SRC field in the flight plan message is not correct. The SRC field should not be sent to IFPS.
SYN95 INVALID SPEED DESIGNATOR Incorrect syntax for the speed/level group has been used. The correct syntax must be used
INVALID TIME DESIGNATOR The indicated time designator does not conform with the The correct syntax must be used
SYN93
standard 24-hour format.
Amendment date: 15-Nov-2012 EDITION 16.1 ANNEX IFPS MAN 14
Edited & produced by EUROCONTROL
©2012 The European Organisation for the Safety of Air Navigation (EUROCONTROL)
 Error Class Error Text Reason Requirements
MISSING OR INVALID TITLE The flight plan message has errors that cause the IFPS The correct syntax must be used
SYN92
system to be unable to identify the message TITLE
DUPLICATE DATA In an ADEXP format message for duplicate data in sets e.g. The correct syntax must be used
SYN91
a duplicate REF, GEO, REN etc.
SYN90 NO MERIDIAN ALLOWED IN FIELD The syntax for the geographical co-ordinate is not correct. The correct syntax must be used
SYN89 MISSING OR INVALID ADEXP ADDRESS Specific error for missing field in ADEXP format messages. The correct syntax must be used
SYN88 MISSING OR INVALID END KEYWORD Specific error for missing field in ADEXP format messages. The correct syntax must be used
SYN87 MISSING OR INVALID ETO Specific error for missing field in ADEXP format messages. The correct syntax must be used
MISSING OR INVALID SIGNIFICANT POINT Specific error for missing field in ADEXP format messages. The correct syntax must be used
SYN86
DESIGNATOR
SYN85 MISSING FIELD Wide range of applications.
MISSING OR INVALID LEVEL The expected level information in the flight plan message The correct syntax must be used
SYN84
cannot be identified.
MULTIPLE MATCHING LATITUDE FOUND IN An EET estimate using only a latitude as a referent point Where a route contains more than one geographical
ROUTE, CANNOT EXPAND PARALLEL has more than one route point indicating the same latitude. coordinate on the same latitude, any associated EET
SYN81
must contain the full geographical coordinates for that
estimate.
MULTIPLE MATCHING LONGITUDE FOUND IN An EET estimate using only a longitude as a referent point Where a route contains more than one geographical
ROUTE, CANNOT EXPAND MERIDIAN has more than one route point indicating the same coordinate on the same longitude, any associated EET
SYN80
longitude. must contain the full geographical coordinates for that
estimate.
NIL NOT EXPECTED The NIL indicator is not allowed for use in the indicated The NIL indicator may only be used in certain subfields
SYN79 (sub)field. where it is intended to cancel all existing data in that
subfield.
NO CHANGES ALLOWED IN KEY FIELD It is not possible to make changes to the indicated key field. It is not possible to make changes to the indicated key
field. Key fields may only be changed by cancelling the
SYN78 existing flight plan and re-filing with the new key field
data.
EXPECTED NUMERIC The syntax for the field that is identified in the error The correct syntax must be used
SYN77
message is not correct.
NO PARALLEL ALLOWED IN FIELD The syntax for the field that is identified in the error The correct syntax must be used
SYN76
message is not correct.
EXPECTED SSR EQUIPMENT DESIGNATOR No SSR equipment designator is found in Item 10. The SSR equipment must be given with one of the
SYN74
approved indicators.
SUSPECT INVALID FIELD It is suspected that there is a Field 18 Subfield after a Field If Field 19 subfields are present, they shall be included
SYN73
19 subfield. after Field 18 subfields.
SUSPECT TEXT TOO LONG The syntax for the field that is identified in the error The correct syntax must be used
SYN72
message is not correct.
SYN71 FIELD TEXT TOO LONG Wide range of applications.
SYN70 FIELD TEXT TOO SHORT Wide range of applications.

Amendment date: 15-Nov-2012 EDITION 16.1 ANNEX IFPS MAN 15

Edited & produced by EUROCONTROL
©2012 The European Organisation for the Safety of Air Navigation (EUROCONTROL)
 Error Class Error Text Reason Requirements
EXPECTED TIME DESIGNATOR NOT FOUND The indicated time designator is missing. Where a time designator is required, it must be
SYN69
included.
TOO MANY ADDRESSES ON LINE The maximum number of 7 AD line addresses has been Each line in the re-addressing function may contain a
SYN68 exceeded on the indicated line, or a following line has not maximum of 7 addresses; any more addresses should
been prefixed by the AD indicator. be carried on to a new 'AD' line.
TOO MANY ALTERNATE AERODROMES In an ADEXP format message if you specify 3 ALTRNT The correct syntax must be used
SYN67
fields you get this error.
ADDITIONAL DATA FOLLOWS TRUNCATION A remote letter 'T' has been identified in the route, indicating Where a route is truncated using the individual letter
SYN66 INDICATOR the truncation point of that route, but further route data has 'T', no further route items should be inserted.
been identified after that designator.
UNEXPECTED SEPARATOR A field separator (e.g. ‘/’) is incorrectly placed in the flight The correct syntax must be used
SYN65
plan message.
MISSING OR INVALID AIRCRAFT ID When the Aircraft ID in an ICAO message consists of invalid
SYN64
characters - e.g. ////
UNKNOWN ENTRY TYPE For RPL only. RPLs in a submission should have a + for
SYN63 new and - for a cancel. Other symbols in this position give
the error.
UNKNOWN OR UNEXPECTED FIELD The flight plan message has errors that cause the IFPS The correct syntax must be used
SYN62 system to be unable to distinguish between the expected
fields.
INVALID WAKE TURBULENCE CATEGORY The aircraft type is filed as ZZZZ and the wake turbulence Where an aircraft type is given as ZZZZ, the correct
SYN60
category given is not L, M or H. wake turbulence category must be given.
THE DCT SEGMENT {ARG1}..{ARG2} IS The specified direct route in the submitted flight plan is The specified direct route in the submitted flight plan is
ROUTE52 FORBIDDEN. RESTRICTION: {ARG3} defined as being not allowed. defined as being not allowed, an alternative routing is
required.
FPL PROCESSED AFTER ESTIMATED TIME Under certain circumstances, the DOF calculated by the FPLs should be submitted to IFPS before the EOBT.
OF ARRIVAL IFPS may be such that the Estimated Time of Arrival
EFPM51 (derived from the EOBT + calculated profile of the FPD) of
the flight is in the past when compared to the message
processing time in IFPS.
CLIMBING/DESCENDING OUTSIDE THE The profile of a flight has been calculated by the system to File where you fly!
VERTICAL LIMITS OF SEGMENT climb or descend on a route segment, mentioned in field 15,
PROF50
{ARG1/POINT_A} {ARG2/ROUTE} outside the defined vertical limits of the airway.
{ARG3/POINT_A}
THE POINT {ARG1} IS UNKNOWN IN THE A point is present in the given route that is regarded as The point should be replaced by either the correct
ROUTE49
CONTEXT OF THE ROUTE being illogical. point, or the geo coordinates of the given point.
THE {ARG1/SID_OR_STAR} {ARG2/TP1} IS There are only 2 terminal procedures available at this A correct TP must be used.
NOT VALID. {ARG3/TP2} IS SUGGESTED. aerodrome and the flight does not comply with the
ROUTE48 parameters of the terminal procedure indicated in the
message. The second terminal procedure is assumed by
the system.

Amendment date: 15-Nov-2012 EDITION 16.1 ANNEX IFPS MAN 16

Edited & produced by EUROCONTROL
©2012 The European Organisation for the Safety of Air Navigation (EUROCONTROL)
 Error Class Error Text
THE {ARG1/SID_OR_STAR} {ARG2/TP1} IS
ROUTE47 NOT VALID BECAUSE OF THE FLIGHT TYPE.
[{ARG3/RESTRICTION_ID}]
THE {ARG1/SID_OR_STAR} {ARG2/TP1} IS
ROUTE46 NOT VALID BECAUSE OF THE AIRCRAFT
TYPE. [{ARG3/RESTRICTION_ID}].
THE {ARG1/SID_OR_STAR} {ARG2/TP1} IS
ROUTE45 NOT VALID BECAUSE OF THE AIRCRAFT
EQUIPMENT. [{ARG3/RESTRICTION_ID}].
THE {ARG1/SID_OR_STAR} {ARG2/TP1} IS
ROUTE44 NOT VALID BECAUSE IT IS CLOSED.
THE {ARG1/SID_OR_STAR} {ARG2/TP1} IS
NOT VALID BECAUSE THE RFL IS BELOW MIN
ROUTE43
LEVEL ON {ARG3/LAST_OR_FIRST} SEGMENT
OF {ARG4/SID_OR_STAR}.
THE {ARG1/SID_OR_STAR} {ARG2/TP1} IS
ROUTE42 NOT VALID BECAUSE OF THE RUNWAY IN
USE.
ROUTE CONTAINS A SYSTEM GENERATED
ROUTE41
PORTION. PLEASE CHECK.
ACTUAL DATE AND TIME OF ARRIVAL IS NOT
WITHIN ACCEPTABLE RANGE: {ARG1/START}
EFPM40
TO {ARG2/END}.
ACTUAL DATE AND TIME OF DEPARTURE IS
NOT WITHIN ACCEPTABLE RANGE:
EFPM39
{ARG1/START} TO {ARG2/END}.
AFIL ETO IS NOT IN ACCEPTABLE RANGE:
EFPM38 {ARG1/START} TO {ARG2/END}
AFP ETO IS NOT IN ACCEPTABLE RANGE:
EFPM37 {ARG1/START} TO {ARG2/END}
FNM ETO IS NOT IN ACCEPTABLE RANGE:
EFPM36 {ARG1/START} TO {ARG2/END}
MFS ETO IS NOT IN ACCEPTABLE RANGE:
EFPM35 {ARG1/START} TO {ARG2/END}
AIRAC DATA NOT AVAILABLE
EFPM34
Amendment date: 15-Nov-2012 EDITION 16.1
©2012 The European Organisation for the Safety of Air Navigation (EUROCONTROL)
Reason Requirements
The given terminal procedure does not comply with A correct TP must be used.
requirement because of a flight type restriction, and no valid
terminal procedures exist to replace it.
The given terminal procedure does not comply with A correct TP must be used.
requirement because of an aircraft type restriction, and no
valid terminal procedures exist to replace it.
The given terminal procedure does not comply with A correct TP must be used.
requirement because of a Radio-Equipment restriction, and
no valid terminal procedures exist to replace it.
The given terminal procedure does not comply with A correct TP must be used.
requirement because of a terminal procedure closure, and
no valid terminal procedures exist to replace it.
The calculated levels of the flight do not comply with the A correct TP must be used.
mandatory level requirements of the given terminal
procedure, and no valid terminal procedures exist to replace
it.
The given terminal procedure does not comply with the A correct TP must be used.
runway in use, and no valid terminal procedures exist to
replace it.
Internal IFPS Error N/A
ARR messages are expected to provide an ATA within a The ATA must be within the acceptable range.
time window defined by a given time parameter before the
EOBT and the IFPS ‘close’ time of the associated flight. The
time parameter shall be set by default to 0 (zero).
DEP messages are expected to provide an ATD within a The ATD must be within the acceptable range.
given time window around the EOBT of the associated
flight. The time window shall be set by default to minus 60
minutes to plus 240 minutes around the EOBT.
FPL messages with ADEP=AFIL may be filed containing The time given for the estimate point should be within
any time value, even if that time value is remote when 1 hour of the current system time.
compared to system time.
AFP messages may be filed containing any time value, The time given for the estimate point should be within
even if that time value is remote when compared to system 1 hour of the current system time.
time.
FNM messages may be filed containing any time value, The time given for the estimate point should be within
even if that time value is remote when compared to system 1 hour of the current system time.
time.
MFS messages may be filed containing any time value, The time given for the estimate point should be within
even if that time value is remote when compared to system 1 hour of the current system time.
time.
The date of flight is outside the valid AIRAC data period. The flight plan message must be filed when the AIRAC
data is available.
ANNEX IFPS MAN 17
Edited & produced by EUROCONTROL
 Error Class Error Text Reason Requirements
MISSING ADEXP EQCST In an ADEXP format message if the ADEXP EQCST field is
SYN32
corrupt.
FLIGHT PLAN ALREADY LOCKED BY Internal IFPS Error N/A
EFPM31
ANOTHER USER
INVALID DCT {ARG1}..{ARG2}: The length of this DCT segment is greater than the Cross- The route must be changed.
({ARG3/DISTANCE} NM). DCT LONGER THAN border DCT limit defined for those adjacent NAS.
ROUTE30 ({ARG4/DISTANCE} NM) ARE NOT ALLOWED
TO CROSS THE BORDER BETWEEN {ARG5}
AND {ARG6}. [{ARG7/RESTRICTION_ID}]
FORBIDDEN TO CROSS THE BORDER This specific DCT segment is defined as NOT ALLOWED to A border crossing point is needed in the route of the
ROUTE29 BETWEEN {ARG1} AND {ARG2} ON DCT cross the boundaries of the two adjacent NAS. flight.
{ARG3}..{ARG4}. [{ARG5/RESTRICTION_ID}]

Amendment date: 15-Nov-2012 EDITION 16.1 ANNEX IFPS MAN 18

Edited & produced by EUROCONTROL
©2012 The European Organisation for the Safety of Air Navigation (EUROCONTROL)
 DOCUMENT FINAL PAGE

Amendment date: 15-Nov-2012 EDITION 16.1 ANNEX IFPS MAN 19

Edited & produced by EUROCONTROL
©2012 The European Organisation for the Safety of Air Navigation (EUROCONTROL)