public byte[] ExtendedSquitterSupplementaryMessage { get; set; }

Public Property ExtendedSquitterSupplementaryMessage As Byte()
	Get
	Set

public:
property array<unsigned char>^ ExtendedSquitterSupplementaryMessage {
	array<unsigned char>^ get ();
	void set (array<unsigned char>^ value);
}

member ExtendedSquitterSupplementaryMessage : byte[] with get, set

Property Value

3.1.2.8.7.2 states that the control field determines the content of DF18 messages. If the control field is set to 0 (ControlField).AdsbDeviceTransmittingIcao24 then the Icao24 and ExtendedSquitterMessage properties are set and this field is null. Otherwise Icao24 is left at 0, ExtendedSquitterMessage is null and this property is filled with the ten bytes between the CF field and the PI field. I've labelled this as a MEX field in the ToString() description of the object but in reality the spec does not declare a name for the field and only describes the content for CF0 messages.

For DF19 messages the only messages that can potentially be decoded are those where the AF field is 0, although even this appears contentious. For all other message types the entire body of the message (which is likely to be encrypted) is placed in this block.

Reference