Publication: Magyar Közlöny
Issue: MK-2007-70 (Year: 2007, Number: 70)
Era: 2004-2010
Section: Melléklet a 2007. évi XLVI. törvényhez
Paragraph Index: 4455

b) Switching from low to high rate: Aircraft shall switch from low to high rate as soon as the aircraft’s position has changed by 10 metres or more since the low rate was selected For transponder-based implementations, the automatically selected transmission rate shall be subject to being overridden by commands received from ground control. TRANSMISSION RATE SUBFIELD (TRS) ALTITUDE TYPE SUBFIELD (ATS) RESERVED 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-99 28/11/02 No. 77 Table 2-8. BDS code 0,8 — Extended squitter aircraft identification and category MB FIELD PURPOSE: To provide aircraft identification and category. Note.— Since there is no internationally agreed criteria for wake vortex categorization, code 4 (set “A”) should be interpreted as indicating a medium category aircraft exhibiting higher than typical wake vortex characteristics. Format type shall be coded as follows: 1 = Identification, aircraft category set D 2 = Identification, aircraft category set C 3 = Identification, aircraft category set B 4 = Identification, aircraft category set A Aircraft/vehicle category shall be coded as follows: Set A 0 = No aircraft category information 1 = Light (<15 500 lbs or 7 031 kg) 2 = Medium 1 (15 500 to 75 000 lbs or 7 031 to 34 019 kg) 3 = Medium 2 (75 000 to 300 000 lbs or 34 019 to 136 078 kg) 4 = High vortex aircraft 5 = Heavy (>300 000 lbs or 136 078 kg) 6 = High performance (>5 g acceleration) and high speed (> 400 kt) 7 = Rotorcraft Set B 0 = No aircraft category information 1 = Glider/sailplane 2 = Lighter-than-air 3 = Parachutist/skydiver 4 = Ultralight/hang-glider/paraglider 5 = Reserved 6 = Unmanned aerial vehicle 7 = Space/transatmospheric vehicle Set C 0 = No aircraft category information 1 = Surface vehicle – emergency vehicle 2 = Surface vehicle – service vehicle 3 = Fixed ground or tethered obstruction 4 - 7 = Reserved Set D: Reserved Aircraft identification coding shall be: As specified in Table 2-32. FORMAT TYPE CODE (specified in 2.2.3.1) AIRCRAFT CATEGORY MSB CHARACTER 1 MSB CHARACTER 2 MSB CHARACTER 3 MSB CHARACTER 4 MSB CHARACTER 5 MSB CHARACTER 6 MSB CHARACTER 7 MSB CHARACTER 8 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-100 28/11/02 No. 77 Table 2-9a. BDS code 0,9 — Extended squitter airborne velocity (Subtypes 1 and 2: velocity over ground) MB FIELD MSB FORMAT TYPE CODE = 19 LSB SUBTYPE 1 SUBTYPE 2 INTENT CHANGE FLAG (specified in 2.3.5.3) IFR CAPABILITY FLAG NAVIGATION UNCERTAINTY CATEGORY – VELOCITY (NUCR) DIRECTION BIT for E-W velocity: 0 = East, 1 = West EAST-WEST VELOCITY NORMAL: LSB = 1 knot SUPERSONIC: LSB = 4 knots All zeros = no velocity information All zeros = no velocity information Value Velocity Value Velocity 0 kt 0 kt 1 kt 4 kt 2 kt 8 kt – – – – 1 022 1 021 kt 1 022 4 084 kt 1 023 >1 021.5 kt 1 023 >4 086 kt DIRECTION BIT for N-S Velocity, 0 = North, 1 = South NORTH-SOUTH VELOCITY NORMAL: LSB = 1 knot SUPERSONIC: LSB = 4 knots All zeros = no velocity information All zeros = no velocity information Value Velocity Value Velocity 0 kt 0 kt 1 kt 4 kt 2 kt 8 kt – – – – 1 022 1 021 kt 1 022 4 084 kt 1 023 >1 021.5 kt 1 023 >4 086 kt SOURCE BIT for vertical rate: 0 = GNSS, 1 = Baro SIGN BIT for vertical rate: 0 = Up, 1 = Down VERTICAL RATE All zeros = no vertical rate information; LSB = 64 ft/min Value Vertical rate 0 ft/min 64 ft/min – 32 576 ft/min >32 608 ft/min RESERVED FOR TURN INDICATOR GNSS ALT. SIGN BIT: 0 = Above baro alt, 1 = Below baro alt GNSS ALT. DIFFERENCE FROM BARO. ALT. All zeros = no information; LSB = 25 ft Value Difference 0 ft 25 ft – – 3 125 ft >3 137.5 ft PURPOSE: To provide additional state information for both normal and supersonic flight. Subtype shall be coded as follows: IFR capability shall be coded as follows: = Transmitting aircraft has no capability for ADS-B-based conflict detection or higher level applications. = Transmitting aircraft has capability for ADS-B-based conflict detection and higher level applications. NUC shall be coded as follows: Code Velocity Type Reserved Ground Speed Normal Supersonic Airspeed, Heading Normal Supersonic Reserved Reserved Reserved NUCR Horizontal Velocity Error (95%) Vertical Velocity Error (95%) Unknown Unknown <10 m/s <15.2 m/s (50 fps) <3 m/s <4.6 m/s (15 fps) <1 m/s <1.5 m/s (5 fps) <0.3 m/s <0.46 m/s (1.5 fps) 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-101 28/11/02 No. 77 Table 2-9b. BDS code 0,9 — Extended squitter airborne velocity (Subtypes 3 and 4: airspeed and heading) MB FIELD MSB FORMAT TYPE CODE = 19 LSB SUBTYPE 3 SUBTYPE 4 INTENT CHANGE FLAG (specified in 2.3.5.3) IFR CAPABILITY FLAG NAVIGATION UNCERTAINTY CATEGORY – VELOCITY (NUCR) STATUS BIT – 0 = Magnetic heading not available, 1 = available MSB = 180° MAGNETIC HEADING (specified in 2.3.5.5) LSB = 360/1 024° AIRSPEED TYPE: 0 = IAS, 1 = TAS AIRSPEED NORMAL: LSB = 1 knot SUPERSONIC: LSB = 4 knots All zeros = no velocity information All zeros = no velocity information Value Velocity Value Velocity 0 kt 0 kt 1 kt 4 kt 2 kt 8 kt – – – – 1 022 1 021 kt 1 022 4 084 kt 1 023 >1 021.5 kt 1 023 >4 086 kt SOURCE BIT FOR VERTICAL RATE: 0 = GNSS, 1 = Baro SIGN BIT FOR VERTICAL RATE: 0 = Up, 1 = Down VERTICAL RATE All zeros = no vertical rate information; LSB = 64 ft/min Value Vertical rate 0 ft/min 64 ft/min – – 32 576 ft/min >32 608 ft/min RESERVED FOR TURN INDICATOR DIFFERENCE SIGN BIT (0 = Above baro alt, 1 = Below baro alt) GEOMETRIC HEIGHT DIFFERENCE FROM BARO. ALT. All zeros = no information; LSB = 25 ft Value Difference 0ft 25 ft – – 3 125 ft >3 137.5 ft PURPOSE: To provide additional state information for both normal and supersonic flight based on airspeed and heading. This format shall only be used if velocity over ground is not available. Subtype shall be coded as follows: IFR capability shall be coded as follows: = Transmitting aircraft has no capability for ADS-B-based conflict detection or higher level applications. = Transmitting aircraft has capability for ADS-B-based conflict detection and higher level applications. Code Velocity Type Reserved Ground speed Normal Supersonic Airspeed, heading Normal Supersonic Reserved Reserved Reserved 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-102 28/11/02 No. 77 Table 2-10. BDS code 0,A — Extended squitter event-driven information MB FIELD PURPOSE: To provide a flexible means to squitter messages other than position, velocity and identification. 1) A message inserted in this register (or an equivalent transmit buffer) shall be broadcast once by the transponder at the earliest opportunity. 2) Formats for messages using this protocol shall be specified in BDS 6,1 to 6,F. 3) The GFM (2.5) shall be responsible for ensuring pseudorandom timing and for observing the maximum transmission rate for this register of 2 per second (2.5.5.1). 4) Read-out (if required) of this register shall be accomplished by extracting the contents of the appropriate BDS register 6,1 to 6,F. Note.— The data in this register is not intended for extraction using the GICB or ACAS cross-link protocols. 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-103 28/11/02 No. 77 Table 2-11. BDS code 0,B — Air/air state information 1 (aircraft state) MB FIELD PURPOSE: To report threat aircraft state information in order to improve the ability of ACAS to evaluate the threat and select a resolution manoeuvre. STATUS MSB = 1 024 kt TRUE AIR SPEED Range = [0-,2 047 kt] LSB = 1,0 kt SWITCH (0 = Magnetic heading, 1 = True heading) STATUS SIGN MSB = 90 degrees HEADING Range = [–180, + 179] LSB = 360/1 024 degrees STATUS SIGN MSB = 90 degrees TRUE TRACK ANGLE Range = [–180, +179] LSB = 360/32 768 degrees MSB = 1 024 kt GROUND SPEED Range = [0, 2 047] LSB = 1/16 kt RESERVED 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-104 28/11/02 No. 77 Table 2-12. BDS code 0,C — Air/air state information 2 (aircraft intent) MB FIELD PURPOSE: To provide threat aircraft intent information in order to improve the ability of ACAS to evaluate the threat and select a resolution manoeuvre. STATUS MSB = 51 200 ft LEVEL OFF ALTITUDE Range = [0, 102 375] LSB = 16 ft STATUS SIGN MSB = 90 degrees NEXT COURSE (TRUE GROUND TRACK) Range = [+179, –180] LSB = 360/1 024 degrees STATUS MSB = 128 seconds TIME TO NEXT WAYPOINT All ones = time exceeds 254 seconds Range = [0, 254] LSB = 1 second STATUS SIGN MSB 8 192 ft/min VERTICAL VELOCITY (UP IS POSITIVE) Range = [+16 352, –16 352] LSB = 32 ft/min STATUS SIGN MSB = 45 degrees ROLL ANGLE Range = [+89, –89] LSB = 360/256 degrees MIL INTERCEPT BIT (0 = no intercept; 1 = intercept) RESERVED 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-105 28/11/02 No. 77 Table 2-16. BDS code 1,0 — Data link capability report MB FIELD PURPOSE: To report the data link capability of the Mode S transponder/data link installation. The coding of this register shall conform to: 1) Annex 10, Volume III, 5.2.9. 2) When bit 25 is set to 1, it shall indicate that at least one Mode S specific service is supported and the particular capability reports shall be checked. Note.— Registers accessed by BDS codes 0,2; 0,3; 0,4; 1,0; 2,0 and 3,0 do not affect the setting of bit 25. 3) Starting from the MSB, each subsequent bit position shall represent the DTE subaddress in the range from 0 to 15. 4) The enhanced protocol indicator shall denote a Level 5 transponder when set to 1 and a Level 2 to 4 transponder when set to 0. 5) The squitter capability subfield (SCS) shall be interpreted as follows: = squitter registers are not updated = squitter registers are being updated 6) The surveillance identifier (SI) bit shall be interpreted as follows: = no surveillance identifier code capability = surveillance identifier code capability 7) Bit 36 shall be toggled each time the common usage GICB capability report (BDS code 1,7) changes. To avoid the generation of too many broadcast capability report changes, BDS code 1,7 shall be sampled at approximately one minute intervals to check for changes. 8) The current status of the on-board DTE shall be periodically reported to the GDLP by on-board sources. Since a change in this field results in a broadcast of the capability report, status inputs shall be sampled at approximately one minute intervals. 9) In order to determine the extent of any continuation of the data link capability report (into those registers reserved for this purpose: BDS 1,1 to BDS 1,6), bit 9 shall be reserved as a ‘continuation flag’ to indicate if the subsequent register shall be extracted. For example: upon detection of bit 9 = 1 in BDS 1,0 then BDS 1,1 shall be extracted. If bit 9 = 1 in BDS 1,1 then BDS 1,2 shall be extracted, and so on (up to BDS 1,5). Note that if bit 9 = 1 in BDS 1,6 then this shall be considered as an error condition. BDS code 1,0 Continuation flag (see 9) RESERVED Reserved for ACAS Mode S subnetwork version number Transponder enhanced protocol indicator (see 4) Mode S specific services capability (see 2) Uplink ELM capability Downlink ELM capability Aircraft identification capability Squitter capability subfield (SCS) (see 5) Surveillance identifier (SI) (see 6) Common usage GICB capability report (see 7) RESERVED FOR ACAS MSB Bit array indicating the support status of DTE subaddresses 0 to 15 (see 3 and 8) LSB 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-106 28/11/02 No. 77 Table 2-23. BDS code 1,7 — Common usage GICB capability report MB FIELD PURPOSE: To indicate common usage GICB services currently supported. 1) Each bit position shall indicate that the associated BDS is available in the aircraft installation when set to 1. 2) Registers 1,8 to 1,C shall be independent of register 1,7 All registers shall be constantly monitored at a rate consistent with their individual required update rate and the corresponding capability bit shall be set to 1 only when valid data is being input to that register at the required rate or above. The capability bit shall be set to a 1 if at least one field in the register is receiving valid data at the required rate with the status bits for all fields not receiving valid data at the required rate set to ZERO. 0,5 Extended squitter airborne position 0,6 Extended squitter ground position 0,7 Extended squitter status 0,8 Extended squitter type and identification 0,9 Extended squitter airborne velocity information 0,A Extended squitter event-driven information 2,0 Aircraft identification 2,1 Aircraft registration number 4,0 Aircraft intention 4,1 Next waypoint identifier 4,2 Next way-out position 4,3 Next way-out information 4,4 Meteorological routine report 4,5 Meteorological hazard report 4,8 VHF channel report 5,0 Track and turn report 5,1 Position coarse 5,2 Position fine 5,3 Air-referenced state vector 5,4 Waypoint 1 5,5 Waypoint 2 5,6 Waypoint 3 5,F Quasi-static parameter monitoring 6,0 Heading and speed report Reserved for aircraft capability Reserved for aircraft capability E,1 Reserved for Mode S byte E,2 Reserved for Mode S byte RESERVED 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-107 28/11/02 No. 77 Tables 2-24 to 2-28. BDS codes 1,8 to 1,C — Mode S specific services GICB capability reports MB FIELD PURPOSE: To indicate GICB services that are installed. Each bit position shall indicate that the GICB service that it represents has been implemented in the aircraft installation when set to 1. Starting from the LSB, each bit position shall represent the register number, in accordance with the following table: The 25 most significant bits of BDS 1,C shall not be used. MSB LSB BDS code Capability installed for BDS 1,8 BDS 1,9 BDS 1,A BDS 1,B BDS 1,C BDS 0,1 to 3,8 BDS 3,9 to 7,0 BDS 7,1 to A,8 BDS A,9 to E,0 BDS E,1 to F,F 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-108 28/11/02 No. 77 Tables 2-29 to 2-31. BDS codes 1,D to 1,F — Mode S specific services MSP capability reports MB FIELD PURPOSE: To indicate MSP services that are installed and require a service. Each bit shall indicate that the MSP it represents requires service when set to 1. Starting from the MSB, each bit position shall represent the MSP channel number for both uplink and downlink channel fields, in accordance with the following table: 1) In BDS 1,F the least significant bits of both uplink and downlink channel fields shall not be used. 2) The conditions for setting the capability bits shall be as defined in the specification of the corresponding service, see section 3. MSB UPLINK MSP CHANNELS LSB MSB DOWNLINK MSP CHANNELS LSB BDS code MSP channels BDS 1,D BDS 1,E BDS 1,F 1 to 28 up and down 29 to 56 up and down 57 to 63 up and down 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-109 28/11/02 No. 77 Table 2-32. BDS code 2,0 — Aircraft identification MB FIELD PURPOSE: To report aircraft identification to the ground. 1) Annex 10, Volume IV, 3.1.2.9. 2) The character coding to be used shall be identical to that defined in Table 3-6 of Chapter 3, Annex 10, Volume IV. 3) This data may be input to the transponder from sources other than the Mode S ADLP. 4) This format shall be used by the extended squitter application. 5) Capability to support this register shall be indicated by setting bit 33 in BDS 1,0 and the relevant bits in BDS 1,7 and 1,8. 6) The aircraft identification shall be that employed in the flight plan. When no flight plan is available the registration marking of the aircraft shall be used. BDS code 2,0 MSB CHARACTER 1 LSB MSB CHARACTER 2 LSB MSB CHARACTER 3 LSB MSB CHARACTER 4 LSB MSB CHARACTER 5 LSB MSB CHARACTER 6 LSB MSB CHARACTER 7 LSB MSB CHARACTER 8 LSB 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-110 28/11/02 No. 77 Table 2-33. BDS code 2,1 — Aircraft and airline registration markings MB FIELD PURPOSE: To permit ground systems to identify the aircraft without the necessity of compiling and maintaining continuously updated data banks. The character coding shall be as defined in Table 3-6 of Chapter 3, Annex 10, Volume IV. STATUS MSB CHARACTER 1 LSB MSB CHARACTER 2 LSB MSB CHARACTER 3 LSB MSB CHARACTER 4 AIRCRAFT REGISTRATION NUMBER LSB MSB CHARACTER 5 LSB MSB CHARACTER 6 LSB MSB CHARACTER 7 LSB STATUS MSB CHARACTER 1 LSB ICAO AIRLINE MSB REGISTRATION MARKING CHARACTER 2 LSB 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-111 28/11/02 No. 77 Table 2-34. BDS code 2,2 — Antenna positions MB FIELD PURPOSE: To provide information on the position of Mode S and GNSS antennas on the aircraft in order to make very accurate measurements of aircraft position possible. 1) The antenna type field shall be interpreted as follows: = Invalid = Mode S bottom antenna = Mode S top antenna = GNSS antenna 4 to 7 = Reserved 2) The X position field shall be the distance in metres along the aircraft centre line measured from the nose of the aircraft. The field shall be interpreted as invalid if the value is 0 and the value of 63 shall mean that the antenna position is 63 metres or more from the nose. 3) The Z position field shall be the distance in metres of the antenna from the ground, measured with the aircraft unloaded and on the ground. The field shall be interpreted as invalid if the value is 0 and the value 31 shall mean that the antenna position is 31 metres or more from the ground. ANTENNA TYPE MSB = 32 m X POSITION Range = [1,63] ANTENNA 1 LSB = 1 m MSB = 16 m Z POSITION Range = [1,31] LSB = 1 m ANTENNA TYPE MSB = 32 m X POSITION Range = [1, 63] ANTENNA 2 LSB = 1 m MSB = 16 m Z POSITION Range = [1, 31] LSB = 1 m ANTENNA TYPE MSB = 32 m X POSITION Range = [1, 63] ANTENNA 3 LSB = 1 m MSB = 16 m Z POSITION Range = [1, 31] LSB = 1 m ANTENNA TYPE MSB = 32 m X POSITION Range = [1, 63] ANTENNA 4 LSB = 1 m MSB = 16 m Z POSITION Range = [1, 31] LSB = 1 m 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-112 28/11/02 No. 77 Table 2-37. BDS code 2,5 — Aircraft type MB FIELD PURPOSE: To provide information on aircraft type. 1) Subfield coding The coding shall be as in Doc 8643 — Aircraft Type Designators. All the subfields that contain characters shall be encoded using the 6-bit subset of 1A-5 as specified in Table 3-6 of Annex 10, Volume IV. 2) Model designation Coding shall consist of four characters as specified in Doc 8643. The fifth character shall be reserved for future expansion and shall contain all zeros until it is specified. 2222 in the first four characters shall mean that the designator is not specified. 3) Number of engines This subfield shall be encoded as a binary number where number 7 means 7 or more engines. MSB AIRCRAFT TYPE LSB MSB NUMBER OF ENGINES LSB MSB ENGINE TYPE LSB MSB CHARACTER 1 LSB MSB CHARACTER 2 LSB MSB CHARACTER 3 MODEL DESIGNATION LSB MSB CHARACTER 4 LSB MSB CHARACTER 5 LSB MSB WAKE TURBULENCE CATEGORY LSB RESERVED 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-113 28/11/02 No. 77 Table 2-48. BDS code 3,0 — ACAS active resolution advisory MB FIELD PURPOSE: To report resolution advisories (RAs) generated by ACAS equipment. The coding of this register shall conform to: 1) Annex 10, Volume IV, 4.3.8.4.2.2. 2) Bit 27 shall mean RA terminated when set to 1. BDS code 3,0 ACTIVE RESOLUTION ADVISORIES RACs RECORD RA TERMINATED MULTIPLE THREAT ENCOUNTER THREAT-TYPE INDICATOR THREAT IDENTITY DATA 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-114 28/11/02 No. 77 Table 2-64 BDS 4,0 — Selected Vertical Intention MB FIELD PURPOSE: To provide ready access to information about the pilot’s current vertical intentions, in order to improve the effectiveness of conflict probes and to provide additional tactical information to controllers. 1) Target altitude shall be the short-term intent value, at which the aircraft will level off (or has levelled off) at the end of the current manoeuvre. The data source that the aircraft is currently using to determine the target altitude shall be indicated in the altitude source bits (54 to 56) as detailed below. Note.— This information which represents the real “aircraft intent”, when available, represented by the altitude control panel selected altitude, the flight management system selected altitude, or the current aircraft altitude according to the aircraft’s mode of flight (the intent may not be available at all when the pilot is flying the aircraft). 2) The data entered into bits 1 to 13 shall be derived from the mode control panel/flight control unit or equivalent equipment. Alerting devices may be used to provide data if it is not available from “control” equipment. The associated mode bits for this field (48 to 51) shall be as detailed below. 3) The data entered into bits 14 to 26 shall be derived from the flight management system or equivalent equipment managing the vertical profile of the aircraft. 4) The current barometric pressure setting shall be calculated from the value contained in the field (bits 28 to 39) plus 800 mb. When the barometric pressure setting is less than 800 mb or greater than 1 209.5 mb, the status bit for this field (bit 27) shall be set to indicate invalid data. 5) Bits 48 to 56 shall indicate the status of the values provided in bits 1 to 26 as follows: Bit 48 shall indicate whether the mode bits (49, 50 and 51) are actively being populated: = No mode information provided = Mode information deliberately provided Bits 49, 50 and 51: = Not active = Active Bit 54 shall indicate whether the target altitude source bits (55 and 56) are actively being populated. = No source information provided = Source information deliberately provided Bits 55 and 56, shall indicate target altitude source: 00 = Unknown 01 = Aircraft altitude 10 = FCU/MCP selected altitude 11 = FMS selected altitude STATUS MSB = 32 768 ft MCP/FCU SELECTED ALTITUDE Range = 0 to 65 520 ft (Resolution) LSB = 16 ft (Resolution) STATUS MSB = 32 768 ft FMS SELECTED ALTITUDE Range = 0 to 65 520 ft LSB = 16 ft (Resolution) STATUS MSB = 204.8 mb Range = 0 to 409.5 mb BAROMETRIC PRESSURE SETTING MINUS 800 mb LSB = 0.1 mb (Resolution) RESERVED STATUS OF MCP/FCU MODE BITS VNAV MODE ALT HOLD MODE APPROACH MODE RESERVED STATUS OF TARGET ALT SOURCE BITS TARGET ALTITUDE SOURCE TARGET ALTITUDE SOURCE 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-115 28/11/02 No. 77 Tables 2-65 to 2-67. BDS codes 4,1 to 4,3 — Next waypoint details PURPOSE: To provide ready access to details about the next waypoint on an aircraft’s route, without the need to establish a data link dialogue with the flight management system. This will assist with short- and medium-term tactical control. Register BDS code 4,1 contains 9 characters in the compressed 6-bit character form giving the waypoint name. BDS code 4,1 MB FIELD BDS code 4,2 MB FIELD BDS code 4,3 MB FIELD STATUS STATUS STATUS MSB SIGN SIGN MSB = 90 degrees MSB = 90 degrees CHARACTER 1 BEARING TO WAYPOINT LSB MSB WAYPOINT LATITUDE CHARACTER 2 Range = [–180, +180] LSB = 360/2 048 degrees LSB STATUS MSB Range = [–180, +180] MSB = 204.8 min CHARACTER 3 TIME TO GO LSB MSB LSB = 90/131 072 degrees STATUS CHARACTER 4 SIGN MSB = 90 degrees Range = [0,409.6] LSB LSB = 0.1 min MSB STATUS MSB = 3 276.8 NM CHARACTER 5 WAYPOINT LONGITUDE LSB MSB DISTANCE TO GO CHARACTER 6 Range = [–180, +180] LSB MSB Range = [0, 6 553.6] CHARACTER 7 LSB = 90/131 072 degrees STATUS SIGN LSB = 0.1 NM LSB MSB = 65 536 ft MSB CHARACTER 8 WAYPOINT CROSSING ALTITUDE LSB MSB RESERVED CHARACTER 9 Range = [0, 131 068] LSB RESERVED LSB = 8 ft 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-116 28/11/02 No. 77 Table 2-68. BDS code 4,4 — Meteorological routine air report MB FIELD PURPOSE: To allow meteorological data to be collected by ground systems. FOM/SOURCE coding: The decimal value of the binary coded (figure of merit) FOM/SOURCE parameter shall be interpreted as follows: = Invalid = INS = GNSS = DME/DME = VOR/DME 5 to 15 = Reserved 1) The interpretation of the two bits assigned to TURBULENCE shall be as shown in the table for BDS code 4,5. Note.— The average static pressure is not a requirement of ICAO Annex 3. FOM/SOURCE STATUS (wind speed and direction) MSB = 256 kt WIND SPEED Range = [0, 512] LSB = 1 kt SIGN MSB = 90 degrees WIND DIRECTION (True) Range = [–180, +180] LSB = 180/256 degrees STATUS SIGN MSB = 64°C STATIC AIR TEMPERATURE Range = [–128, +128] LSB = 0.25° STATUS MSB = 1 024 hPa AVERAGE STATIC PRESSURE Range = [0,2 048] LSB = 1 hPa STATUS TURBULENCE (see 1) STATUS MSB = 100% Range = [0, 100] HUMIDITY LSB = 100/64% 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-117 28/11/02 No. 77 Table 2-69. BDS code 4,5 — Meteorological hazard report MB FIELD PURPOSE: To provide reports on the severity of meteorological hazards, in particular for low flight. Hazard coding: The interpretation of the two bits assigned to each hazard shall be as defined in the table below: The definition of the terms LIGHT, MODERATE and SEVERE shall be those defined in the PANS-ATM (Doc 4444), where applicable. STATUS TURBULENCE STATUS WIND SHEAR STATUS MICROBURST STATUS ICING STATUS WAKE VORTEX STATUS SIGN MSB = 64°C STATIC AIR TEMPERATURE Range = [–128, +128] LSB = 0.25°C STATUS MSB = 1 024 hPa AVERAGE STATIC PRESSURE Range = [0, 2 048] LSB = 1 hPa STATUS MSB = 32 768 ft RADIO HEIGHT Range = [0, 65 528] LSB = 16 ft RESERVED Bit 1 Bit 2 NIL LIGHT MODERATE SEVERE 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-118 28/11/02 No. 77 Table 2-72. BDS code 4,8 — VHF channel report MB FIELD PURPOSE: To allow the ATC system to monitor the settings of the VHF communications channel and to determine the manner in which each channel is being monitored by the aircrew. Channel report coding: Each VHF communications channel shall be determined from the 15-bit positive binary number, N in kHz, according to the formula. Channel (MHz ) = Base + N × 0.001 (MHz) where Base = 118.000 MHz Notes.— 1) The use of binary to define the channel improves the coding efficiency. 2) This coding is compatible with analogue channels on 25 kHz, 8.33 kHz channel spacing and VDL as described below. 3) VDL has a full four bits allocated such that the active status of each of its four multiplex channels can be ascertained. 25 kHz VDL: Mode 3 25 kHz analogue 8.33 kHz analogue Audio status coding: Each pair of audio status bits shall be used to describe the aircrew monitoring of that audio channel according to the following table: VHF 1 STATUS VHF 1 AUDIO STATUS VHF 2 STATUS VHF 2 AUDIO STATUS VHF 3 STATUS VHF 3 AUDIO STATUS 121.5 MHz AUDIO STATUS Bit Status MSB (12 800 kHz) ... range 118.000 to 143.575 136.975 (military uses) LSB (25 kHz) 4 × channel active flags VDL indicator = 1 Bit Status MSB (12 800 kHz) ... range 118.000 to 143.575 136.975 (military uses) LSB (25 kHz) unused unused unused 8.33 indicator = 0 VDL indicator = 0 Bit Status MSB (17 066 kHz) ... range 118.000 to 152.112 136.975 (military uses) LSB (17 066/2 048 kHz) unused 8.33 indicator = 1 VDL indicator = 0 Bit 1 Bit 2 UNKNOWN NOBODY HEADPHONES ONLY LOUDSPEAKER 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-119 28/11/02 No. 77 Table 2-80. BDS code 5,0 — Track and turn report MB FIELD PURPOSE: To provide track and turn data to the ground systems. 1) The maximum acceptable data age at time of transmission to the ground shall be 1 second for all parameters. 2) The register update rate shall be sufficient to ensure that the maximum acceptable data age of all parameters is not exceeded in normal operations. 3) If maximum acceptable data age is exceeded for any parameter, then the status bit for that parameter shall be actively set to 0 by the GFM. Note.— This applies if any parameter becomes unavailable due to abnormal operations. 4) If the value of a parameter from the data source exceeds the range allowable in the register definition, the maximum allowable value in the correct positive or negative sense shall be used instead. Note.— This requires active intervention by the GFM. 5) The data entered into this register shall, whenever possible, be derived from the sources that are controlling the aircraft. 6) If any parameter is not available on an aircraft, all bits corresponding to that parameter shall be actively set to 0 by the BDS servicing process. 7) The LSB of all fields shall be obtained by rounding. STATUS SIGN 1 = Left (left wing down) MSB = 45 degrees ROLL ANGLE Range = [–90, +90] LSB = 45/256 degrees STATUS SIGN 1 = West (e.g. 315° = –45°) MSB = 90 degrees TRUE TRACK ANGLE Range = [–180, +180] LSB = 90/512 degrees STATUS MSB = 1 024 kt GROUND SPEED Range = [0, 2 046] LSB = 1 024/512 kt STATUS SIGN 1 = Minus MSB = 8 degrees/second TRACK ANGLE RATE Range = [–16, +16] LSB = 8/256 degrees/second STATUS MSB = 1 024 kt TRUE AIRSPEED Range = [0, 2 046] LSB = 1 023/512 kt 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-120 28/11/02 No. 77 Table 2-81. BDS code 5,1 — Position report coarse MB FIELD PURPOSE: To provide a three-dimensional report of aircraft position. 1) The single status bit (bit 1) shall be set to 0 if any of the three parameters are invalid and is identical to the status bit in BDS 5,2. 2) The required valid range for latitude is +90 degrees to –90 degrees, but the parameter shall be coded with an MSB of 90 degrees to allow the use of the same coding algorithm as for longitude. 3) The source of the information in this register shall be the same as that indicated in the FOM/SOURCE field of BDS 5,2. STATUS (see 1) SIGN MSB = 90 degrees LATITUDE Range = [–180, +180] (see 2) LSB = 360/1 048 576 degrees SIGN MSB = 90 degrees LONGITUDE Range = [–180, +180] LSB = 360/1 048 576 degrees SIGN MSB = 65 536 ft PRESSURE ALTITUDE Range = [–1 000, +126 752] LSB = 8 ft 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-121 28/11/02 No. 77 Table 2-82. BDS code 5,2 — Position report fine MB FIELD PURPOSE: To provide a high-precision three-dimensional report on aircraft position when used in conjunction with BDS 5,1. Information on the source of the data is included. FOM/SOURCE coding: The decimal value of the binary-coded (figure of merit) FOM/SOURCE parameter shall be interpreted as follows: = Loss of navigational capability = RNP 20 (e.g. INS data) pressure altitude = RNP 5 (e.g. VOR/DME) pressure altitude = RNP 1 (e.g. DME/DME or GNSS) pressure altitude = Reserved for differential GNSS (circular position error (CPE) 10 m) pressure altitude = Reserved for differential GNSS (CPE 2.5 m) pressure altitude 6-10 = Reserved = RNP 1 (e.g. DME/DME or GNSS) GNSS height = Reserved for differential GNSS (CPE 10 m) height = Reserved for differential GNSS (CPE 2.5 m) height 14-15 = Reserved Note.— RNP signifies required navigation performance. Suitable RNP categories have not yet been defined for values below 1; therefore, CPE is used. 1) The single status bit (bit 1) shall be set to 0 if any of the three parameters are invalid and is identical to the status bit in BDS 5,1. 2) The LATITUDE (fine) and LONGITUDE (fine) parameters are in 2’s complement coding so they shall be interpreted in conjunction with the corresponding parameters in BDS 5,1. Note.— When GNSS height is contained in bits 42 to 56, the pressure altitude can be obtained from BDS 5,1. STATUS (see 1) FOM/SOURCE MSB = 90/128 degrees LATITUDE FINE Range = [0, 180/128] LSB = 90/16 777 216 degrees MSB = 90/128 degrees LONGITUDE FINE Range = [0, 180/128] LSB = 90/16 777 216 degrees SIGN MSB = 65 536 ft PRESSURE ALTITUDE or GNSS HEIGHT (HAE) Range = [–1 000, 126 752] LSB = 8 ft 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-122 28/11/02 No. 77 Table 2-83. BDS code 5,3 — Air-referenced state vector MB FIELD PURPOSE: To provide the ATC system with the current measured values of magnetic heading IAS/Mach, altitude rate and TAS. STATUS SIGN MSB = 90 degrees MAGNETIC HEADING Range = [–180, +180] LSB = 90/512 degrees STATUS MSB = 512 kt INDICATED AIRSPEED (IAS) Range = [0, 1 024] LSB = 1 kt STATUS MSB = Mach 2.048 MACH NUMBER Range = [0, 4.096] LSB = Mach 0.008 STATUS MSB = 1 024 kt TRUE AIRSPEED (TAS) Range = [0, 2 048] LSB = 0,5 kt STATUS SIGN MSB = 8 192 ft/min ALTITUDE RATE Range = [–16 384, +16 384] LSB = 64 ft/min 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-123 28/11/02 No. 77 Table 2-84 to 2-86. BDS codes 5,4 to 5,6 — Waypoints 1, 2 and 3 MB FIELD PURPOSE: To provide information on the next three waypoints. BDS 5,4 contains details of the next waypoint, BDS 5,5 contains details of the next waypoint plus 1, and BDS 5,6 contains details of the next waypoint plus 2. 1) The single status bit (bit 1) shall be set to 0 if any of the parameters are invalid. 2) The estimated time or flight level shall be calculated from the trajectory scheduled in the FMS. Note.— More detailed information on the next waypoint is given in BDS 4,1 to 4,3. 3) When the waypoint identity has only three characters, two leading 0 characters shall be added (e.g. CDN becomes 00CDN). 4) Estimated time is in minutes and a value of all ones shall be used to indicate that the waypoint referred to is more than one hour away. STATUS (see 1) MSB CHARACTER 1 LSB MSB CHARACTER 2 LSB MSB CHARACTER 3 LSB MSB CHARACTER 4 LSB MSB CHARACTER 5 LSB MSB = 30 min ESTIMATED TIME OF ARRIVAL (NORMAL FLIGHT) Range = [0, 59] LSB = 60/512 min MSB = 320 ESTIMATED FLIGHT LEVEL (NORMAL FLIGHT) Range = [0, 640] LSB = 10 MSB = 30 min TIME TO GO (DIRECT ROUTE) Range = [0, 59] LSB = 60/512 min RESERVED 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-124 28/11/02 No. 77 Table 2-95. BDS code 5,F — Quasi-static parameter monitoring MB FIELD PURPOSE: To permit the monitoring of changes in parameters that do not normally change very frequently, i.e. those expected to be stable for 5 minutes or more by accessing a single register. Parameter monitor coding: The changing of each parameter shall be monitored by 2 bits. The value 00 shall indicate that no valid data are available on this parameter. The decimal value for this 2-bit field shall be cycled through 1,2 and 3, each step indicating a change in the monitored parameter. The meteorological hazards subfield shall report changes to turbulence, wind shear, wake vortex, icing and microburst, as in register number 4516. SELECTED ALTITUDE SELECTED HEADING SELECTED SPEED SELECTED MACH NUMBER SELECTED ALTITUDE RATE SELECTED FLIGHT PATH ANGLE NEXT WAYPOINT FMS HORIZONTAL MODE FMS VERTICAL MODE VHF CHANNEL REPORT METEOROLOGICAL HAZARDS TARGET ALTITUDE RESERVED 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-125 28/11/02 No. 77 Table 2-96. BDS code 6,0 — Heading and speed report MB FIELD PURPOSE: To provide heading and speed data to ground systems. 1) The maximum acceptable data age at time of transmission to the ground shall be 1 second for all parameters. 2) The register update rate shall be sufficient to ensure that the maximum acceptable data age of all parameters is not exceeded in normal operations. 3) If maximum acceptable data age is exceeded for any parameter, then the status bit for that parameter shall be actively set to 0 by the GFM. 4) If the value of a parameter from the data source exceeds the range allowable in the register definition, the maximum allowable value in the correct positive or negative sense shall be used instead. Note.— This requires active intervention by the GFM. 5) The data entered into this register shall, whenever possible, be derived from the sources that are controlling the aircraft. 6) All parameters shall be required except for inertial vertical velocity which shall be supplied only by aircraft with a suitable inertial source. If inertial vertical velocity is not available, bits 46 to 56 inclusive shall be actively set to 0 by the GFM. 7) The LSB of all fields shall be obtained by rounding. STATUS SIGN 1 = West (e.g. 315° = –45°) MSB = 90 degrees MAGNETIC HEADING Range = [–180, +180] LSB = 90/512 degrees STATUS MSB = 512 kt INDICATED AIRSPEED Range = [0, 1 023] LSB = 512/512 = 1 kt STATUS MSB = 2.048 MACH Range = [0, 4.096] LSB = 2.048/512 STATUS SIGN 1 = Below MSB = 8 192 ft/min BAROMETRIC ALTITUDE RATE Range = [–16 384, +16 352] LSB = 8 192/256 = 32 ft/min STATUS SIGN 1 = Below MSB = 8 192 ft/min INERTIAL VERTICAL VELOCITY Range = [–16 384, +16 352] LSB = 8 192/256 = 32 ft/min 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-126 28/11/02 No. 77 Table 2-97. BDS code 6,1 — Emergency/priority status MB FIELD PURPOSE: To provide additional information on aircraft status. Subtype shall be coded as follows: = No information = Emergency/priority status 2 to 7 = Reserved Emergency/priority status shall be coded as follows: 1) Message delivery shall be accomplished once per second using the event-driven protocol. 2) Termination of emergency state shall be detected by coding in the surveillance status field of the airborne position message. FORMAT TYPE CODE = 28 SUBTYPE CODE = 1 EMERGENCY/PRIORITY STATUS RESERVED Value Meaning No emergency General emergency Lifeguard/Medical Minimum fuel No communications Unlawful interference Reserved Reserved 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-127 28/11/02 No. 77 Table 2-98/99. BDS codes 6,2/6,3 — Current/next trajectory change point (TCP/TCP+1) MB FIELD FORMAT TYPE CODE = 29 TCP Type (0 = current, 1 = next) TRAJECTORY POINT/LEG TYPE (See 2.3.9.3) TCP DATA VALID (0 = invalid, 1 = valid) TCP Format (0 = 4D TCP) TCP Format (1 = 3D TCP) MSB MSB TCP/TCP+1 TCP/TCP+1 ALTITUDE ALTITUDE (See 2.3.9.6) (See 2.3.9.6) LSB LSB MSB = 180 degrees MSB = 180 degrees TCP/TCP+1 TCP/TCP+1 LATITUDE LATITUDE (CPR even format coding) (Angular weighted binary coding) (See 2.3.9.7.1) (See 2.3.9.7.2) LSB MSB TCP/TCP+1 LONGITUDE LSB = 2–17 x 360 degrees (CPR even format coding) MSB = 180 degrees TCP/TCP+1 (See 2.3.9.8.1) LONGITUDE (Angular weighted binary coding) (See 2.3.9.8.2) LSB MSB TCP/TCP+1 TIME-TO-GO (TTG) (See 2.3.9.9) LSB LSB = 2–17 x 360 degrees PURPOSE: To provide aircraft intent as defined by the current or next trajectory change point. 1) Message delivery shall be accomplished using the event-driven protocol. 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-128 28/11/02 No. 77 Table 2-100. BDS code 6,4 — Aircraft operational coordination message MB FIELD PURPOSE: To provide the current state of the various aircraft parameters required to support operational applications, particularly those involving paired aircraft. 1) Message delivery shall be accomplished using the event-driven protocol. FORMAT TYPE CODE = 30 SUBTYPE CODE = 0 MSB PAIRED ADDRESS (specified in 2.3.10.3) LSB MSB RUNWAY THRESHOLD SPEED (specified in 2.3.10.4) LSB ROLL ANGLE SIGN BIT (specified in 2.3.10.5) MSB ROLL ANGLE (specified in 2.3.10.6) LSB GO-AROUND (specified in 2.3.10.7) ENGINE-OUT (specified in 2.3.10.8) RESERVED 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-129 28/11/02 No. 77 Table 2-101. BDS code 6,5 — Aircraft operational status MB FIELD PURPOSE: To provide the capability class and current operational mode of ATC-related applications on board the aircraft. 1) Message delivery shall be accomplished using the event-driven protocol. MSB FORMAT TYPE CODE = 31 LSB MSB SUBTYPE CODE = 0 LSB MSB EN-ROUTE OPERATIONAL CAPABILITIES (CC-4) (specified in 2.3.11.3) LSB MSB TERMINAL AREA OPERATIONAL CAPABILITIES (CC-3) LSB (specified in 2.3.11.4) MSB APPROACH/LANDING OPERATIONAL CAPABILITIES (CC-2) LSB (specified in 2.3.11.5) MSB SURFACE OPERATIONAL CAPABILITIES (CC-1) (specified in 2.3.11.6) LSB MSB EN-ROUTE OPERATIONAL CAPABILITY STATUS (OM-4) LSB (specified in 2.3.11.7) MSB TERMINAL AREA OPERATIONAL CAPABILITY STATUS (OM-3) LSB (specified in 2.3.11.8) MSB APPROACH/LANDING OPERATIONAL CAPABILITY STATUS (OM-2) LSB (specified in 2.3.11.9) MSB SURFACE OPERATIONAL CAPABILITY STATUS (OM-1) LSB (specified in 2.3.11.10) RESERVED 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-130 28/11/02 No. 77 Table 2-241. BDS code F,1 — Military applications MB FIELD PURPOSE: To provide data in support of military applications. 1) The character field shall be used to indicate whether 2 characters or 4 characters are used in the Mode 1 code. The logic shall be as follows: 0 = 2 octal codes (A1-A4 and B1-B4) 1 = 4 octal codes (A1-A4, B1-B4, C1-C4 and D1-D4) 2) The status fields shall be used to indicate whether the data are available or unavailable. The logic shall be as follows: 0 = Unavailable 1 = Available STATUS Character Field (see 1) C1 A1 C2 A2 C4 A4 MODE 1 CODE X B1 D1 B2 D2 B4 D4 STATUS C1 A1 C2 A2 C4 A4 MODE 2 CODE X B1 D1 B2 D2 B4 D4 RESERVED 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-131 28/11/02 No. 77 Table 2-242. BDS code F,2 — Military applications MB FIELD PURPOSE. This register is used for military applications involving DF=19. Its purpose is to provide data in support of military applications. ‘TYPE CODE’ shall be encoded as follows: 0 = Mode code information 1 – 31 = Unassigned 1) The character field shall be used to indicate whether 2 characters or 4 characters are used in the Mode 1 code. The logic shall be as follows: 0 = 2 octal codes (A1-A4 and B1-B4) 1 = 4 octal codes (A1-A4, B1-B4, C1-C4, and D1-D4) 2) The status fields shall be used to indicate whether the data are available or unavailable. The logic shall be as follows: 0 = Unavailable 1 = Available TYPE CODE = 0 STATUS Character Field (see 1) C1 A1 C2 A2 C4 A4 X MODE 1 CODE B1 D1 B2 D2 B4 D4 STATUS C1 A1 C2 A2 C4 A4 X MODE 2 CODE B1 D1 B2 D2 B4 D4 STATUS C1 A1 C2 A2 C4 A4 X MODE A CODE B1 D1 B2 D2 B4 D4 RESERVED 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-132 28/11/02 No. 77 3. FORMATS FOR MODE S SPECIFIC PROTOCOLS (MSP) 3.1 MSP CHANNEL NUMBER ALLOCATIONS The details of protocols and data transfers shall be as specified in the following paragraphs. Note.— Some MSP channel numbers have been assigned (see Chapter 5, Table 5-25). 3.2 UPLINK MSP CHANNELS The following sections are numbered 3.2.X, where ‘X’ is the decimal equivalent of the uplink MSP channel number. This shall be done to allow definitions of the hitherto undefined formats to be inserted without affecting the paragraph numbers. For MSP packet formats refer to Chapter 5. 3.2.1 UPLINK MSP CHANNEL 1 (Reserved for specific services management) The description of this channel has not yet been developed. 3.2.2 UPLINK MSP CHANNEL 2 (Traffic information service (TIS)) 3.2.2.1 PURPOSE The TIS shall have the capability to generate automatic alert information on any aircraft that carries an operating transponder (Mode A/C or Mode S) or aircraft that are under primary radar tracking integrated with the SSR system. Note.— The traffic information service (TIS) is intended to improve the safety and efficiency of “see and avoid” flight by providing the pilot with an automatic display of nearby traffic and warnings of any potentially threatening traffic conditions. The TIS is functionally equivalent to ACAS I, providing traffic advisories but no resolution advisory information. By utilizing the surveillance database maintained by Mode S ground interrogators and its data link, the TIS can provide airborne traffic alerting with a minimum airborne equipage requirement. The TIS is provided without any ATC involvement. 3.2.2.2 TIS UPLINK MESSAGE FORMATS All TIS uplink messages shall be structured as shown below. Each TIS uplink message shall be 56 bits. TIS traffic data messages shall consist of one or more short-form MSP packets. There shall be three types of TIS uplink messages as follows: 1) “Keep-alive” 2) “Goodbye” 3) “Traffic data” Header Message type Traffic block 1 Traffic block 2 8 bits 6 bits 21 bits 21 bits 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-133 28/11/02 No. 77 Note.— The formats of TIS downlink messages are defined in section 4 of this appendix under broadcast identifier 0216. 3.2.2.2.1 Message header The 8-bit header shall be present in all TIS messages. The message header for TIS shall have the value 02 (hexadecimal), since all TIS messages utilize the short-form MSP protocol and TIS is assigned MSP channel 2. 3.2.2.2.2 Message type The 6-bit message type field shall be used to differentiate the different types of uplink messages: In the case of “first segment” traffic data messages, the 6-bit message type field shall contain the Mode S interrogator-derived tracked own-heading of the aircraft receiving the TIS message. This heading shall be quantized in 6 degree increments and shall be expressed with reference to magnetic north at the interrogator. The own-heading value in traffic data messages shall be provided to permit display heading correction on board the TIS-equipped aircraft by using an airborne heading sensor. Note.— Such a heading correction may be necessary when the aircraft is manoeuvring or crabbing due to wind. Since there may be several TIS traffic data messages to a given aircraft during a given scan, TIS processing shall be able to group the TIS traffic data uplinks together correctly. The “first”, “intermediate”, and “final” segment type values shall provide the necessary information to perform this grouping process. The mechanism for this shall be as specified below. Buffer space for at least 4 TIS traffic data messages (eight aircraft) shall be provided. 3.2.2.2.2.1 Keep-alive message The TIS keep-alive message shall contain the message header and the message type fields as described above. The message type field shall be set to 63 decimal. The remaining bits of the message shall be unused. 3.2.2.2.2.2 Goodbye message The TIS goodbye message shall contain the message header and the message type fields as described above. The message type field shall be set to 62 decimal. The remaining bits of the message shall be unused. 3.2.2.2.3 Traffic information block Each TIS traffic data message shall contain two 21-bit traffic information blocks whose structure is shown below. The six fields in a traffic information block shall describe one TIS alert aircraft. One TIS traffic data message shall be able to define one or two alert aircraft. Note.— A number ‘n’ of TIS traffic data messages may be uplinked in a given scan to convey information on up to 2n alert aircraft. Message type value TIS message uplink type 0 to 59 Traffic data, first segment (own-heading) Traffic data, intermediate segment(s) Traffic data, final segment Goodbye Keep-alive Traffic bearing Traffic range Relative altitude Altitude rate Traffic heading Traffic status 6 bits 4 bits 5 bits 2 bits 3 bits 1 bit 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-134 28/11/02 No. 77 3.2.2.2.3.1 Traffic bearing The 6-bit traffic bearing field shall contain the bearing angle from the own-aircraft heading to the alert aircraft, quantized in 6 degree increments. The valid range for the traffic bearing field shall be 0 to 59 (with the exception described below). Note.— Since this bearing angle is defined by TIS with respect to its measured own-aircraft heading, corrections from an airborne heading source can be applied. If there is only one alert aircraft in a given TIS traffic data message, the traffic bearing field in the unused traffic information block shall be set to the value 63 (a bearing angle greater than 360 degrees) and the remainder of the bits in the traffic information block shall be ignored. This shall be termed as a “null alert” block. 3.2.2.2.3.2 Traffic range The 4-bit traffic range field shall contain the distance between own-aircraft and the alert aircraft. A non-linear range encoding shall be used to minimize the number of bits required for this field as follows: 3.2.2.2.3.3 Relative altitude The 5-bit relative altitude field shall contain the difference in altitude between the own-aircraft and the alert aircraft. A non-linear encoding shall be used to minimize the number of bits required for this field. A special encoding value shall be used to indicate that the alert aircraft has no reported altitude. By convention, a positive value in the relative altitude field shall indicate that the alert aircraft is above the own-aircraft. Relative altitude shall be given by: Relative altitude = AltitudeAlert aircraft – AltitudeOwn-aircraft where altitudes are indicated in feet. The TIS encoding for relative altitude shall be: Traffic range value (r) Range (in increments of 230 m (0.125 NM)) 0 < r < 1 1 < r < 3 3 < r < 5 5 < r < 7 7 < r < 9 9 < r < 11 11 < r < 13 13 < r < 15 15 < r < 18 18 < r < 22 22 < r < 28 28 < r < 36 36 < r < 44 44 < r < 52 52 < r < 56 r >56 Relative altitude value (alt) Relative altitude (feet) 0 < alt < +100 +100 < alt < +200 +200 < alt < +300 +300 < alt < +400 +400 < alt < +500 2007/70/II. szám Part I Annex 10 — Aeronautical Telecommunications 5-135 28/11/02 No. 77 3.2.2.2.3.4 Altitude rate The 2-bit altitude rate field shall indicate whether the alert aircraft is climbing, descending, or level. An altitude rate of 500 ft/min shall be used as a threshold. The encoding of the TIS altitude rate field shall be: 3.2.2.2.3.5 Traffic heading The 3-bit traffic heading field shall contain the heading of the alert aircraft quantized to 45 degree increments. This heading shall be based on the Mode S ground interrogator track for the alert aircraft. Note.— The coarse quantization of traffic heading is sufficient to aid the pilot receiving the TIS alert message to visually acquire the traffic alert aircraft. 3.2.2.2.3.6 Traffic status The 1-bit traffic status field shall identify the type of alert represented by this traffic information block. A status value of “ZERO” shall indicate a “proximity” alert and a status value of “ONE” shall indicate a “threat” alert. +500 < alt < +600 +600 < alt < +700 +700 < alt < +800 +800 < alt < +900 +900 < alt < +1 000 +1 000 < alt < +1 500 +1 500 < alt < +2 000 +2 000 < alt < +2 500 +2 500 < alt < +3 000 +3 000 < alt < +3 500 +3 500 < alt No reported altitude –100 < alt < 0 –200 < alt < –100 –300 < alt < –200 –400 < alt < –300 –500 < alt < –400 –600 < alt < –500 –700 < alt < –600 –800 < alt < –700 –900 < alt < –800 –1 000 < alt < –900 –1 500 < alt < –1 000 –2 000 < alt < –1 500 –2 500 < alt < –2 000 –3 000 < alt < –2 500 alt < –3 000 Altitude rate field value Altitude rate Unused Climbing (>500 ft/min) Descending (>500 ft/min) Level Relative altitude value (alt) Relative altitude (feet) 2007/70/II. szám Annex 10 — Aeronautical Telecommunications Volume III 5-136 28/11/02 No. 77 3.2.2.2.4 Handling multiple TIS alerts As described above, the traffic data information for a given scan shall consist of one or more TIS traffic data messages. The last traffic information block of the last TIS uplink message for this scan shall be a null-alert block if there is an odd number of alert aircraft in this message. The null-alert condition shall be indicated by the value 63 decimal in the traffic bearing field of the traffic information block. 3.2.2.2.4.1 The TIS traffic information blocks within a given TIS traffic data message shall be arranged with the highest priority alerts first. All traffic information blocks with the status “threat” shall precede traffic information blocks with the status “proximity”. Within a status class, the traffic information blocks shall be put in order of increasing traffic range. Note.— This ordering ensures that the most critical traffic alerts will be at the head of the list of traffic information blocks. Therefore, TIS will report on the most significant aircraft up to the limit of the number of messages transferable in one scan. 3.2.2.3 TIS TRAFFIC DATA MESSAGES GROUPING MECHANISM 3.2.2.3.1 The mechanism for grouping TIS traffic data messages for a given scan shall be based on the message type field in each message as described in 3.2.2.2. 3.2.2.3.2 Since the Mode S Comm-A protocol can deliver multiple copies of the same message, the initial step in message grouping shall be a check to eliminate duplicate messages. This shall be accomplished by a bit comparison of successive messages received with the same message type. 3.2.2.3.3 After duplicate elimination, the TIS traffic data for a given grouping shall always begin with a “first” segment message. This message shall contain the own-heading value for the group. Additional TIS traffic data messages in the grouping (if present) shall be structured as indicated in the table below: 3.2.2.3.4 The receipt of a “first” segment shall start the formation of a message group. Subsequent TIS traffic data uplink messages shall be added to the group until one of the following conditions occurs:

Source: https://magyarkozlony.hu/hivatalos-lapok/7e70cec03f34e3c2efd8610b865b65591eafd701/dokumentumok/a55dc160549d57fa4db0035e37c6a6a98dd1a0b9/letoltes