This sub-message inserts a new Flight Designator or adds new Periods of Operation and/or new Day(s) of Operation (at the Frequency Rate, if stated) for an existing Flight Designator. When used in conjunction with an SKD sub-message, the data contained in the NEW submessage supersedes the data, if any, for the period specified by its associated SKD sub-message.
The format of an SSM NEW message is as follows: Standard Message Identifier |
S-leg dom | M-leg dom past midnight | M-leg dom to non-s past midnight | M-leg non-s to sch to dom | Several flights in one message | Different flights and types | M-leg with return to same airport |
---|---|---|---|---|---|---|
SSM | SSM | SSM | SSM | SSM | SSM | SSM |
This sub-message cancels (i.e. withdraws) the complete routing of a Flight Designator within the Period and on the Day(s) of Operation (and at the Frequency Rate, if stated).
The format of an SSM CNL message is as follows: Standard Message Identifier |
One Flight in period specified | Several flights in one message | Flight less then 24h in future | Including ASM created flight |
---|---|---|---|
SSM | SSM | SSM SI FLIGHT IS SET TO CNL NOT DELETED | SSM |
This sub-message replaces all existing information pertaining to a Flight Designator within the Period and on the Day(s) of Operation (at the Frequency Rate, if stated) by the new information. Other Periods and other Day(s) of Operation during the period stated (if existing) are not affected. The extension of periods and/or the addition of days of operation are not permitted using RPL sub-messages.
The format of an ASM RPL message is as follows: Standard Message Identifier |
Description | S-leg dom | M-leg dom past midnight | M-leg dom to non-s past midnight | M-leg non-s to sch to dom inkluding XASM |
---|---|---|---|---|
Examples | SSM | SSM | SSM | SSM |
Comment | If changing airport on date of operation, old legs will be marked as cancelled | XASM must be included if ASM message has created flights in the same period. |
For a specific Flight designator/Period of Operation and day(s) of Operation this sub message changes only the Timing information and/or the conditional data elements (if supplied) that can be transmitted in this type of message.
•Other Periods of Operation/Day(s) of Operation remain unchanged
•Data Elements previously transmitted and therefore already held in a recipients system and not included in the message remain unchanged.
The format of an ASM FLT message is as follows: Standard Message Identifier |
Description | S-leg dom |
---|---|
Examples | SSM |
Comment |
This sub-message only changes the Flight Designator (and its associated data elements) and/or the Operational Suffix, for the Period and Day(s) of Operation (at the Frequency Rate, if stated).
Other data elements, Periods and Day(s) of Operation of the original Flight Designator and Operational Suffix are not affected.
The format of an ASM FLT message is as follows: Standard Message Identifier |
Description | Affects day 6-7 bi-weekly |
---|---|
Examples | SSM |
Comment | Changes from TEF9999 to TEF8999 |
This sub-message cancels all existing information for the Flight Designator specified from the Schedule Validity Effective Date as specified to (and including) the Schedule Validity Discontinue Date, if stated. It indicates that revised schedule information, if any, will follow immediately in one or more associated sub-messages using Action Identifier NEW.
The format of an ASM SKD message is as follows: Standard Message Identifier |
Description | S-leg dom |
---|---|
Examples | SSM |
Comment | All flights in period specified are deleted in the Avinor systems. |