DEI - Values used in the SSM/ASM messages (this is not a sub-message):

Number	Description	Example
DEI 1	Joint Operation Airline Designators	1/KL/LH
DEI 2	Operating Airline Disclosure Code Share	2/DL
DEI 3	Aircraft Owner	3/DY
DEI 4	Cockpit Crew Employer	4/WF
DEI 5	Cabin Crew Employer	5/LX
DEI 6	Onward Flight	6/SK345/15
DEI 10	Codeshare	10/DY132/UF4621

See IATA manual "Standard Schedules Information Manual (SSIM)" chapter 2.6 for more DEI codes.

Change Reason:

A set of codes used to provide an explanation for a change of an adhoc flight or slot request/response.

Code	Interpretation
AIRS	Airspace restrictions
ARPT	Airfield restrictions
COMM	Commercial reasons, demand or lack of demand
CREW	Crew shortage
DAMA	Aircraft damage
EQUI	Equipment shortage
FUEL	Fuel shortage
HDLG	Ground handling
HOLI	Holiday
INDU	Industrial dispute
OPER	Operational reasons
PERF	Aircraft performance
POLI	Political situation
POSI	Aircraft positioning
REPO	Aircraft re-positioning
ROTA	Aircraft rotation
RTNS	Return to normal schedule or reinstatement of flight status prior to issuance of ASM(s) (withdrawal of ASM change)
RUNW	Runway restrictions
TECH	Technical reasons, maintenance, etc.
WEAT	Weather conditions

This is specified in the IATA manual "Standard Schedules Information Manual (SSIM)" chapter 2.6.

SSM - Standard Schedules Message

NEW - Insertion of New Flight Information

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.

Format of message:

The format of an SSM NEW message is as follows:

Standard Message Identifier
Time mode
Action Identifier
Flight designator
Period /Frequency
Service Type, Aircraft Type, Aircraft Configuration Version
Routing og Leg information (LEG NO 1)
Routing og Leg information (LEG NO 2)

Examples, single-leg (s-leg) and multi-leg (m-leg) flights, both domestic (dom), Schengen (sch) and Non-Schengen (non-s):

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 UTC NEW TEF9999 04APR24 03MAY24 1234567 J 738 C16M165VV738B.X103 OSL1455 KKN1550	SSM UTC NEW TEF9989 12APR24 20MAY24 123467 J 739 C16M165VV738B KKN1455 TRD1550 TRD1620 BGO1800 BGO0030/1 BVG0230/1	SSM UTC NEW TEF9997 06APR24 12MAY24 1267 J 738 C16M165VV738B OSL1455 TRD1550 TRD1630 KRS1730 KRS0255/1 LHR0855/1	SSM UTC NEW TEF9996 10APR24 20MAY24 1234567 J 738 C16M165VV738B LHR0200 ARN1000 ARN1455 KKN1650 KKN1620 BGO1800	SSM UTC NEW TEF9995 06FEB24 12FEB24 1234567 J 738 C16M165VV738B OSL1455 TRD1550 // NEW TEF9994 06FEB24 12FEB24 1234567 J 738 C16M165VV738B TRD1615 OSL1705	SSM UTC NEW TEF9993 06FEB24 12FEB24 1234567 J 738 C16M165VV738B HAM1255 BLL1325 BLL1455 OSL1550 // EQT ABB9996 06FEB24 10FEB24 3456 J 321 C16M165VV738B	SSM UTC NEW TEF9992 12MAR24 16MAR24 1234567 J 738 C16M165VV738B OSL1455 TRD1550 TRD1620 HFT1800 HFT1900 BGO2000 BGO2130 OSL2200

CNL - Cancellation of Flight Information

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
Time mode
Action Identifier
Flight designator
Period /Frequency

Examples, one flight or several flights at the same time:

One Flight in period specified	Several flights in one message	Flight less then 24h in future	Including ASM created flight
SSM UTC CNL TEF9999 22APR24 03MAY24 1234567	SSM UTC CNL TEF9995 06FEB24 12FEB24 1234567 // CNL TEF9994 06FEB24 12FEB24 1234567	SSM UTC CNL TEF9997 06APR24 12MAY24 1267 SI FLIGHT IS SET TO CNL NOT DELETED	SSM UTC CNL XASM TEF9996 10APR24 20MAY24 123456

RPL - Replacement of Existing Flight Information

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 SSM RPL message is as follows:

Standard Message Identifier
Time mode
Action Identifier
Flight designator
DateStart DateEnd WeekDays
Service Type, Aircraft Type, Aircraft Configuration Version
Routing og Leg information (LEG NO 1)
Routing og Leg information (LEG NO 2)

Examples, one flight or several flights at the same time:

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 UTC RPL TEF9999 04APR24 03MAY24 1234567 J 738 C16M165VV738B.X103 OSL1455 KKN1550	SSM UTC RPL TEF9989 12APR24 20MAY24 123467 J 739 C16M165VV738B KKN1455 TRD1550 TRD1620 BGO1800 BGO0030/1 BVG0230/1	SSM UTC RPL TEF9997 06APR24 12MAY24 1267 J 738 C16M165VV738B OSL1455 TRD1550 TRD1630 BGO1730 BGO0255/1 LHR0855/1	SSM UTC RPL XASM TEF9996 10APR24 20MAY24 1234567 J 73W C16M165VV738B LHR0200 ARN1000 ARN1455 KKN1650 KKN1620 BGO1800
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.

TIM- Change of Time Information

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 SSM TIM message is as follows:

Standard Message Identifier
Time mode
Action Identifier
Flight designator
DateRange
Flight designator

Example:

S-leg dom
SSM UTC TIM TEF9997 01DEC15 23DEC15 23 OSL1200 BGO1400

FLT - Change of Flight Designator

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 SSM FLT message is as follows:

Standard Message Identifier
Time mode
Action Identifier
Flight designator
DateRange
Flight designator

Example:

Description	Affects day 6-7 bi-weekly
Example	SSM UTC FLT AIRS TEF9999 01DEC 29DEC 67/W2 TEF8999
Comment	Changes from TEF9999 to TEF8999

SKD- Schedule Update

This sub-message cancels/deletes 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 SSM SKD message is as follows:

Standard Message Identifier
Time mode
Action Identifier (XASM not mandatory)
Flight designator
DateStart DateEnd (EndDate is optional!)

Example:

Description	SKD Example
Example	SSM UTC SKD XASM TEF9998 18SEP 18NOV
Comment	All flights in period specified are deleted in the Avinor systems.

EQT- Change of Equipment Information

For a specific Flight designator/Period of Operation and day(s) of Operation this sub message changes only the Equipment 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 SSM EQT message is as follows:

Standard Message Identifier
Time mode
Action Identifier
Flight designator
DateStart DateEnd WeekDays
Service Type, Aircraft Type, Configuration, DEI 1 to 6
OrigDest, Flight#, Airc.Type, Configuration, DEI 1 to 6

Example:

EQT Example
SSM UTC EQT TEF9995 18APR24 23APR24 234 J 73W C012M124.C036M106 3/TEF 4/TEF 5/TEF 6/TEF1196/19NOV15 AMSSVG 953/AMS182010 SVG182140 AMSSVG 958/TEF LNDIG/TEF 73W AMSSVG 960/FLEET 73H TEF /73W TEF

ADM- Change of Existing Information

Change of Existing Information Expressed by the Use of Data Element Identifier Only
For a specific Flight designator/Period of Operation and day(s) of Operation this sub message changes only those data elements which are specified by the use of a Data Element Identifier.

•Other Periods of Operation/Day(s) of Operation remain unchanged

•When cancelling existing information the statement ‘NIL’ must be made

•If changes are leg related, replacement data need only be transmitted for legs where the data has changed. For example, in the case of Data Element Identifier 10, it is not necessary to transmit all legs that have Data Element Identifier 10 information, only those legs where DEI 10 needs changing

The format of an SSM ADM message is as follows:

Standard Message Identifier
Time mode
Action Identifier
Flight designator
DateStart DateEnd WeekDays
OrigDest, Flight#, Airc.Type, Configuration, DEI 3 to 6

Example:

ADM Example
SSM UTC ADM TEF1205 18NOV15 18SEP15 2467 AMSSVG 952/J 73W C036M106 3/TEF 4/TEF 5/TEF 6/TEF1196/19NOV15 AMSSVG 953/AMS182010 SVG182140 AMSSVG 958/TEF 73W

ASM - Ad-Hoc Schedules Message

NEW - Insertion of New Flight Information

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.

Format of message:

The format of an ASM NEW message is as follows:

Standard Message Identifier
Time mode
Action Identifier
Flight designator/Date
Service Type, Aircraft Type, Aircraft Configuration / Version, Aircraft Registration, DEI
Routing og Leg information (LEG NO 1)
Routing og Leg information (LEG NO 2)

Examples, single-leg (s-leg) and multi-leg (m-leg) flights, both domestic (dom), Schengen (sch) and Non-Schengen (non-s):

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
ASM UTC NEW TEF7999/04APR24 J 738 C16M165VV738B.X103 OSL1455 KKN1550	ASM UTC NEW TEF7998/02APR24 J 739 C16M165VV738B KKN1455 TRD1550 TRD1620 BGO1800 BGO0030/1 BVG0230/1	ASM UTC NEW TEF9997/06APR24 J 738 C16M165VV738B OSL1455 TRD1550 TRD1630 KRS1730 KRS0255/1 LHR0855/1	ASM UTC NEW TEF9996/10APR24 J 738 C16M165VV738B LHR0200 ARN1000 ARN1455 KKN1650 KKN1620 BGO1800	ASM UTC NEW TEF9995/06FEB24 J 738 C16M165VV738B OSL1455 TRD1550 // NEW TEF9994/06FEB24 J 738 C16M165VV738B TRD1615 OSL1705	ASM UTC NEW TEF7993/06FEB24 J 738 C16M165VV738B HAM1255 BLL1325 BLL1455 OSL1550 // TIM TEF7996/06FEB24 TRD1615 OSL1705	ASM UTC NEW TEF9992/12MAR24 J 738 C16M165VV738B OSL1455 TRD1550 TRD1620 HFT1800 HFT1900 BGO2000 BGO2130 OSL2200

CNL - Cancellation of Flight Information

This sub-message cancels (i.e. declares as not operating), but retains as part of the basic schedule, one or more flights or parts of flight(s) defined by the Flight Identifier(s) (and Flight Leg Change Identifier, if applicable).
It is recommended that the facility to cancel part of a flight (using ASM/CNL with a Flight Leg Change Identifier) is confined to the operational phase of the flight only since a partial cancellation may lead to a Flight Designator duplication problem if the first leg or a middle leg of a flight is cancelled.
Partial cancellations would normally be communicated unambiguously using ASM/RPL.

Format of message:

The format of an ASM CNL message is as follows:

Standard Message Identifier
Time mode
Action Identifier
Flight designator/Date

Examples, single-leg (s-leg) and multi-leg (m-leg) flights:

S-leg dom	Several flights in one message	Different flights and types
ASM UTC CNL TEF7999/04APR24	ASM UTC CNL TEF7995/06FEB24 // CNL TEF7994/06FEB24	ASM UTC NEW TEF7993/06FEB24 J 738 C16M165VV738B HAM1255 BLL1325 BLL1455 OSL1550 // CNL TEF7996/06FEB24

RPL - Replacement of Flight Information

This sub-message replaces all information pertaining to an existing flight defined by a Flight Identifier by the new information.
If only specific information has to be replaced, the following Action Identifiers can be used instead of the complete RPL message.

Format of message:

The format of an ASM RPL message is as follows:

Standard Message Identifier
Time mode
Action Identifier
Flight designator/Date
Service Type, Aircraft Type, Aircraft Configuration / Version, Aircraft Registration, DEI
Routing og Leg information (LEG NO 1)
Routing og Leg information (LEG NO 2)

Examples, single-leg (s-leg) and multi-leg (m-leg) flights, both domestic (dom), Schengen (sch) and Non-Schengen (non-s):

S-leg dom	M-leg dom past midnight	M-leg dom to non-s past midnight and Route change
ASM UTC RPL TEF7999/04APR24 J 73W C16M165VV738B.X103 OSL1455 KKN1550	ASM UTC RPL TEF7998/02APR24 J 73W C16M165VV738B KKN1455 TRD1550 TRD1620 BGO1800 BGO0030/1 BVG0230/1	ASM UTC RPL TEF9997/06APR24 J 738 C16M165VV738B OSL1455 BGO1550 BGO1630 KRS1730 KRS0255/1 LHR0855/1

RRT - Change of Routing

This sub-message changes only routing information (and its associated data elements) of a flight defined by a Flight Identifier.
The new routing must contain at least one Station from the previous routing. Stations common to both the previous and the new routings must appear in the same sequence.
The new routing, including timings, must be stated for all uncompleted legs of the flight. In order to avoid ambiguity regarding operational flights or flights scheduled to be in the operational phase, the Flight Leg(s) Change Identifier must be used to identify the flight leg(s) to be replaced by the schedule stated in the RRT message. If any of the above rules cannot be met then RPL must be used. For planning purposes, it is recommended that RPL be used.

Format of message:

The format of an ASM RRT message is as follows:

Standard Message Identifier
Time mode
Action Identifier
Flight designator/Date
Routing og Leg information (LEG NO 1)
Routing og Leg information (LEG NO 2)

Examples, single-leg (s-leg) and multi-leg (m-leg) flights, both domestic (dom), Schengen (sch) and Non-Schengen (non-s):

S-leg dom	M-leg dom past midnight	M-leg dom to non-s past midnight and Route change	Route change skip one airport
ASM UTC RRT TEF7999/04APR24 OSL1455 KRS1550	ASM UTC RRT TEF7998/02APR24 KKN1455 TOS1550 TOS1620 BGO1800 BGO0030/1 BVG0230/1	ASM UTC RRT TEF9997/06APR24 OSL1455 MOL1550 MOL1630 KRS1730 KRS0255/1 LHR0855/1	ASM UTC RRT TEF7998/02APR24 KKN1455 BGO1800 BGO0030/1 BVG0230/1

TIM - Change of Time Information

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.

Format of message:

The format of an ASM TIM message is as follows:

Standard Message Identifier
Time mode
Action Identifier
Flight designator/Date
Routing og Leg information (LEG NO 1)
Routing og Leg information (LEG NO 2)

Examples:

S-leg dom	M-leg dom past midnight
ASM UTC TIM TEF7999/04APR24 OSL1455 KRS1550	ASM UTC TIM TEF7998/02APR24 KKN1455 TOS1550 TOS1620 BGO1800 BGO0030/1 BVG0230/1

RIN - Reinstate Flight

This sub-message reinstates (i.e. declares as now operating again in the form and with the data in existence prior to the issuance of the last appropriate ASM/CNL messages) one or more flights or parts of the routing defined by Flight Identifier(s) and previously cancelled by an ASM/CNL sub-message. Only flights cancelled within 12 months of operating can be reinstated.
Any subsequent changes to the flight (e.g. routing, times, equipment) must be handled by an appropriate sub-message.

Format of message:

The format of an ASM RIN message is as follows:

Standard Message Identifier
Time mode
Action Identifier
Flight designator/Date

Example:

RIN Example
ASM UTC RIN TEF7999/04APR24

ADM - Change of Existing Information Expressed by the Use of Data Element Identifier Only

For a specific Flight designator/Period of Operation and day(s) of Operation this sub message changes only those data elements which are specified by the use of a Data Element Identifier.

•Other Periods of Operation/Day(s) of Operation remain unchanged

•When cancelling existing information the statement ‘NIL’ must be made

•If changes are leg related, replacement data need only be transmitted for legs where the data has changed. For example, in the case of Data Element Identifier 10, it is not necessary to transmit all legs that have Data Element Identifier 10 information, only those legs where DEI 10 needs changing

Note: When using multiple Action Identifiers, all formats for the combinations and, therefore, processing rules, are determined by the primary Action Identifier. Qualifying as secondary Action Identifiers are those that form a subset of the primary Action Identifier. Combinations with conflicting formats are not permitted, e.g. TIM-EQT. The secondary Action Identifier is intended for information purposes only i.e. human reading and understanding of changes.Consequently, the following combinations are permitted:

Primary Secondary

RPL ADM/CON/EQT/RRT/TIM
CON ADM
EQT ADM/CON
RRT ADM/CON/EQT/TIM
TIM ADM

Format of message:

The format of an ASM ADM message is as follows:

Standard Message Identifier
Time mode
Action Identifier
Flight designator/Date
OrigDest, Flight#, Airc.Type, Configuration, DEI 3 to 6

Example:

ADM example
ASM UTC ADM TEF7991/18NOV24 AMSSVG 952/J 73W C036M106 3/KL 4/KL 5/KL 6/KL1196/19NOV24 AMSSVG 953/AMS182010 SVG182140 AMSSVG 958/KL 73W

FLT - Change Flight Designator

This sub-message only changes the Flight Designator (and its associated data elements), and/or the Operational Suffix, for the Flight Identifier Date (and part of the routing, if stated). Other data elements, dates, and parts of the routing of the original Flight Designator and Operational Suffix are not affected.

Format of message:

The format of an ASM FLT message is as follows:

Standard Message Identifier
Time mode
Action Identifier
Flight designator/Date OLD, Flight designator/Date NEW

Example:

Change existing designator with new
ASM UTC FLT AIRS TEF7990/01DEC24 TEF7990R/01DEC24

CON- Change of Aircraft Configuration/Version

For a specific Flight designator/Period of Operation and day(s) of Operation this sub message changes only the Aircraft configuration Version 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.

Format of message:

The format of an ASM CON message is as follows:

Standard Message Identifier
Time mode
Action Identifier
Flight designator/Date
Service Type, Aircraft Type, Configuration, DEI 1 to 6
OrigDest, Flight#, Airc.Type, Configuration, DEI 1 to 6

Example:

Change existing configuration
ASM UTC CON TEF7989/20NOV24 J 73W C016M118.C036M106 3/TEF 4/TEF 5/TEF 6/TEF1188/20NOV24 AMSBGO 952/J 73W C036M106 3/TEF 4/TEF 5/TEF 6/TEF1188/20NOV24

EQT- Change of Equipment Information

For a specific Flight designator/Period of Operation and day(s) of Operation this sub message changes only the Aircraft configuration Version 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.

Format of message:

The format of an ASM EQT message is as follows:

Standard Message Identifier
Time mode
Action Identifier
Flight designator/Date
Service Type, Aircraft Type, Configuration, DEI 1 to 6
OrigDest, Flight#, Airc.Type, Configuration, DEI 1 to 6

Example:

Change existing equipment
ASM UTC EQT TEF7989/20NOV24 J 73W C016M118.C036M106 3/TEF 4/TEF 5/TEF 6/TEF1188/20NOV24 AMSSVG 953/AMS182010 SVG182140 AMSSVG 958/TEF PHBXC/TEF 73W

SSIM - Standard Schedule Information Message

The SSIM file contains a carriers complete flight schedule, not limited to, but preferably for one season. The SSIM file is specified in the IATA manual Standard Schedules Information Manual (SSIM), chapter 7.

ex_codeshare_3.sim

MVT - Movement Message

Information regarding departure and arrival times. MVT messages are defined in AHM 780.

Format of message:

The format of an MVT message is as follows:

MVT
Flight nummer
Aircraft Movement Information

– Departure Message
– Arrival Message
– Delay Message
– Delayed Take-off Message
– Return to Ramp Message
– Revised Estimated Time of Arrival Message
– Arrival Taxi Time Variance Information Message

Supplementary Information

Message Elements Status (M/C/O)
MANDATORY — the status of a data element, marked M, containing information that forms a fundamental part of the procedure and must always be included.
CONDITIONAL — the status of a data element, marked C, which becomes mandatory under certain circumstances which have to be specified. May be omitted if these circumstances do not prevail.
OPTIONAL — the status of a data element, marked O, which may be omitted if not required by the Carrier or Governmental regulations. Omission of this element is independent of all other elements and does not have any effect on other elements.
Note: For carriers own flight the optional elements need not be transmitted.

Element No.	M/C/O	Element	Format
1	M	Standard Message Identifier	MVT
2	M	New line, carriage return	<=
3	M	Flight Identifier, composed of maximum 11 characters	mm(a)fff(f)(a)/ff
3.1	M	Airline designator, 2–3 characters. The third character included for possible extension of the airline designator.	mm(a)
3.2	M	Flight Number with Optional Operational Suffix if applicable	fff(f)(a)
3.3	M	Scheduled UTC date of departure out of its initial point of departure of that flight number, oblique followed by two numerics which are included in the 11 characters of the flight identifier. Example: TEF347/12 or TEF347A/12 Note: A separator slash is required between Element 2.3 and the airline designator/flight number.	/ff
4	M	Aircraft registration 2–10 printable characters, preceded by a full stop. No hyphen to be transmitted. Note: When the aircraft registration is not known, (XXXXX) shall be shown for ED and NI messages.	.mm(m)(m)(m)(m)(m)(m)(m)(m)
DEP MSG
5	M	Departure Information is composed of maximum	AD(ff)ffff(/(ff)ffff)=
5.1	M	Departure Identifier	AD
5.2	M	Off-block time in four-digit time group or six-digit date/time group. Note: Date field in six-digit group refers to UTC date Of event. Note: Off-block time—time the aircraft commences to roll with its own or external power.	(ff)ffff
5.3	O	Airborne time in four-digit time group or six-digit date/time group preceded by an oblique. Note: Date field in six-digit group refers to UTC date of event. Example: AD1325 or AD1325/1332 or AD052355/060012	(/(ff)ffff)
6	C	Estimated Arrival (Touchdown) Information, composed of identifier EA and followed by the fourdigit time group or six-digit date/time group, space and airport of destination, IATA three-letter code. Mandatory for sectors scheduled in excess of three hours. Note: Element Nos. 5 and 6 to be on one line.	EA(ff)ffff=aaa<=
7	C	Actual Delay Information is composed of maximum 17 characters	DLmm(/mm)/ffff(/ffff)<=
7.1	C	Delay Identifier	DL
7.2	C	One delay reason—two character delay code followed by an oblique and four-digit group to shown duration of delay (hours and minutes).	mm/ffff
7.3	C	Two delay reasons—two character delay code for each delay and four-digit time groups for duration of each delay. All figure groups to be separated by obliques. Example: DL72/0120 or DL13/81/0020/0015 Note: Where more than two delay reasons apply use optional element 8.4 Additional Delay Information for additional delay codes.	mm/mm/ffff/ffff
8	O	Passenger Information Per Destination is composed of the Passenger Identifier PX and the number of seats occupied by passengers per destination, shown in sequence of routing commencing with the next station ahead. Figure groups to be separated by an oblique. Example: PX5 PX112 PX12/134/56	PXf(f)(f)(/f(f)(f))R[.N]<=
ARR MSG
9	M	Arrival Information is composed of maximum 15 characters	AA((ff)ffff/)(/(ff)ffff)<=
9.1	M	Arrival Identifier Note: Either element 9.2 or 9.3 or both shall be present.	AA
9.2	O	Touch-down time in a four-digit time group or six-digit date/time group.	((ff)ffff)
9.3	M	On-block time in a four-digit time group or six-digit date/time group preceded by an oblique. Example: AA1218/1225 or AA/1225 or AA032355/040005	(/(ff)ffff)
9.4	O	Flight Leg Date Indicator is composed of five characters. The identifier FLD followed by two digits to signify UTC Scheduled Date of Departure for Flight Leg. Example: FLD03	FLDff<=

Examples:

Descriptions

AD/EA

AA

Forced Return

NI

AD/EA/DL/PX/DLA

AD/EA/DL/PX/EDL/DLA

Syntax

MVT
TEF402/27.LNDIG.TRF
AD0410/0414 EA0459 BGO

MVT
TEF1196/26.LNDIG.AMS
AA0509/0513

MVT
TEF1234/18.LNDIG.BGO
FR0835/0840
SI BIRD STRIKE, PAX MOVED TO TEF1234R

MVT
TEF1234/18.LNDIG.BGO
NI180835
DLDT

MVT
TEF1751/26.LNDIG.IST
AD0427/0456 EA0821 OSL
DL89/0007
PX57
DLA89Z///
SIISTOSL
SENT ISTKLTK ISTGPTK OSLKZTK OSLTZTK

MVT
TEF778/18.LNDIG.FRA
AD2135/2152 EA190915 SIN
DL93/81/0015/0015
PX163/47
EDL11/73/0005/0005
DLA93B//11C/
SI OPERATING WITH RECLEARANCE FLT PLN

Comments

Operating TRF-BGO

In case of forced return, it is best for the original flight to be landed and any new flights for the same passengers to be created with a new flight number. This can be done for example by creating a new flight with the same flight id, but with a suffix. If possible, the SI element should give information about this.

In MAOS, reception of NI times will delete all estimated times for departure. Reception of new estimated times will delete NI times.

Next Information is composed of eight characters. The identifier NI is followed by two digits to indicate the UTC date and four digits for the UTC time group of the event.

DIV - Diversion Message

Diversion messages are described in AHM 730. DIV messages are information from airline/handler regarding changes in flight route, often because of bad weather, techincal problems or due to medical issues.

DIV messages for multileg flights must be preceeded by a reroute (RRT) message.

Format of message:

The format of a DIV message is as follows:

Standard Message Identifier
Flight designator/date.regnum.Original_destination
EstArr NewDest
DivReason NumPax

Example:

DIV example
DIV TEF0981/13.LNDIG.HFT EA0432 TOS DRWT PX023

LDM - Load Message

Message from airline/handler regarding load of aircraft. Very important for correct adjustment of weight on aircraft, for billing purposes on airport, and for the next airport to know how the aircraft is loaded.

Format of message:

The format of an LDM message is as follows:

Standard Message Identifier
Flight designator/date.Airreg.SubType.NumCrew Cockpit/Cabin
-Dest.PAX.Diverse info om last av flyet.
Supplementary Informatio

Example:

LDM Example
LDM TEF402/27.LNDIG.DH4.2/2 -BGO.47/0/0.T231.3/88.4/143.PAX/47 SI MESSAGE FROM PILOT null BGO BAG/231 CGO/0 MAIL/0

ADM/RAD - Administration/Revised Administration Message

Used for indicating Aircraft Registration used on flights.

Format of message:

Definitions:

a: single alphanumeric character

n: single numeric character

m: single alphanumeric or numeric character excluding special characters like "-" and "@"

x: free text, any character and special character

->: white Space

<=: linefeed and Carriage return

ADM/RAD (LETIS)

Data Element	Format	Data Element Example	Notes
Message Heading
Standard Message Identifier	ADM	ADM
Separator (Space)	->	Space
Scheduled GMT date of departure out of its originating station.	nnaaa(nn)	29MAR16	Optional Year (nn).
Separator (Space)	->	Space	Mandatory if the next element included
Sequence number	NRn(n)(n)	NR01	Mandatory for RAD
End of line	<=
Aircraft Type
Aircraft Type	x(x)...	DH1	Freetext
End of line	<=
Data Element	Format	Data Element Example	Notes
Aircraft Line
Aircraft registration	(aa)(aaa)	LNDIG	Optional Country (aa).
Separator (Space)	?	Space
Flight Identifier	aa(a)nnn(n)/nn	TEF001/29	Optional Airline Designator (aa) and Flight Identifier Date preceded by a slash (/)
Departure Station	aaa	OSL	Optional
Arrival Station	aaa	BGO	Mandatory if Departure station is assigned.
Standard Text	mmmmm(m)(m)(m)(m)(m)	FERRY or "VERCHG" or "BACK UP" or "MAINT" or "REPAIR" or "RESERVE"	Optional
Separator (Space)	?	Space	Mandatory if Standard Text is assigned.
Station	aaa	TOS	Mandatory if Standard Text is assigned.
Separator (Space)	?	Space	Mandatory if Standard Text FERRY is assigned.
Station	aaa	ALF	Mandatory if Standard Text FERRY is assigned.
Free Text	”(”x(x)...”)”	(ABCDEF)	Preceding with ”(” and ending with ”)”
End of line	<=

Examples:

ADM (Letis)

RAD (Letis)

ADM 25APR
DH1
LNABC TEF739 734 808 809 830 831 707 758 818 819
LNDEF
LNGHI TEF172 124 125 135 149 166
LNJKL
DH2
LNMNO TEF730 805 885 810 811 852 853 812 813 823

Example RAD (Letis):

RAD 24APR NR05
73H
LNPQR TEF1502 1503 1052 1053 414 417 1198
LNSTU TEF418
LNVWX TEF527 310 311 410 413 1108 1109 436

ADM/RAD (OPUS)

Element No.	M/C/O	Definition/Description	Format	Example
1	M	Message Type	RAD	RAD
2	M	Space	?
3	M	Origin Date	ffaaaff	22APR10
4	M	End of line	<=
5	M	Aircraft Registration	mm(m)(m)(m)(m)(m)(m)(m)(m)	LNDIG
6	M	End of line	<=
7	M	Flight Data	mm(a)fff(f)(a)/ff<=	TEF635
7.1	M	Airline Designator	mm(a)	TEF
7.2	M	Flight Number	fff(f)(a)	635
7.3	O	Flight Date	/ff	/23
7.4	M	Space	?
7.5	M	Departure Station	aaa	OSL
7.6	M	Space	?
7.7	M	Arrival station	aaa	CPH
7.8	M	End of line	<=

Examples:

ADM (OPUS)	RAD (OPUS)
ADM 25APR16 LNABC TEF4105 BOO OSL TEF255 OSL BGO TEF260 BGO OSL LNDEF TEF4561 TOS BOO TEF4561 BOO TRD TEF4556 TRD BOO	RAD 25APR16 LNGHI TEF2882 CPH TRD TEF2889 TRD CPH

IR1 - Requested Fuel

Fuel request message.

Format of message:

The format of an IR1 message is as follows:

Standard Message Identifier
Date
Flight_designator Destination FUEL

Example:

IR1
IR1 08JUL17 TEF175 OSL 13000

PLE - Passenger Load Estimate

This message is used to update passenger numbers.

Format of message:

The format of a PLE message is as follows:

Standard Message Identifier
Flight designator/date Field_description
Destination/STD
Origin PAX_count

Example:

PLE Example
PLE TEF201/14JUL19 C/Y/M/TOTL KRS/0700 OSL 13/0/91/104

KMBL - Passenger Load - Amadeus format

This message is used to update passenger numbers. KMBL is designed by Amadeus.

Element	M/C/O	Definition/Description	Format	Example
1	M	Message Identifier	KMBL	KMBL
2	M	Airline Designator	/AL-mm(a)	/AL-TEF
3	M	Flight Number	/FL-fff(f)(a)	/FL-635
4	M	Departure Date	/DT-ffaaaff	/DT-31MAR16
5	M	Title	MARKET ANALYSIS - BOOKINGS COUNT	MARKET ANALYSIS - BOOKINGS COUNT
6	M	Spaces	→
7	M	Date	DATE:→ffaaaff	DATE: 30MAR16
8	M	End Of Line	<≡
9	M	Header	FLT BRDOFF DEP EQP CS AD	FLT BRDOFF DEP EQP CS AD
10	M	Space	→
11	M	Class Header	CAP→→BKG(→CAP→→BKG) (→CAP→→BKG)	CAP BKG CAP BKG
12	M	End Of Line	<≡	End Of Line
13	M	Weekday	aa	TH
14	M	Space	→
15	M	Date	ffaaaff	31MAR16
16	M	Spaces	→*
17	M	Class Types (Capacity/Booked)	a→→→→a(→→→a→→→→a) (→→→a→→→→a)	Y Y M M
18	M	End Of Line	<≡
19	M	Airline Designator	mm(a)	TEF
20	O	Space	→	If Airline Designator is 2 characters
21	M	Flight	fff(f)(a)	635
22	O	Spaces	→*	If Flight Number is less than 5 characters
23	M	Departure	aaa	OSL
24	M	Arrival Station	aaa	ARN
25	M	Space	→
26	M	STD	ffff	1330
27	M	Spaces	→→→→
28	M	Aircraft Type	mmm	73C
29	M	Class Data (Capacity/Booked)	→→→→→
30	M	Class	n(n)(n)→n(n)(n)(→n(n)(n)→n(n)(n)) (→n(n)(n)→*n(n)(n))	166 71 20 14
31	M	End Of Line	<≡
32	M	Footer	REQUESTED AT:→→ffff→ffaaaff<≡	REQUESTED AT: 1700 30MAR16

Example:

KMBL Example	Description
KMBL/AL-TEF/FL-0968/DT-09JUL19 MARKET ANALYSIS – BOOKINGS COUNT DATE: 08JUL19 FLT BRDOFF DEP EQP CS AD CAP BKG TU 09JUL19 Y Y TEF0968 BGOCPH 1515 738 N 186 179 REQUESTED AT: 1515 08JUL19	Message Identifier/Airline Designator/Flight Number/Dep Date Title ->-> Date Header -> Class Header Weekday -> Date -> Class Types (Capacity/Booked) Airliine Designator -> Flight Number -> Dep Station -> Arr Station -> STD -> Aircraft Type -> Class Data (Capacity/booked) Footer

PRM - Passenger with Reduced Mobility

PRM messages can be one of three different types:

PAL Message : (Passenger Assistance List) This is sent automatically from airlines reservations systems, if there are no PRM passengers it will still be sent with a NIL value. You will get this 48 hours before the flight is scheduled to depart
CAL Message : (Change Assistance List) This is *only* sent if there is a change to the PAL message (late PRM bookings) *Because of this you will not always receive a CAL*
PSM Message : (Passenger Services Message) When an aircraft departs towards OSL, this message is sent. It's the actual PRM passengers on the flight who boarded. This is always sent, even if value is NIL

Here is an example of a PSM message for flight with route LHR-ARN-OSL:

PSM Example

PSM
TEF0710/04OCT LHR PART1
-ARN 3PAX / 4SSR
WCHR 000C 002Y
WCHS 000C 001Y
OTHS 000C 001Y
C CLASS NIL
M CLASS NIL
Y CLASS 3PAX / 4SSR
1LASTNAME/FIRSTNAMEMRS 12B
WCHR
1LASTNAME/FIRSTNAMEMS 14H
WCHS
1LASTNAME/FIRSTNAMEMR 25D
TEF161Y05GOT
OTHS
WCHR
-OSL 3PAX / 3SSR
WCHR 000C 001Y
WCHS 000C 001Y
NFST 000C 001Y
C CLASS NIL
M CLASS NIL
Y CLASS 3PAX / 3SSR
1LASTNAME/FIRSTNAMEMS 15J
TEF338Y05TRD
WCHS
1LASTNAME/FIRSTNAMEMR 16C
WCHR
1LASTNAME/FIRSTNAMEMR 19A
NFST
ENDPSM

PTM - Passenger Transfer Message

Message detailing what passengers will be transferred from one flight to another. If more then one part, this must be detailed, and END PARTn must be used.

Format of message:

The format of a PTM message is as follows:

Standard Message Identifier
Flight designator/date OrigDest PartNumber
Flight designator Dest PaxDesc NumBag Last/Firstname
Flight designator Dest PaxDesc NumBag Last/Firstname
Flight designator Dest PaxDesc NumBag Last/Firstname
Flight designator Dest PaxDesc NumBag Last/Firstname
Flight designator Dest PaxDesc NumBag Last/Firstname
Flight designator Dest PaxDesc NumBag Last/Firstname
ENDPTM

Example:

PTM
PTM TEF402/27APR TRFBGO PART1 TEF4144 AES 1C 0B KIN/STEIN TEF102 FRO 1M 0B BRE/ANDRE TEF102 FRO 1M 0B JOH/JONNY TEF102 FRO 1M 0B MCG/JUAN CUE TEF102 FRO 1M 1B WEG/GREG KRIST TEF392 ABZ 1M 1B PAN/PETE AGU ENDPTM