相关文章推荐
Info

Syntax Errors:

The syntax error type contains all those errors raised when the submitted message does not adhere to the prescribed formats and manner of specifying data as described in ICAO
Doc. 4444, Appendices 2 & 3; ICAO Doc. 7030, EUR Region; the IFPS Software
Requirements document, and in this document.

Info

Extended Flight Plan Message:

The Expanded Flight Plan Message (EFPM) error type contains those errors raised when
data in the submitted message is inconsistent either with other Items in that message or with the existing IFPS flight plan database, or there is insufficient data to create a flight plan.

Info

Profile errors:

The Profile error type contains all those errors raised where data inconsistencies or violations are found during the calculation of the flight profile of the submitted message.

Info

Route errors:

The Route error type contains all those errors raised where the data format and content in the route portion of the submitted message do not adhere to the prescribed formats and
manner of specifying data, or are inconsistent with the NM CACD.

Info

General Errors:

General Errors are internal IFPS errors and therefore are not visible to external users.

Info

Routing Assistance Errors:

The Proposal Routes tool in the NOP may use all those error message types used in the
IFPS, but it may also use one type specific to the Proposal Routes tool. A number of errors raised are specific to that system alone; such errors are of a type ‘ROUTING ASSISTANCE ERRORS’.

Info

Warning Errors:

The Warning error type contains those errors that are generated to provide indications of difficulties in advance of the introduction of specific new checks to be carried out by the IFPS, e.g. RVSM and 8.33 kHz. Under these conditions, the error message is attached to the output message by the IFPS, but no manual processing error is raised.

Warning error types may also be generated during internal IFPS processing of messages to assist in the manual treatment of messages by the IFPS staff.

  • EFPM166: Z PRESENT BUT COM/DAT/NAV ABSENT (Field Name) (1)EFPM166: PBN PRESENT BUT R ABSENT (Field Name)                (2)EFPM166: R PRESENT BUT PBN ABSENT (Field Name)                (3)
  • EFPM167: FILED PBN REQUIRES CEQPT
  • EFPM209: STS/NONRVSM IS NOT EXPECTED FOR AN RVSM APPROVED FLIGHT WITHIN EUR RVSM AIRSPACE
  • EFPM210: NON RVSM APPROVED FLIGHT WITHIN EUR RVSM AIRSPACE AND STS/NONRVSM IS NOT EXPECTED FOR A CIVIL AIRCRAFT
  • EFPM211: STS/NONRVSM IS REQUIRED FOR NON RVSM APPROVED STATE FLIGHT
  • EFPM212: FIELDS 10 AND/OR 18 INCORRECT FOR STATE FORMATION FLIGHT IN EUR RVSM AIRSPACE
  • EFPM213: UNEXPECTED ROUTE DATA
  • EFPM214: MISSING ROUTE DATA
  • EFPM215: FLIGHT PLAN DATA HAS RESTRICTED ACCESS
  • EFPM216: POSSIBLE DOF SBUFIELD WITH WRONG SYNTAX DETECTED IN FIELD18. (Field Name)
  • EFPM217: FPL WITH SAME ARC_ID AND OVERLAPPING FLYING PERIOD EXISTS:
  • EFPM219: NON RVSM APPROVED FLIGHT WITHIN EUR RVSM AIRSPACE
  • EFPM220: NO EXISTING FILED FLIGHT PLAN MATCHING THIS MESSAGE
  • EFPM221: NO VALID ENVIRONMENT FOR TIME
  • EFPM223: EOBT IN THE PAST COMPARED TO IFPS SYSTEM TIME:
  • EFPM224: MESSAGE MATCHES MULTIPLE FLIGHT PLANS
  • EFPM225: MISSING OR ERRONEOUS FIELD (Field Name)
  • EFPM226: THIS MESSAGE ASSOCIATES WITH THE FPD:
  • EFPM227: MANUAL ADDRESSING REQUIRED. PRESS APPLY TO CONTINUE
  • EFPM228: INVALID VALUE (...)EFPM228: INVALID VALUE AT ROW=XX, COL=YY (...)
  • EFPM229: INVALID FORMAT
  • EFPM230: ASSOCIATION NO LONGER VALID THE FPD IS CLOSED
  • EFPM231: CIVIL FORMATION FLIGHT NOT PERMITTED IN EUR RVSM AIRSPACE
  • EFPM232: FLIGHT PLAN ALREADY RECEIVED FROM ADDRESS
  • EFPM234: ESTIMATED OFF BLOCK DATE AND TIME IS NOT WITHIN ACCEPTABLE RANGE AFTER FILING TIME. (EOBD)
  • EFPM235: FIELD FORBIDDEN IN THIS TYPE OF MESSAGE (Field Name)
  • EFPM236: ESTIMATED OFF BLOCK DATE AND TIME NOT IN THE ACCEPTABLE RANGE: DDHHMM TO DDHHMM
  • EFPM237: MESSAGE MATCHES EXISTING INVALID MESSAGES
  • EFPM238: MESSAGE FILED BEFORE MATCHING FILED FLIGHT PLAN
  • EFPM239: DATE AND TIME GIVEN ARE INCONSISTENT WITH
  • EFPM241: MESSAGE ASSOCIATES TO FLIGHT
  • EFPM243: AIRCRAFT TYPE IS ZZZZ BUT TYP Z IS NOT PRESENT (ARCTYP)
  • EFPM245: AIRCRAFT TYPE AND TYPZ PRESENT (TYPZ)
  • EFPM247: EFPM247: ALTERNATE AERODROME IS ZZZZ BUT ALTN INFO IS NOT PRESENT (ALTRNT1 or ALTRNT2)
  • EFPM248: AERODROME IS ZZZZ BUT DEP Z IS NOT PRESENT (ADEP) EFPM248: AERODROME IS ZZZZ BUT DEST Z IS NOT PRESENT (ADES)
  • EFPM249: ACTUAL DATE AND TIME OF DEPARTUE IS NOT WITHIN ACCEPTABLE RANGE, AFTER RECEPTION TIME. (ATD)
  • EFPM250: ACTUAL DATE AND TIME OF ARRIVAL IS NOT WITHIN ACCEPTABLE RANGE, AFTER RECEPTION TIME. (ATA)
  • EFPM31: FLIGHT PLAN ALREADY LOCKED BY ANOTHER USER
  • EFPM321: FPL WITH SAME REG MARKINGS AND OVERLAPPING FLYING PERIOD EXISTS:
  • EFPM324: ACTIVE FPL WITH SAME GUFI EXISTS: (ARCID) (ADEP) (ADES) (EOBT)                          FF-ICE
  • EFPM330: ROUTE CROSSES TOO MANY AIRSPACES MORE THAN
  • EFPM334: AIRCRAFT OPERATOR FLIGHT PLAN VERSION NOT INCREMENTING BY 1 CURRENT NEW                                           FF-ICE
  • EFPM335: INCONSISTENT DATA (TOTAL NUMBER OF AIRCRAFT AND  FORMATION COUNT ARE DIFFERENT)           FF-ICE EFPM335: INCONSISTENT DATA ( WAS SUBMITTED AS A NON_ICAO AIRCRAFT TYPE DESIGNATOR)      FF-ICE
  • EFPM34: AIRAC DATA NOT AVAILABLE (Field Name)
  • EFPM35: MFS ETO IS NOT IN ACCEPTABLE RANGE: HH:MM TO HH:MM (Field Name)
  • EFPM36: FNM ETO IS NOT IN ACCEPTABLE RANGE: HH:MM TO HH:MM (Field Name)
  • EFPM37: AFP ETO IS NOT IN ACCEPTABLE RANGE: HH:MM TO HH:MM (Field Name)
  • EFPM38: AFIL ETO IS NOT IN ACCEPTABLE RANGE: HH:MM TO HH:MM (Field Name)
  • EFPM39: ACTUAL DATE AND TIME OF DEPARTURE IS NOT IN ACCEPTABLE RANGE: HH:MM TO HH:MM. (Field Name)
  • EFPM40: ACTUAL DATE AND TIME OF ARRIVAL IS NOT IN ACCEPTABLE RANGE: HH:MM TO HH:MM. (Field Name)
  • EFPM402: CLOSED FPL WITH SAME GUFI EXISTS: (ARCID) (ADEP) (ADES) (EOBT)                                        FF-ICE
  • EFPM405: NOT ALLOWED TO USE A FPL TO UPDATE THE EOBT OF EXISTING FPL: . DLA OR CHG IS REQUIRED.
  • EFPM406: EUR OAT ONLY ALLOWED FOR MIL FLIGHTS
  • EFPM51: FPL PROCESSED AFTER ESTIMATED TIME OF ARRIVAL
  • GEN207: UNABLE TO GENERATE A COMPLETE REPLY
  • GEN277: MESSAGE REQUIRES SPECIAL HANDLING
  • PROF173: RS: IS CLOSED FOR DCT REF:
  • PROF188: FLIGHT PLAN DOES NOT COMPLY WITH 8.33 CARRIAGE REQUIREMENTS
  • PROF189: NON 8.33 BUT UHF EQUIPPED AIRCRAFT IN 8.33 AIRSPACE NOT HANDLING UHF
  • PROF190: NON 8.33 AND NON UHF EQUIPPED AIRCRAFT IN 8.33 AIRSPACE
  • PROF191: PROF191: TTL_EET DIFFERENCE > (value) %, CALCULATED TTL_EET FROM TO = (HHMM)
  • PROF192: TOTAL STAY/DLE TIME GREATER THAN TOTAL ESTIMATED ELAPSED TIME.
  • PROF193: IFR OPERATIONS AT AERODROME ARE NOT PERMITTED
  • PROF194: IS NOT AVAILABLE IN FL RANGE
  • (1) PROF195: DOES NOT EXIST IN FL RANGE  (2) PROF195: DOES NOT EXIST IN FL RANGE
  • PROF197: RS: :FXXX..FXXX IS CLOSED FOR CRUISING REF:
  • PROF198: IS A CDR 3 IN FL RANGE
  • PROF200: IS A CLOSED CDR_1 IN FL RANGE
  • PROF201: CANNOT CLIMB OR DESCEND ON IN FL RANGE BECAUSE OF UNAVAILABLE LEVELS ON                     PROF201: CANNOT CLIMB OR DESCEND ON IN FL RANGE CLOSED, BECAUSE OF UNAVAILABLE LEVELS ON
  • PROF202: IS NOT AVAILABLE IN FL RANGE
  • PROF203: PROFILE ANALYSIS STOPPED
  • PROF204: RS: TRAFFIC VIA IS ON FORBIDDEN ROUTE REF: PROF204: RS: TRAFFIC VIA :[] IS ON FORBIDDEN ROUTE REF:
  • PROF205: RS: TRAFFIC VIA IS OFF MANDATORY ROUTE REF:
  • PROF206: THE DCT SEGMENT .. IS NOT AVAILABLE IN FL RANGE (UNAVAILABLE ROUTE )
  • PROF323: TRAJECTORY INFO ERROR (…)                                                FF-ICEPROF323: TRAJECTORY INFO ERROR (MORE THAN ONE TOD)PROF323: TRAJECTORY INFO ERROR (NUMBER OF TOC AND REQUESTED CRUISING LEVELS DO NOT MATCH)PROF323: TRAJECTORY INFO ERROR (DERIVED TAXI TIME IS NOT IN RANGE TO )PROF323: TRAJECTORY INFO ERROR (FIRST ELEMENT DOES NOT CONTAIN THE DEPARTURE AERODROME)PROF323: TRAJECTORY INFO ERROR (LAST ELEMENT DOES NOT CONTAIN THE DESTINATION AERODROME)PROF323: TRAJECTORY INFO ERROR (ALONG ROUTE DISTANCE INCONSISTENCY BETWEEN and )PROF323: TRAJECTORY INFO ERROR (RSL WITHOUT ISL)PROF323: TRAJECTORY INFO ERROR (TCV WITHOUT ISL)PROF323: TRAJECTORY INFO ERROR (POINT NOT ON ROUTE )PROF323: TRAJECTORY INFO ERROR (UNKNOWN DESIGNATOR )PROF323: TRAJECTORY INFO ERROR (POINT NOT AT )PROF323: TRAJECTORY INFO ERROR (ROUTE CANNOT FOLLOW AFTER POINT )PROF323: TRAJECTORY INFO ERROR ( PERFORMANCE PROFILE NOT PROGRESSING BETWEEN ALTITUDES  )
  • PROF325: CRITICAL YOYO DETECTED ON .. CRITICAL ON ..
  • PROF326: CRITICAL YOYO DETECTED ON .. DUE TO DESCENT AT .. CLIMB AT
  • PROF340: CRITICAL SHARP TURN DETECTED AT POINT ON   ..
  • PROF50: CLIMBING/DESCENDING OUTSIDE THE VERTICAL LIMITS OF SEGMENT
  • PROF53: THE DCT SEGMENT .. IS NOT ALLOWED: ALONG AIRSPACE BORDER BETWEEN and
  • RA274: NBROUTE ARGUMENT INVALID
  • RA281: NUMBER OF CONSTRAINTS FOR ROUTE GENERATION EXCEEDS {ARG1/NUMBER}
  • ROUTE125: FLIGHT RULES Z WITH NO IFR PART.
  • ROUTE126: FLIGHT RULES Y WITH NO VFR PART.
  • ROUTE127: FLIGHT RULES V WITH IFR PART.
  • ROUTE129: INSUFFICIENT DATA TO RESOLVE HOMONYM AT
  • ROUTE130 : UNKNOWN DESIGNATOR
  • ROUTE131: TRUNCATED ROUTE
  • ROUTE132: THE IS NOT VALID. IS SUGGESTED. OTHER POSSIBLE TPS VIA ARE
  • ROUTE133: THE STAY PORTION AT POINT IS NOT PERMITTED FOR A FLIGHT GOING OUT OF THE IFPZ
  • ROUTE134: THE STAR LIMIT IS EXCEEDED FOR AERODROME CONNECTING TO
  • ROUTE135: THE SID LIMIT IS EXCEEDED FOR AERODROME CONNECTING TO
  • ROUTE138: CANNOT HAVE A ROUTE BETWEEN THE SAME POINT; ROUTE: , POINT:
  • ROUTE139: IS PRECEDED BY WHICH IS NOT ONE OF ITS POINTS
  • ROUTE140: IS FOLLOWED BY WHICH IS NOT ONE OF ITS POINTS
  • ROUTE142: POINT AMBIGUOUS , POSSIBLE CHOICES ARE
  • ROUTE143: A POINT DESIGNATOR IS EXPECTED BEFORE
  • ROUTE144: NO ROUTE BETWEEN and
  • ROUTE145: A POINT IS EXPECTED AFTER A STAY INDICATOR
  • ROUTE146: JUNCTIONS EXIST BETWEEN and BUT CANNOT BE USED. Junctions are
  • ROUTE147: THE NAT TRACK IS NOT ACTIVE.
  • ROUTE148: NO JUNCTION BETWEEN AND
  • ROUTE149: MISSING DESIGNATOR
  • ROUTE150: MISSING CRUISING FLIGHT LEVEL
  • ROUTE151: THE POINT CANNOT BE USED TO LEAVE OR JOIN THE TP
  • ROUTE152: FLIGHT NOT APPLICABLE TO IFPS
  • ROUTE155: MULTIPLE JUNCTIONS BETWEEN AND . IS SUGGESTED.
  • ROUTE157: FLIGHT RULES I WITH VFR PART.
  • ROUTE161: THIS FIELD VALUE IS INCONSISTENT WITH THE FLIGHT RULES. (RFL)
  • ROUTE162: THE POINT FROM DLE DATA IS NOT IN THE FLIGHT ROUTE ROUTE162: THE POINT FROM ESTIMATE DATA IS NOT IN THE FLIGHT ROUTE
  • ROUTE165: THE DCT SEGMENT : :. MAXIMUM IS : [Restriction Id]ROUTE165: THE DCT SEGMENT ..: (XX NM) IS TOO LONG FOR . MAXIMUM IS : [Restriction Id]
  • ROUTE168: INVALID DCT . DCT ARE NOT ALLOWED TO CROSS THE BORDER BETWEEN AND
  • ROUTE169: CONSECUTIVE STAY INDICATORS NOT ALLOWED
  • ROUTE171: CANNOT EXPAND THE ROUTE
  • ROUTE172: MULTIPLE ROUTES BETWEEN AND . IS SUGGESTED. OTHER CANDIDATES ARE:
  • ROUTE174: INVALID TIME GIVEN FOR (EET PT) ROUTE174: INVALID TIME GIVEN FOR (EET FIR)
  • ROUTE175: SPEED AT IS INVALID OR INCOMPATIBLE WITH AIRCRAFT PERFORMANCE
  • ROUTE176: FLIGHT LEVEL AT IS INVALID OR INCOMPATIBLE WITH AIRCRAFT PERFORMANCE
  • ROUTE178: CRUISING SPEED IS INVALID OR INCOMPATIBLE WITH AIRCRAFT PERFORMANCE
  • ROUTE179: CRUISING FLIGHT LEVEL IS INVALID OR INCOMPATIBLE WITH AIRCRAFT PERFORMANCE
  • ROUTE180: ROUTE ANALYSIS HAS ABORTED
  • ROUTE29: FORBIDDEN TO CROSS THE BORDER BETWEEN AND on DCT .. ..
  • ROUTE30: INVALID DCT ..: ( NM). DCT LONGER THAN ( NM) ARE NOT ALLOWED TO CROSS THE BORDER BETWEEN AND .
  • ROUTE301: NO VALID CONNECTION POINT FOUND ON FLIGHT PLAN ROUTE.
  • ROUTE302: CANNOT AUTOMATICALLY GENERATE ROUTE WITH IFPSTOP PORTION
  • ROUTE303: NO VALID ROUTE FOUND TO CONNECT TO FLIGHT ROUTE.
  • ROUTE304: CANNOT AUTOMATICALLY GENERATE ROUTE WITH VFR OR OAT PORTION
  • ROUTE305: FLIGHT TYPE IS MILITARY. PLEASE CHECK NAS OF GENERATED PORTION: .
  • ROUTE308: THE IS NOT VALID BECAUSE THERE IS NO CONNECTING POINT WITH ROUTE.
  • ROUTE310: IFPSRA NO ROUTE FOUND
  • ROUTE311: IFPSRA NO ACK
  • ROUTE312: ROUTE AUTOMATICALLY BUILT. PLEASE CHECK.
  • ROUTE314: INVALID RFL IN VFR PORTION
  • ROUTE315: THE IS NOT VALID BECAUSE OF THE AIRCRAFT OPERATOR CODE.
  • ROUTE316: THE IS NOT VALID BECAUSE OF THE AIRCRAFT REGISTRATION.
  • ROUTE317: THE IS NOT VALID BECAUSE OF THE 24 BIT AIRCRAFT ADDRESS.
  • ROUTE318: THE IS NOT VALID BECAUSE OF THE FLIGHT PLAN SOURCE.
  • ROUTE319: THE IS NOT VALID BECAUSE OF THE FLIGHT PLAN STATUS.
  • ROUTE322: INVALID POINT USAGE. THE POINT IS NOT ALLOWED IN THE PART OF THE ROUTE
  • ROUTE329: THE IS NOT VALID BECAUSE OF THE REMARK FIELD. []
  • ROUTE41: PLEASE CHECK NAS OF GENERATED PORTION: .
  • ROUTE42: THE IS NOT VALID BECAUSE OF THE RUNWAY IN USE.
  • ROUTE43: THE IS NOT VALID BECAUSE THE RFL IS BELOW MIN LEVEL ON SEGMENT OF .
  • ROUTE44: THE IS NOT VALID BECAUSE IT IS CLOSED.
  • ROUTE45: THE IS NOT VALID BECAUSE OF THE AIRCRAFT EQUIPMENT. .
  • ROUTE46: THE IS NOT VALID BECAUSE OF THE AIRCRAFT TYPE. .
  • ROUTE47: THE IS NOT VALID BECAUSE OF THE FLIGHT TYPE. .
  • ROUTE48: THE IS NOT VALID. IS SUGGESTED.
  • ROUTE49: THE POINT IS UNKNOWN IN THE CONTEXT OF THE ROUTE
  • ROUTE52: THE DCT SEGMENT .. IS FORBIDDEN. RESTRICTION: ROUTE52: THE DCT SEGMENT ..IS FORBIDDEN. (Free Route Airspace)
  • SYN100: INVALID LIST
  • (1) SYN101: INVALID LEVEL DESIGNATOR AT ROW= x, COL= y (RFL) (2) SNY101: INVALID LEVEL DESIGNATOR (ROUTE)
  • SYN102: INVALID LATITUDE DESIGNATOR AT ROW= x, COL= y (Field Name)
  • SYN103: INVALID ID USED IN FIELD AT ROW= x, COL= y (Field Name)
  • SYN104: INVALID FIELD AT ROW=x, COL=y (Field Name) SYN104: INVALID FIELD AT ROW=x, COL=y
  • SYN105: INVALID DISTANCE DESIGNATOR
  • SYN106: WRONG POINT FOR GEO
  • SYN108: INVALID DATE DESIGNATOR AT ROW= x, COL= y (Field Name)
  • SYN109: FIELD CONTAINS INVALID CHARACTER(S) AT ROW = x, COL = y (Field Name)
  • SYN110: INVALID BEARING DESIGNATOR AT ROW= x, COL= y (Field Name)
  • SYN111: MISPLACED INDICATOR. MUST BE AFTER A POINT AT ROW= x, COL= y (Field Name)
  • SYN112: INCORRECT USAGE OF BRACKETS "(" AND ")"
  • SYN114: EXPECTED ‘/’ AT ROW= x, COL= y
  • SYN115: EXPECTED FLIGHT TYPE AND RULES AT ROW= x, COL= y (FLTTYP)
  • SYN116: EXPECTED OR INVALID FLIGHT TYPE AT ROW= x, COL= y (Field Name)
  • SYN117: EXPECTED OR INVALID FLIGHT RULES AT ROW= x, COL= y (Field Name)
  • SYN118: EXPECTED END OF MESSAGE
  • SYN120: INTERNAL ERROR
  • SYN121: DUPLICATE ERROR AT ROW=x, COL=y (Sub-Field name)
  • SYN122: EXPECTED DATE DESIGNATOR NOT FOUND
  • SYN123: EXPECTED CNA EQUIPMENT DESIGNATOR AT ROW= x, COL= y (Field Name)
  • SYN124: MISSING OR INVALID CHANGE RULES
  • SYN153: INVALID COMBINATION OF MODE S CAPABILITY AT ROW=x, COL=y
  • SYN33: (Indicator Name) NOT ALLOWED IN ROUTE
  • SYN60: INVALID WAKE TURBULENCE CATEGORY AT ROW= x, COL= y (WKTRC)
  • SYN62: UNKNOWN OR UNEXPECTED FIELD AT ROW= x, COL= y (Field Name)
  • SYN64: MISSING OR INVALID AIRCRAFT ID
  • SYN65: UNEXPECTED SEPARATOR AT ROW= x,COL= y (Field Name)
  • SYN66: ADDITIONAL DATA FOLLOWS TRUNCATION INDICATOR
  • SYN68: TOO MANY ADDRESSES ON LINE AT ROW= x,COL= y
  • SYN69: EXPECTED TIME DESIGNATOR NOT FOUND AT ROW= x, COL= y (Field Name)
  • SYN70: FIELD TEXT TOO SHORT AT ROW= x,COL= y (Field Name)
  • SYN71: FIELD TEXT TOO LONG AT ROW= x,COL= y (Field Name)
  • SYN72: SUSPECT TEXT TOO LONG AT ROW= x,COL= y (Field Name)
  • (1) SYN73: SUSPECT INVALID FIELD AT ROW= x,COL= y (F18 AFTER F19              (x,y)) (2) SYN73: SUSPECT INVALID FIELD AT ROW= x, COL= y (ICAO DAT/ in RMK DATA)
  • SYN74: EXPECTED SSR EQUIPMENT DESIGNATOR AT ROW= x,COL=Y (SEQPT)
  • SYN76: NO PARALLEL ALLOWED IN FIELD AT ROW= x,COL= y (Field Name)
  • SYN77: EXPECTED NUMERIC ROW= x,COL=y (Field Name)
  • SYN78: NO CHANGES ALLOWED IN KEY FIELD AT ROW= x,COL= y (Field Name)
  • SYN80: MULTIPLE MATCHING LONGITUDE FOUND IN ROUTE, CANNOT EXPAND MERIDIAN
  • SYN81: MULTIPLE MATCHING LATITUDE FOUND IN ROUTE, CANNOT EXPAND PARALLEL
  • SYN84: MISSING OR INVALID LEVEL
  • SYN85: MISSING FIELD ROW= x, COL= y (Field Name)
  • SYN87: MISSING OR INVALID ETO
  • SYN88: MISSING OR INVALID END KEYWORD
  • SYN90: NO MERIDIAN ALLOWED IN FIELD AT ROW= x,COL= y (Field Name)
  • SYN91: DUPLICATE DATA
  • SYN92: MISSING OF INVALID TITLE
  • SYN93: INVALID TIME DESIGNATOR AT ROW= x, COL= y (Field Name)
  • SYN95: INVALID SPEED DESIGNATOR AT ROW= x, COL= y (Field Name)
  • SYN96: INVALID SOURCE
  • SYN97: INVALID SEPARATOR AT ROW= x, COL= y
  • SYN98: INVALID POINT
  • SYN99: INVALID LONGITUDE DESIGNATOR AT ROW= x, COL= y (Field Name)
  • WARN257: INVALID AIRCRAFT ADDRESS (CODE) HAS NOT BEEN STORED
  • WARN258: INVALID AIRCRAFT ADDRESS (CODE) HAS NOT BEEN STORED. PREVIOUS AIRCRAFT ADDRESS HAS BEEN REMOVED
  • WARN262: WHAT-IF-REROUTE MESSAGE
  • WARN265: EQCST FIELD CONTAINS CONFLICTING EQUIPMENT CHANGES FOR
  • WARN313: TRAJECTORY INFO DISCARDED (...)                                                FF-ICE
  • WARN320: AIRCRAFT TYPE ZZZZ, CALCULATED DEFAULT CATEGORY
  • WARN328: ERROR SUPPRESSED (…)
  • WARN333: INFORMATION (…)                                                FF-ICEWARN333: INFORMATION (CLIMB/DESCENT PERFORMANCE PROFILE MUST CONSIST OF AT LEAST TWO ITEMS: PERFORMANCE PROFILE DISCARDED)WARN333: INFORMATION (DCT BETWEEN AND REPLACED BY IN FIELD 15)WARN333: INFORMATION ( PERFORMANCE PROFILE NOT PROGRESSING BETWEEN ALTITUDES  )WARN333: INFORMATION (EDIT OF IGNORED)WARN333: INFORMATION (POINT NOT ON ROUTE )WARN333: INFORMATION (UNKNOWN DESIGNATOR )
  • This online tool uses the content of the official version of the IFPS User Manual, and includes the latest updates released by Operational Instructions. It enables the users of the tool to have a constant access to the most up-to-date version of the manual.

    The official version of the IFPS User Manual shall normally be published at least one (1) month prior to the date of application of the procedures. The document is available for consultation and for download on the EUROCONTROL Internet Site: https://www.eurocontrol.int/publication/ifps-users-manual

    The official electronic version of this manual available on the above webpage in .pdf format shall take precedence over the tool and any printed versions. Only in the case of contingency, where the tool and the electronic version are not available or may be considered unreliable shall a printed version be the official source.

    Please note that, in case of off-line access to this tool, the information contained therein may be outdated.

     
    推荐文章