System Description

System Description and Installation Manual for MXS ICD10004-01
© Sagetech Corporation 2018 Confidential Proprietary Export-Controlled Page 37 of 160
3. Flight ID Message: Type 0x02
The Flight ID Message sets the Flight ID and, if used, it should be sent at least once every 5 seconds. If the Flight ID is
not received for 10 seconds, the transponder defaults to using the aircraft registration sent in the Installation Message.
This message is not commonly sent.
Note: It is not a requirement to use the Flight ID message.
An overview of the Flight ID Message is shown in Table 0-7Table 6-7. Table 0-8Table 6-8 provides the detailed message
definition. An example of a Flight ID Message is found in Table 0-9Table 6-9.
Table 0-7 Flight ID Message Payload Structure Overview
Payload Index Message Field Number bytes
0
Flight ID
8
8
Reserved
4
Table 0-8 Flight ID Message Payload Structure Detail
Flight ID
Byte Offset
Byte
Name
Field Description
00
FD0
FD0 FD1 FD2 FD3 FD4 FD5 FD6 FD7 Flight ID
01
FD1 0x4E 0x32 0x35 0x36 0x37 0x47 0x41 0x20 N2567GA
02
FD2
Flight ID Bytes
Set 64-bit Flight ID. If flight identification data is available, this is used in lieu of aircraft registration.
Flight ID (aircraft radio call sign) is used in the flight plan. Otherwise the transponder defaults to
aircraft registration data as set in the installation message. Up to eight ASCII characters can be entered.
Data is sent as unsigned chars and valid ASCII characters are outlined below:
Valid ASCII Hex Values
0x20 (Space)
0x30-0x39 (0-9)
0x41-0x5A (A-Z)
The most significant byte is sent first. The ASCII characters must be left-justified and the Flight ID may
not contain spaces. The Flight ID must be padded with space characters on the right. (For reference, see
DO-181d section 2.2.19.1.13).
If Flight ID is not available, fill this field with space characters (0x20). This will set Flight ID to “Not
Available” and Aircraft Registration will be used instead.
03
FD3
04
FD4
05
FD5
06
FD6
07
FD7