annex generated errors

Transcription

NETWORK OPERATIONS HANDBOOK
EUROCONTROL
ANNEX TO THE IFPS USERS MANUAL
ANNEX to the IFPS USERS MANUAL
Generated Errors
Edition N°: 17.1
www.eurocontrol.int/lists/publications/network-operations-library
Amendment date: 29-Oct-2013
EDITION 17.1
ANNEX IFPS MAN
Edited & produced by EUROCONTROL
©2012 The European Organisation for the Safety of Air Navigation (EUROCONTROL)
i
©2013 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.
Edition Validity date
Reference
File name
Number of pages
:
:
:
:
:
17.1
29-Oct-2013
ANNEX TO THE IFPS USERS MANUAL
Generated Errors
19
EDITION 17.1
ANNEX IFPS MAN
ii
Error Class
EFPM309
RA307
ROUTE306
ROUTE305
ROUTE304
ROUTE303
ROUTE302
ROUTE301
RA282
RA281
RA280
RA279
RA278
RA276
RA275
Error Text
Reason
Requirements
It is not always possible to update a stored flight plan
when the flight has been activated.
MESSAGE ASSOCIATES TO
{ARG1/FLTSTATE} FLIGHT
The submitted message associates to a stored flight plan
that has been off block/activated/terminate/deleted in the
NM systems
FREEZE POINT {ARG1/POINT} NOT ON
FLIGHT ROUTE
CANNOT IDENTIFY {ARG1/ITEM_A} POINT IN
THE ROUTE
ROUTE CONTAINS A SYSTEM GENERATED
PORTION AND FLIGHT TYPE IS MILITARY.
PLEASE CHECK.
CANNOT AUTOMATICALLY GENERATE
ROUTE WITH VFR OR OAT PORTION
NO VALID ROUTE FOUND TO CONNECT TO
FLIGHT ROUTE.
CANNOT AUTOMATICALLY GENERATE
ROUTE WITH IFPSTOP PORTION.
NO VALID CONNECTION POINT FOUND ON
FLIGHT PLAN ROUTE.
THE AVOID POINT AND VIA POINT CANNOT
BE THE SAME
NUMBER OF CONSTRAINTS FOR ROUTE
GENERATION EXCEEDS {ARG1/NUMBER}
DUPLICATE KEYWORD {ARG1/KEYWORD} IN
ROUTE GENERATION PARAMETERS
ROUTE ENTIRELY FROZEN. NO ROUTE
GENERATION POSSIBLE
CANNOT FREEZE FROM/TO {ARG1/POINT}
Errors given when using the route proposals tool in the NOP
Portal or via B2B.
Internal IFPS Error
N/A
Internal IFPS Error
N/A
Internal IFPS Error
N/A
Internal IFPS Error
N/A
Internal IFPS Error
N/A
Internal IFPS Error
N/A
INVALID RFL
INVALID SPEED
/NBROUTE ARGUMENT INVALID
Portal or via B2B.
Portal or via B2B.
Portal or via B2B.
Portal or via B2B.
Portal or via B2B.
Portal or via B2B.
Portal or via B2B.
Portal or via B2B.
RA274
RA273
RA272
AERODROMES TOO CLOSE TO EACH OTHER
AERODROME OF DESTINATION DOES NOT
EXIST IN ENV DATABASE
EDITION 17.1
The error is given if the user requests an invalid number of
routes - e.g. 0
Portal or via B2B.
Portal or via B2B.
ANNEX IFPS MAN
3
Error Class
RA271
RA270
RA269
RA268
EFPM250
EFPM249
EFPM248
EFPM247
Error Text
Reason
AERODROME OF DEPARTURE DOES NOT
UNKNOWN AIRCRAFT TYPE
AIRSPACE {ARG1/AIRSPACE} DOES NOT
POINT {ARG1/POINT} DOES NOT EXIST IN
ENV DATABASE
ACTUAL DATE AND TIME OF ARRIVAL IS NOT
WITHIN ACCEPTABLE RANGE, AFTER
RECEPTION TIME.
ACTUAL DATE AND TIME OF DEPARTURE IS
NOT WITHIN ACCEPTABLE RANGE, AFTER
RECEPTION TIME.
AERODROME IS ZZZZ BUT {ARG1} IS NOT
PRESENT
ALTERNATE AERODROME IS ZZZZ BUT ALTN
INFO IS NOT PRESENT
The filed departure time is more than 10 minutes in the
future, when compared to the current system time.
Where a DEP message is received, the departure time
should not be in the future.
Wide range of applications.
Where an unclassified alternate aerodrome is
indicated as ZZZZ in Item 16c, it is necessary to
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
Item 18.
Where a known ICAO aircraft type designator is used
in F9, the F18 TYP/ subfield should not also be used.
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
TYP is also present or a message containing TYP/NIL has
been submitted that has not replaced the Item 9 ZZZZ with
a known aircraft type designator.
Where a known ICAO type designator is used in Item
9, the Item 18 sub-field TYP should not also be used.
Any further details should be included in the sub-field
RMK.
AIRCRAFT TYPE IS ZZZZ BUT {ARG1} IS NOT
PRESENT
The aircraft type is given in Item 9, but the Item 18 sub-field
TYP is also present or a message containing TYP/NIL has
been submitted that has not replaced the Item 9 ZZZZ with
a known aircraft type designator.
Where a known ICAO type designator is used in Item
9, the Item 18 sub-field TYP should not also be used.
Any further details should be included in the sub-field
RMK.
Z PRESENT BUT COM/DAT/NAV ABSENT
(CEQPT)
Field 10a contains Z, but no explanation is given in either
the COM,NAV or DAT sub-fields in field 18.
Field 10a contains R, but no PBN/ is given in field 18.
Either remove the Z from field 10a or add a COM,
NAV or DAT/ sub-field in field 18.
EFPM244
EFPM166
Where an ARR message is filed, the arrival time
should not be in the future.
Item 16c contains ZZZZ but no ALTN indicator is present in
Item 18.
EFPM245
EFPM243
Requirements
Portal or via B2B.
Portal or via B2B.
Portal or via B2B.
Portal or via B2B.
The filed arrival time is more than 10 minutes in the future,
when compared to the current system time.
R PRESENT BUT PBN ABSENT (CEQPT)
EFPM166
EDITION 17.1
Where R is used in the equipment designators of a flight
plan, it is necessary to specify the performance based
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.
ANNEX IFPS MAN
4
Error Class
Error Text
Reason
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
(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
specified in item 10a.
A performance based navigation level is achieved by
the carriage of certain equipment. Some equipment(s)
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}
{ARG2}
In RPL - if a from date is later than a to date or if the period
of operation is not within the activation period for a given
RPL
EFPM166
EFPM167
EFPM240
EFPM238
Requirements
PBN PRESENT BUT R ABSENT (CEQPT)
MESSAGE FILED BEFORE MATCHING FILED
FLIGHT PLAN
MESSAGE MATCHES EXISTING INVALID
MESSAGES
In IFPS when an ARR message has an ATA that is earlier
than the ATD.
The message has a filing time earlier than that of an
existing flight plan.
The message associates with another message that has
failed automatic processing and is awaiting or undergoing
manual treatment by the IFPS staff.
EFPM237
EDITION 17.1
The IFPS shall treat all associated messages in order
of filing time.
Where any message fails automatic processing and is
moved to the manual treatment queue, all subsequent
associated messages shall be linked to that invalid
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.
ANNEX IFPS MAN
5
Error Class
Error Text
Reason
Requirements
ESTIMATED OFF BLOCK DATE AND TIME NOT
IN THE ACCEPTABLE RANGE: {ARG1/START}
TO {ARG2/END}
For a FPL the filed EOBT and DOF is more than 30 minutes
in the past, or more than 120 hours (5 days) in the future,
when compared to current system time.
For DLA messages and CHG messages updating an
existing EOBT to be accepted by the IFPS, the new
EOBT must not be less than the IFPS time at the time
of processing, or not more than 20 hours in advance of
the IFPS time at the time of processing.
For a DLA or CHG the filed EOBT and DOF is more than 0
minutes in the past, or more than 20 hours in the future,
when compared to current system time.
EFPM236
For FPL messages containing a DOF, the IFPS may
accept messages with an EOBT up to 12 hours in the
past, and up to 120 hours (5 days) in advance of the
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
MESSAGE
Check that the TITLE of the message is correct and
that unnecessary field have not been included in the
submitted message.
ESTIMATED OFF BLOCK DATE AND TIME IS
NOT WITHIN ACCEPTABLE RANGE, AFTER
FILING TIME.
The field that is specified in the error message is not
expected for the type of message submitted (e.g. EST
DATA in a FPL).
The filed DOF is more than 30 minutes in the past, or more
than 120 hours (5 days) in the future, when compared to
current system time.
EFPM233
FLIGHT PLAN ALREADY GENERATED FROM
RPL DATA
A flight plan matching the submitted message has already
been generated from RPL data.
To submit a FPL, the flight that was generated from
RPL data must first be cancelled.
EFPM232
FLIGHT PLAN ALREADY RECEIVED FROM
ADDRESS {ARG1}
A flight plan matching the submitted message has already
been received from the indicated address.
The same flight plan has already been received and
accepted by IFPS from the given address.
EFPM231
CIVIL FORMATION FLIGHT NOT PERMITTED
IN EUR RVSM AIRSPACE
In the submitted message, the flight type is not given as M,
and the number of aircraft indicated is more than 1.
Within the EUR RVSM airspace, formation flights are
only allowed for military flights.
EFPM230
ASSOCIATION NO LONGER VALID THE FPD IS
CLOSED
Fpd Closed would be raised if whilst processing an
associated message - an FPD became closed.
EFPM235
EFPM234
EDITION 17.1
For DLA and CHG messages updating an existing
EOBT to be accepted by the IFPS, the new EOBT
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 120 hours (5 days) in advance of the 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 system time,
with the appropriate DOF being inserted automatically
by the IFPS.
ANNEX IFPS MAN
6
Error Class
Error Text
Reason
Requirements
EFPM228
INVALID VALUE {ARG1}
When the ETO in an AFIL messages is in an incorrect
format.
EFPM227
MANUAL ADDRESSING REQUIRED. PRESS
APPLY TO CONTINUE
An internal check for the IFPS staff to add any addresses
following the use of IFPSTO/IFPSTART.
THIS {ARG1/TITLE} MESSAGE ASSOCIATES
WITH THE FPD: {ARG2/KEYS}
MISSING OR ERRONEOUS FIELD
Internal IFPS error for when an APL message created from
FNM/MFS/AFP partially associates with an existing FPD.
MESSAGE MATCHES MULTIPLE FLIGHT
PLANS
The IFPS holds more than one valid flight plan with which
the invalid message may match.
Where there is more than one matching flight plan is
held in the IFPS, the correct message association may
be increased in accuracy by adding the EOBT and
DOF of the submitted message.
EOBT IN THE PAST COMPARED TO IFPS
SYSTEM TIME: {ARG1}
At the time of processing, the EOBT in the submitted
message is in the past compared to the IFPS system time.
The IFPS shall only accept those messages that
indicate an EOBT that is not in the past when
compared to the IFPS system time at the time of
processing that message.
NO EXISTING FILED FLIGHT PLAN MATCHES
THIS MESSAGE
The IFPS does not hold a valid flight plan that matches the
key fields indicated in the submitted message.
The referent flight plan may or may not have been
filed; it may have been cancelled or closed by another
party, or the key fields in the submitted message do
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
RVSM AIRSPACE
In the submitted message, the flight rules are not M, the
equipment does not contain W, and STS/NONRVSM is not
found in Item 18.
Flights within the EUR RVSM airspace are required to
be suitably equipped (Item 10 includes 'W') or to be a
military flight (Item 8 flight type is 'M') or the exempted
(STS/NONRVSM in Item 18).
FPL WITH SAME ARC_ID AND OVERLAPPING
FLYING PERIOD EXISTS:{ARG1}
A valid flight plan exists in the IFPS with a given total flying
time that overlaps with that given in the submitted message.
The IFPS cannot accept a flight plan that has the
same callsign and a flying time, based on the EOBT
and total estimated elapsed flying time, that overlaps
with an existing valid flight plan.
POSSIBLE DOF SUBFIELD WITH WRONG
SYNTAX DETECTED IN FIELD18.
A possible incorrectly formatted DOF has been identified in
the flight plan.
The IFPS shall check for a DOF in the correct format
of DOF/YYMMDD. The IFPS shall also check for any
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
ACCESS.
The requested flight plan is not available for unauthorised
access.
The requested flight plan has been classified as
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
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
messaged (e.g. MFS message).
EFPM229
EFPM226
EFPM225
EFPM224
EFPM223
INVALID FORMAT
EFPM220
EFPM219
EFPM217
EFPM216
EFPM215
EFPM214
EFPM213
EDITION 17.1
The correct format must be used.
Following the insertion of IFPSTOP/IFPSTART but the
IFPS staff, it may be necessary for them to manually
add extra distribution addresses.
ANNEX IFPS MAN
7
Error Class
EFPM212
EFPM211
EFPM210
EFPM209
PROF206
PROF205
PROF204
PROF203
PROF202
PROF201
Error Text
Reason
Requirements
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.
Within the EUR RVSM airspace, State formation
flights shall not include W in Item 10, but must include
STS/NONRVSM in Item 18.
THE DCT SEGMENT <Point A> .. <Point B> IS
NOT AVAILABLE IN FL RANGE <FL_Range>
(UNAVAILABLE ROUTE <ROUTE ID>)
The indicated DCT route is co-located with an airway
which is not available at the at the requested flight level
filed and the system is unable to connect the two points via
an airway.
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.
RS: TRAFFIC VIA <Ref_Loc_Id> IS OFF
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
<Ref_Loc_Id>:<FL_Range>
[<DDHHMM..DDHHMM>] IS ON FORBIDDEN
ROUTE REF: <Restriction Id> <Textual
Description>
PROFILE ANALYSIS STOPPED
The route detailed in the submitted message does not
comply with the specified mandatory RAD route.
The filed route must comply with all relevant RAD
restrictions.
The route detailed in the message follows the listed
forbidden RAD route.
restrictions.
The system is unable to continue creating a profile for the
flight.
Ensure that all information in the message is accurate.
{ARG1/POINT1} {ARG2/ROUTE}
{ARG3/POINT2} IS NOT AVAILABLE IN FL
RANGE {ARG4/FL_RANGE}
The flight has been calculated to fly on a closed CDR-0.
CANNOT CLIMB OR DESCEND ON <Point>
<Route> <Point> IN FL
RANGE <FL_Range> BECAUSE OF
UNAVAILABLE LEVELS ON <Route_List>
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.
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.
FIELDS 10 AND/OR 18 INCORRECT FOR
STATE FORMATION FLIGHT IN EUR RVSM
AIRSPACE
STS/NONRVSM IS REQUIRED FOR NON
RVSM APPROVED STATE FLIGHT
NON RVSM APPROVED FLIGHT WITHIN EUR
RVSM AIRSPACE AND STS/NONRVSM IS NOT
EXPECTED FOR A CIVIL AIRCRAFT
STS/NONRVSM IS NOT EXPECTED FOR AN
RVSM APPROVED FLIGHT WITHIN EUR RVSM
AIRSPACE
EDITION 17.1
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.
ANNEX IFPS MAN
8
Error Class
Error Text
Reason
The given route segment is classified as unavailable CDR1
at the calculated time of use by this flight.
<Point> <Route> <Point> IS A CLOSED CDR_2
IN FL RANGE <FL_Range>
<Point> <Route> <Point> IS A CDR_3 IN FL
RANGE <FL_Range>
RS: CLOSED AT: REF: UNTI: BETWEEN:
<Point> <Route> <Point> DOES NOT EXIST IN
FL RANGE <FL_RANGE>
The route detailed in the submitted message follows the
listed closed RAD route.
The given route does not exist at the requested flight level
between the indicated points.
restrictions.
against the published existence for that part of that
route at that time
(Point> <Route> <Point> IS NOT AVAILABLE IN
FL RANGE <FL_Range>
The given route is classified as unavailable at the requested
flight level between the indicated points.
PROF200
PROF199
PROF198
PROF197
PROF195
PROF194
PROF193
IFR OPERATIONS AT AERODROME
{ARG1/AERODROME} ARE NOT PERMITTED
[{ARG2/RESTRICTION_ID}]
TOTAL STAY TIME GREATER THAN TOTAL
ESTIMATED ELAPSED TIME.
PROF192
PROF191
Requirements
<Point> <Route> <Point> IS A CLOSED CDR_1
IN FL RANGE <FL_Range>
TTL_EET DIFFERENCE > (value) %,
CALCULATED TTL_EET <ADEP> FROM TO
<ADES>= <Time> (HHMM)
EDITION 17.1
The departure/destination aerodrome cannot be accessed
under IFR rules
The flight should be filed with a VFR segment.
The submitted message contains an en-route STAY
indicator with a time greater than the total estimated
elapsed time indicated in Item 16b.
The IFPS shall check the given EET for a submitted
flight plan, and where a STAY indicator is used in the
route, the associated time is also checked. Where the
STAY time is incompatible with the calculated total
EET (including its accepted percentage error), an error
is generated.
The total EET given is greater than the accepted maximum
calculated by the IFPS for this trajectory.
The IFPS shall calculate a total estimated flying time
for all flight plans, based on the speed(s) and flight
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.
ANNEX IFPS MAN
9
Error Class
PROF190
PROF189
PROF188
ROUTE180
ROUTE179
ROUTE178
ROUTE176
ROUTE175
Error Text
Reason
The submitted flight plan does not indicate that the flight
does not carry the necessary equipage to enter 8.33kHz
airspace.
The indicated sector(s) require that all flights intending
to use that airspace carry either 8.33kHz equipage (Y
in Item 10) or UHF (U in Item 10), but the submitted
message contains neither.
NON 8.33 BUT UHF EQUIPPED AIRCRAFT IN
8.33 AIRSPACE NOT HANDLING UHF
The indicated equipment contains U, but the flight is
calculated to enter a sector(s) that requires Y equipage.
The indicated sector(s) require that all flights intending
to use that airspace carry the full 8.33kHz equipage (Y
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
CARRIAGE REQUIREMENTS
The flight does not comply with those mandatory conditions
associated with the IFPZ 8.33kHz airspace.
The flight must be compliant with all 8.33kHz
conditions in Items 10, 15 & 18 when that flight is
planned to enter the IFPZ 8.33kHz airspace.
ROUTE ANALYSIS HAS ABORTED
CRUISING FLIGHT LEVEL INVALID OR
INCOMPATIBLE WITH AIRCRAFT
PERFORMANCE
The filed cruising flight level is either incorrect or beyond the
known performance of the filed aircraft type.
CRUISING SPEED IS INVALID OR
PERFORMANCE
The filed cruising speed is either incorrect or beyond the
known performance of the filed aircraft type.
The IFPS holds a performance table for each aircraft
type that includes the maximum known speeds at
certain flight levels attainable for that type. Where the
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
PERFORMANCE
The flight level filed at the given point is either incorrect or
beyond the known performance of the filed aircraft type.
type that includes the maximum known flight level
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
PERFORMANCE
The speed filed at the given point is either incorrect or
beyond the known performance of the filed aircraft type.
type that includes the maximum known speeds at
certain flight levels attainable for that type. Where the
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
incorrectly formatted or is greater than the total EET for that
flight.
The time given for an EET point must be less than the
total EET for the flight in Item 16b and greater than
zero.
MULTIPLE ROUTES BETWEEN AND .
POSSIBLE ROUTES ARE:
More than one available route exists between the indicated
points.
Several possible routes exist between the indicated
points and the appropriate one should be specified.
CANNOT EXPAND THE ROUTE
The flight has been calculated to transit an artificial route
segment (GAP).
Such a route segment cannot be used; an alternative
route must be used instead.
ROUTE174
ROUTE172
ROUTE171
Requirements
NON 8.33 AND NON UHF EQUIPPED
AIRCRAFT IN 8.33 AIRSPACE
EDITION 17.1
type that includes the maximum known flight level
attainable for that type. Where the filed cruising flight
level is either incorrect or beyond the known
performance of the filed aircraft type, an error is
generated.
ANNEX IFPS MAN
10
Error Class
ROUTE170
ROUTE169
ROUTE168
ROUTE165
ROUTE162
ROUTE162
ROUTE161
ROUTE159
ROUTE158
ROUTE157
ROUTE155
Error Text
Reason
The IFPS is unable to automatically determine the IFPZ
entry or exit point of the flight.
An IFPZ entry or exit point should be included in the
route.
CONSECUTIVE STAY INDICATORS NOT
ALLOWED
Consecutive STAY indicators have been found associated
with the same point.
Each STAY indicator must have a point before and
after that STAY information. It is not possible to have
consecutive STAY indicators at the same point.
INVALID DCT. DCT ARE NOT ALLOWED TO
CROSS THE BORDER BETWEEN AND
The specified DCT routing is not allowed as it crosses the
indicated FIR border.
THE DCT SEGMENT : NM IS TOO LONG FOR
MAXIMUM IS: NM
The portion of the specified DCT segment within the limits
of an FIR exceeds the ‘en-route DCT limit’ for that FIR and
the system is unable to connect the two points via an
airway.
Each FIR may specify whether or not it will allow DCT
routings across its border, so the specified DCT
routing is not allowed as it crosses the indicated FIR
border.
The specified direct route in the submitted flight plan
exceeds the given maximum for the indicated
airspace, so an available route using the ATS route
structure is required for this segment.
THE POINT FROM ESTIMATE DATA IS NOT IN
THE FLIGHT ROUTE
An estimate is given in Item 18 for a point not on the filed
route.
IFPS will compare any estimate points given in Item 18
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
FLIGHT ROUTE
A point specified in the DLE indicator is not on the route.
THIS FIELD VALUE IS INCONSISTENT WITH
THE FLIGHT RULES.
The flight rules are Y or Z, but the IFPS is unable to identify
conditions within Item 15 that are consistent with the given
flight rules.
The level indication at the RVSM entry/exit point does not
correspond to the correct cruise level for that route.
The level indication at the RVSM entry/exit point and/or the
RVSM entry/exit point has not been included in the
submitted route, or if there is an invalid route given
immediately after the RVSM entry/exit point.
The flight rules have been submitted as IFR only, but a
change to VFR is indicated at a point in the route.
A point specified in the DLE indicator shall be explicitly
or implicitly present on the flight route.
The flight rules and any changes thereto in Item 15
must correspond.
If a change to VFR is intended, then the flight rules
should be given as Y (IFR then VFR).
MULTIPLE JUNCTIONS BETWEEN AND.
More than one possible junction point exists between the
indicated airways.
A specific point must be given at the junction between
two airways.
FLIGHT NOT APPLICABLE TO IFPS
The submitted message gives no indication of an IFR or
GAT portion of that flight within the IFPZ.
THE POINT CANNOT BE USED TO LEAVE OR
JOIN THE TP
The indicated point is not the first point of a STAR or the
last point of a SID, and may not be used to connect into or
out of the terminal procedure.
Those flights planning to operate within the IFPZ must
have at least an identifiable IFR/GAT portion within the
IFPZ.
Where a terminal procedure is used in a route, that
procedure must be followed to the last point if a
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
level is unrecognisable.
The cruising flight level must be indicated in Item 15.
MISSING DESIGNATOR
When there is a missing point in an EET or DLE field.
All required fields must be present in submitted
messages.
INVALID RFL AT EUR RVSM AIRSPACE
ENTRY/EXIT
INVALID EUR RVSM AIRSPACE ENTRY/EXIT
CONDITION
FLIGHT RULES I WITH VFR PART.
ROUTE152
ROUTE151
ROUTE150
ROUTE149
Requirements
CANNOT FIND ENTRY/EXIT POINT ON
{ARG1/ROUTE}
EDITION 17.1
The level indicated at the RVSM entry/exit point must
comply with the RVSM levels published for that route.
It is required to indicate the speed and level at the
EUR RVSM entry/exit point, and a valid route
immediately after the RVSM entry/exit point.
ANNEX IFPS MAN
11
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
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
system.
The North Atlantic tracks for that period must be valid
in the IFPS.
A POINT IS EXPECTED AFTER A STAY
INDICATOR
A STAY indicator has been filed without the required point
before and after the indicator.
The STAY indicator is preceded by the point at which
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.
A POINT DESIGNATOR IS EXPECTED
BEFORE {ARG1/ITEM}
For an AFIL FPL, the first point in the route is an airway.
Where two consecutive points are filed in a route, the
IFPS can only automatically process them when a
valid available route exists between them.
The route must not start with an unknown navigation
beacon, an airway, a DCT or any designator other
than a known ICAO designator for a navigation
beacon, a navigation beacon with bearing/range, or a
set of geographical coordinates.
ROUTE141
THE POINT {ARG1} IS NOT ON THE ROUTE
{ARG2}
The indicated point is not part of the given route.
Any point filed as part of a route must be recognised
as being associated with that route.
ROUTE140
IS FOLLOWED BY WHICH IS NOT ONE OF ITS
POINTS
The indicated point is not published as a part of the given
route.
as being associated with that route.
ROUTE139
IS PRECEDED BY WHICH IS NOT ONE OF ITS
POINTS
The indicated point is not published as a part of the given
route.
as being associated with that route
ROUTE138
CANNOT HAVE A ROUTE BETWEEN THE
SAME POINT; ROUTE: , POINT:
It is not possible to file a route from a point to that same
point.
THE SID LIMIT IS EXCEEDED FOR
AERODROME CONNECTING TO
No known departure procedure exists between the
aerodrome and the specified first point of the route, and the
direct distance exceeds the maximum allowed for
departures at that aerodrome.
The filed route must ensure that the point - route –
point sequence is correct and progressive.
There is no known departure procedure that exists to
connect the aerodrome to the specified first point of
the route, and the direct distance exceeds the
maximum allowed for departures at that aerodrome.
THE STAR LIMIT IS EXCEEDED FOR
AERODROME CONNECTING TO
No known arrival procedure exists between the aerodrome
and the specified last point of the route, and the direct
distance exceeds the maximum allowed for arrivals at that
aerodrome.
Where an arrival procedure exists, it should be used to
connect the route to the arrival aerodrome. Where no
known arrival procedure exists, the distance from the
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
PERMITTED FOR A FLIGHT GOING OUT OF
THE IFPZ
THE <sid or star> IS NOT VALID. <sid or star> IS
SUGGESTED. OTHER POSSIBLE TPS VIA
<List_Of_Points> ARE <TP>
A STAY indicator has been used for a flight that intends to
operate outside the IFPZ as well as inside.
The STAY indicator is only permitted for use with
those flights that remain entirely within the IFPZ.
There are several terminal procedures available at this
aerodrome and the flight does not comply with the
parameters of the terminal procedure indicated in the
message. The first compliant terminal procedure is
assumed by the system. Other possibilities are presented to
the IFPS staff.
A correct TP must be used.
ROUTE148
ROUTE147
ROUTE145
ROUTE144
ROUTE143
ROUTE135
ROUTE134
ROUTE133
ROUTE132
EDITION 17.1
ANNEX IFPS MAN
12
Error Class
ROUTE131
ROUTE130
Error Text
Reason
TRUNCATED ROUTE
The route as filed has been truncated and is therefore
incomplete.
UNKNOWN DESIGNATOR {ARG1}
INSUFFICIENT DATA TO RESOLVE
HOMONYM AT {ARG1/POINT}
This error is reported when a point that is present in the
route field is stored more than once in the NM Environment
database. Due to the proximity of the points associated with
the trajectory of the flight, IFPS cannot determine which of
the points to use.
The submitted message indicates that the flight intends to
change to VFR in or above RVSM airspace.
ROUTE129
ROUTE128
VFR NOT PERMITTED IN OR ABOVE EUR
RVSM AIRSPACE
ROUTE127
FLIGHT RULES V WITH IFR PART.
The VFR indicator should be given in the route to
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
given in the route.
The IFR indicator should be given in the route to
indicate at which point the flight intends to change to
IFR.
INVALID COMBINATION OF MODE S
CAPABILITY AT ROW=x, COL=y
The Mode S indication is not unique or ADS-B & ADS-C is
notified without any transponder mode indicated (A, C or S).
When the aircraft is equipped with Mode S surveillance,
being ‘I’,’P’,’X’, only one descriptor is allowed and when
either E,H,L, S is present it excludes I, P and X. Also, the
indication of ADS-B or C shall not be present without any
transponder mode (A, C or S).
INCONSISTENT WITH ASSOCIATED
FLIGHTPLAN FORMAT (OLD: <field name(s)>)
(NEW: <field name(s)>)
The message associates with a flight plan. The stored flight
plan is in new format and the associated message
is in old format or vice versa and there is inconsistent data
in these 2 messages.
When the CHGRUL field has been incorrectly defined.
No communication or navigation equipment indicators are
given in Item 10.
An old format flight plan may be updated by a new
format message and vice versa provided the end
result of the processing is a fully consistent flight plan
either old or new.
EXPECTED DATE DESIGNATOR NOT FOUND
The format of the DOF field is not correct.
Always ensure that the FOF field is submitted in the
correct format and that only one ‘/’ separator is used.
DUPLICATE ERROR AT ROW=x, COL=y (subfield name)
There is a duplicate sub-field indicator which is not allowed.
The following sub-field indicators DEP/,DEST, DOF/,
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
FPL
A syntax error is causing IFPS to be unable to find the end
of the submitted message.
The flight rules are either missing or using an invalid
designator.
SYN153
SYN123
SYN122
SYN121
SYN119
SYN118
SYN117
SYN116
VFR at or above F290 is not permitted in the EUR
RVSM airspace.
The flight rules are Y (IFR then VFR), but no VFR indicator
is given in the route.
ROUTE125
SYN124
The message should be submitted with the point name
replaced with the geographical coordinates of the
point.
FLIGHT RULES Y WITH NO VFR PART.
ROUTE126
SYN136
Requirements
The message should be submitted with the complete
route.
MISSING OR INVALID CHANGE RULES
EXPECTED CNA EQUIPMENT DESIGNATOR
EXPECTED END OF MESSAGE
MISSING OR INVALID FLIGHT RULES
MISSING OR INVALID FLIGHT TYPE
EDITION 17.1
The flight type is either missing or using an invalid
designator.
A minimum of 1 communication or navigation
equipment indicator must be given in Item 10.
The correct syntax must be used
The flight rules must be present, and must use an
approved indicator.
The flight type must be present, and must use an
approved indicator.
ANNEX IFPS MAN
13
Error Class
SYN115
SYN114
SYN113
Error Text
Reason
The flight type and flight rules are either missing or using an
invalid designator.
The flight type and flight rules must be present, and
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
must be present in the submitted message.
INVALID MESSAGE LENGTH
This is an RPL only error - when a line exceeds the allowed
length.
INCORRECT USAGE OF BRACKETS '(' AND ')'
The submitted message contains more brackets than just
the opening and closing '(' and ').
The opening and closing indicators of any message
are '(' and ')' respectively, thus they cannot be used
within a message in any way.
MISPLACED INDICATOR. MUST BE AFTER A
POINT
An indicator (VFR, IFR, GAT, OAT, etc.) in the route field
does not follow a point.
An change of rules, flight type, etc must be put in the
route field after a point designator.
INVALID BEARING DESIGNATOR
The indicated bearing designator is outside the range 000 to
360.
One or more invalid characters used in the text.
Any bearing indication must reflect to a maximum
value of 360º.
Ensure only valid characters are used in the text.
For an invalid date - e.g. an Alphabetic character in the
DOF
In an ADEXP format message for a badly formed distance
field in a reference (REF) point.
One or more invalid characters used in the text.
SYN112
SYN111
SYN110
SYN109
SYN108
SYN105
SYN104
FIELD CONTAINS INVALID CHARACTER(S)
INVALID DATE DESIGNATOR
INVALID DISTANCE DESIGNATOR
INVALID FIELD
SYN101
SYN98
Where more than one STAY indicator is used in the
route, each indicator must have a separate and
consecutive sequence number, to a maximum value of
9.
INVALID LATITUDE DESIGNATOR
The indicated latitude value does not contain either 2 or 4
numbers.
The IFPS can only accept latitude values given as
either 2 or 4 numbers.
INVALID LEVEL DESIGNATOR
Incorrect syntax for the speed/level group has been used.
INVALID LIST
In an ADEXP format message when you have a -BEGIN
followed by an unexpected keyword - i.e. one that isn't
ADDR, RTE_PTS, EQCST
The indicated longitude value does not contain either 3 or 5
numbers.
The level indication must use the correct format.
INVALID LONGITUDE DESIGNATOR
INVALID POINT
In an ADEXP format message for problems with points in
fields e.g. missing PTID in a REF point.
The flight plan message has errors that cause the IFPS
system to be unable to distinguish between the expected
fields.
The SRC field in the flight plan message is not correct.
Incorrect syntax for the speed/level group has been used.
INVALID SEPARATOR
SYN97
SYN96
SYN95
SYN93
Ensure only valid characters are used in the text.
Multiple STAY indicators with the same sequence number
have been used in Item 15.
SYN100
SYN99
INVALID ID USED IN FIELD {ARG1/FIELD}
SYN103
SYN102
Requirements
EXPECTED FLIGHT TYPE AND RULES
INVALID SOURCE
INVALID SPEED DESIGNATOR
INVALID TIME DESIGNATOR
The indicated time designator does not conform with the
standard 24-hour format.
EDITION 17.1
The IFPS can only accept latitude values given as
either 3 ot 5 numbers.
The SRC field should not be sent to IFPS.
ANNEX IFPS MAN
14
Error Class
SYN92
SYN91
SYN90
SYN89
SYN88
SYN87
SYN86
SYN85
SYN84
SYN81
SYN80
Error Text
Reason
MISSING OR INVALID TITLE
DUPLICATE DATA
NO MERIDIAN ALLOWED IN FIELD
MISSING OR INVALID ADEXP ADDRESS
MISSING OR INVALID END KEYWORD
MISSING OR INVALID ETO
MISSING OR INVALID SIGNIFICANT POINT
DESIGNATOR
MISSING FIELD
MISSING OR INVALID LEVEL
MULTIPLE MATCHING LATITUDE FOUND IN
ROUTE, CANNOT EXPAND PARALLEL
Specific error for missing field in ADEXP format messages.
SYN74
SYN73
SYN72
SYN71
SYN70
The expected level information in the flight plan message
cannot be identified.
An EET estimate using only a latitude as a referent point
has more than one route point indicating the same latitude.
Where a route contains more than one geographical
coordinate on the same latitude, any associated EET
must contain the full geographical coordinates for that
estimate.
Where a route contains more than one geographical
coordinate on the same longitude, any associated EET
must contain the full geographical coordinates for that
estimate.
An EET estimate using only a longitude as a referent point
has more than one route point indicating the same
longitude.
NIL NOT EXPECTED
The NIL indicator is not allowed for use in the indicated
(sub)field.
The NIL indicator may only be used in certain subfields
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
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
message is not correct.
No SSR equipment designator is found in Item 10.
SYN78
SYN76
MULTIPLE MATCHING LONGITUDE FOUND IN
ROUTE, CANNOT EXPAND MERIDIAN
SYN79
SYN77
Requirements
system to be unable to identify the message TITLE
In an ADEXP format message for duplicate data in sets e.g.
a duplicate REF, GEO, REN etc.
The syntax for the geographical co-ordinate is not correct.
NO PARALLEL ALLOWED IN FIELD
EXPECTED SSR EQUIPMENT DESIGNATOR
The SSR equipment must be given with one of the
approved indicators.
SUSPECT INVALID FIELD
It is suspected that there is a Field 18 Subfield after a Field
19 subfield.
If Field 19 subfields are present, they shall be included
after Field 18 subfields.
SUSPECT TEXT TOO LONG
FIELD TEXT TOO LONG
FIELD TEXT TOO SHORT
EDITION 17.1
ANNEX IFPS MAN
15
Error Class
SYN69
Error Text
Reason
EXPECTED TIME DESIGNATOR NOT FOUND
The indicated time designator is missing.
TOO MANY ADDRESSES ON LINE
The maximum number of 7 AD line addresses has been
exceeded on the indicated line, or a following line has not
been prefixed by the AD indicator.
TOO MANY ALTERNATE AERODROMES
In an ADEXP format message if you specify 3 ALTRNT
fields you get this error.
A remote letter 'T' has been identified in the route, indicating
the truncation point of that route, but further route data has
been identified after that designator.
A field separator (e.g. ‘/’) is incorrectly placed in the flight
plan message.
When the Aircraft ID in an ICAO message consists of invalid
characters - e.g. ////
For RPL only. RPLs in a submission should have a + for
new and - for a cancel. Other symbols in this position give
the error.
system to be unable to distinguish between the expected
fields.
The aircraft type is filed as ZZZZ and the wake turbulence
category given is not L, M or H.
SYN68
SYN67
SYN66
SYN65
SYN64
ADDITIONAL DATA FOLLOWS TRUNCATION
INDICATOR
UNEXPECTED SEPARATOR
MISSING OR INVALID AIRCRAFT ID
UNKNOWN ENTRY TYPE
SYN63
UNKNOWN OR UNEXPECTED FIELD
SYN62
SYN60
ROUTE52
INVALID WAKE TURBULENCE CATEGORY
THE DCT SEGMENT {ARG1}..{ARG2} IS
FORBIDDEN. RESTRICTION: {ARG3}
defined as being not allowed.
FPL PROCESSED AFTER ESTIMATED TIME
OF ARRIVAL
Under certain circumstances, the DOF calculated by the
IFPS may be such that the Estimated Time of Arrival
(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.
The profile of a flight has been calculated by the system to
climb or descend on a route segment, mentioned in field 15,
outside the defined vertical limits of the airway.
EFPM51
PROF50
ROUTE49
CLIMBING/DESCENDING OUTSIDE THE
VERTICAL LIMITS OF SEGMENT
{ARG1/POINT_A} {ARG2/ROUTE}
{ARG3/POINT_A}
THE POINT {ARG1} IS UNKNOWN IN THE
CONTEXT OF THE ROUTE
THE {ARG1/SID_OR_STAR} {ARG2/TP1} IS
NOT VALID. {ARG3/TP2} IS SUGGESTED.
ROUTE48
EDITION 17.1
A point is present in the given route that is regarded as
being illogical.
There are only 2 terminal procedures available at this
aerodrome and the flight does not comply with the
parameters of the terminal procedure indicated in the
message. The second terminal procedure is assumed by
the system.
Requirements
Where a time designator is required, it must be
included.
Each line in the re-addressing function may contain a
maximum of 7 addresses; any more addresses should
be carried on to a new 'AD' line.
Where a route is truncated using the individual letter
'T', no further route items should be inserted.
Where an aircraft type is given as ZZZZ, the correct
wake turbulence category must be given.
defined as being not allowed, an alternative routing is
required.
FPLs should be submitted to IFPS before the EOBT.
File where you fly!
The point should be replaced by either the correct
point, or the geo coordinates of the given point.
ANNEX IFPS MAN
16
Error Class
ROUTE47
ROUTE46
ROUTE45
ROUTE44
ROUTE43
ROUTE42
ROUTE41
EFPM40
EFPM39
Error Text
Reason
NOT VALID BECAUSE OF THE FLIGHT TYPE.
[{ARG3/RESTRICTION_ID}]
NOT VALID BECAUSE OF THE AIRCRAFT
TYPE. [{ARG3/RESTRICTION_ID}].
NOT VALID BECAUSE OF THE AIRCRAFT
EQUIPMENT. [{ARG3/RESTRICTION_ID}].
NOT VALID BECAUSE IT IS CLOSED.
NOT VALID BECAUSE THE RFL IS BELOW MIN
LEVEL ON {ARG3/LAST_OR_FIRST} SEGMENT
OF {ARG4/SID_OR_STAR}.
NOT VALID BECAUSE OF THE RUNWAY IN
USE.
ROUTE CONTAINS A SYSTEM GENERATED
PORTION. PLEASE CHECK.
ACTUAL DATE AND TIME OF ARRIVAL IS NOT
WITHIN ACCEPTABLE RANGE: {ARG1/START}
TO {ARG2/END}.
ACTUAL DATE AND TIME OF DEPARTURE IS
NOT WITHIN ACCEPTABLE RANGE:
{ARG1/START} TO {ARG2/END}.
EFPM38
AFIL ETO IS NOT IN ACCEPTABLE RANGE:
{ARG1/START} TO {ARG2/END}
EFPM37
AFP ETO IS NOT IN ACCEPTABLE RANGE:
EFPM36
FNM ETO IS NOT IN ACCEPTABLE RANGE:
EFPM35
MFS ETO IS NOT IN ACCEPTABLE RANGE:
EFPM34
AIRAC DATA NOT AVAILABLE
EDITION 17.1
The given terminal procedure does not comply with
requirement because of a flight type restriction, and no valid
terminal procedures exist to replace it.
requirement because of an aircraft type restriction, and no
valid terminal procedures exist to replace it.
requirement because of a Radio-Equipment restriction, and
no valid terminal procedures exist to replace it.
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
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
runway in use, and no valid terminal procedures exist to
replace it.
Internal IFPS Error
ARR messages are expected to provide an ATA within a
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
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
any time value, even if that time value is remote when
compared to system time.
AFP messages may be filed containing any time value,
even if that time value is remote when compared to system
time.
FNM messages may be filed containing any time value,
time.
MFS messages may be filed containing any time value,
time.
The date of flight is outside the valid AIRAC data period.
Requirements
N/A
The ATA must be within the acceptable range.
The ATD must be within the acceptable range.
The time given for the estimate point should be within
1 hour of the current system time.
The flight plan message must be filed when the AIRAC
data is available.
ANNEX IFPS MAN
17
Error Class
SYN32
EFPM31
ROUTE30
ROUTE29
Error Text
Reason
MISSING ADEXP EQCST
FLIGHT PLAN ALREADY LOCKED BY
ANOTHER USER
INVALID DCT {ARG1}..{ARG2}:
({ARG3/DISTANCE} NM). DCT LONGER THAN
({ARG4/DISTANCE} NM) ARE NOT ALLOWED
TO CROSS THE BORDER BETWEEN {ARG5}
AND {ARG6}. [{ARG7/RESTRICTION_ID}]
FORBIDDEN TO CROSS THE BORDER
BETWEEN {ARG1} AND {ARG2} ON DCT
{ARG3}..{ARG4}. [{ARG5/RESTRICTION_ID}]
EDITION 17.1
In an ADEXP format message if the ADEXP EQCST field is
corrupt.
Internal IFPS Error
Requirements
N/A
The length of this DCT segment is greater than the Crossborder DCT limit defined for those adjacent NAS.
The route must be changed.
This specific DCT segment is defined as NOT ALLOWED to
cross the boundaries of the two adjacent NAS.
A border crossing point is needed in the route of the
flight.
ANNEX IFPS MAN
18
DOCUMENT FINAL PAGE
EDITION 17.1
ANNEX IFPS MAN
19

annex generated errors

Transcription

Documents pareils

Slots Machines Mecca Jeu Casino En Ligne 3D

GOOD NEWSPAPERS WITH INFORMATION : These sites give

Page 1 of 2 Route finder, route planner, directions, journey planner

Guernsey Church to Church Walk to be held on Sunday 7 September

Adjusted unit rates applicable to April 2010 flights

TREK CHINA CHALLENGE MANUAL

eurostar black out dates

PREPAVOGT

meeting announcement

IC3 Complaint

Implementation guide Web Services V4