ETSO-C199 A1

A1 Introduction

A1.1 TABS Intent

A1.1.1 The intent of a TABS is to increase safety by encouraging the voluntary equipage of a low-cost, compact, easy-to-install device that will allow other aircraft equipped with collision avoidance systems and traffic advisory systems to track and display the TABS aircraft. TABSs are intended to be used on aircraft that are exempted from carrying a transponder or Automatic Dependent Surveillance — Broadcast (ADS-B) equipment, such as gliders, balloons and aircraft without electrical systems. TABS devices do not meet the transponder requirements defined in Commission Implementing Regulation (EU) No 1207/2011 of 22 November 2011 laying down requirements for the performance and the interoperability of surveillance for the single European sky. A TABS will allow these exempted aircraft to be visible to other aircraft equipped with:

1.a Traffic Advisory System (TAS) as defined in ETSO-C147();

2.a Traffic Alert and Collision Avoidance System I (TCAS I) as defined in ETSO-C118();

3.a Traffic Alert and Collision Avoidance System II, (TCAS II), as defined in ETSO-C119d;

4.ADS-B IN capability as defined in ETSO-C166b, and ETSO-C195b; or

5.ADS-B IN capability as defined in ETSO-C154c in airspace where UAT is used.

A1.1.2 A TABS is designed to:

6.reply to ATCRBS Mode C, and Mode S UF=0, 4, 5, 20 and 21 interrogations;

7.not reply to ATCRBS Mode A interrogations;

8.not reply to Mode S UF=11, and 16 interrogations;

9.incorporate ETSO-C88b, Automatic Pressure Altitude Reporting Code-Generating Equipment;

10.transmit ADS-B Messages: Aircraft Identification and Category, Airborne Position, Airborne Velocity, Emergency Priority Status Message, and Aircraft Operational Status;

11.optionally provide Surface Position Messages;

12.optionally use a commercial GNSS source meeting the requirements of this ETSO.

A1.1.3 A TABS can potentially act as a low-cost platform for other aviation applications. Although additional capabilities are beyond the scope of this ETSO, TABSs may include additional functions such as data loggers, search and rescue transmitter, or provide flight information services.

A1.2 Requirements

A1.2.1 TABS requirements are derived from existing Mode S transponder and 1090 MHz Extended Squitter ADS-B requirements. A designer who builds equipment to meet this ETSO may decide to incorporate the full transponder and ADS-B capability by using a device that meets ETSO-C112e and ETSO-C166b. If they elect to implement the full functionality, they must demonstrate that functionality against the unmodified test procedures in EUROCAE ED-102A, including Corrigendum-1, dated January, 2012, that are required by ETSO-C112e and ETSO-C166b respectively. Designers who wish to take advantage of the reduced transponder requirements afforded to ETSO-C199 Class A devices must meet the modified requirements outlined in paragraphs A1.2.3 Transponder Function Requirements, A1.2.4 Altitude Source Function Requirements, and A1.2.5 ADS-B OUT Function Requirements in this Appendix in their entirety. Designers wishing to take advantage of the Class B reduced GNSS requirements will need to meet the requirements outlined in paragraphs A1.2.6 GNSS Position Source Function Requirements.

A1.2.2 MOPS text is used here with the permission of the RTCA. Table 1 provides notes in italics and parenthesis explaining how to read the tables that modify the text in the source documents.

Table 1 — (Source document reference) (type of change)

A1.2.3 Transponder Function Requirements Derived From DO-181E (For Class A Devices) A1.2.3.1 The transponder function must meet the Minimum Performance Standards (MPS) qualification and documentation requirements in RTCA, Inc. document RTCA document DO-181E, Section 2, for a Level 2, Class 2, transponder as modified below.

A1.2.3.1.1 Flight Crew Control Function Changes

A1.2.3.1.2 A cost factor in any device is the control and display functions to interface with the human operator. TABS display and control requirements are a subset of those required for transponders. Some user controls are allowed via an external device prior to flight (e.g., a personal electronic device (PED)). If the system is powered by batteries, display of the available battery life is recommended. Table 2 provides an overview of the flight crew control functions.

Table 2 — Summary of Control and Indication Requirements by Operation Mode

A1.2.3.1.3 RTCA document DO-181E, Section 2.1.7.a, Flight Crew Control Functions, is amended as shown in Table 3.

Table 3 — DO-181E Section 2.1.7.a amendment

A1.2.3.1.4 RTCA document DO-181E, Section 2.1.7.b, Flight Crew Control Functions, is amended as shown in Table 4.

Table 4 — DO-181E Section 2.1.7.b amendment

A1.2.3.1.5 RTCA document DO-181E, Section 2.1.7.c, Flight Crew Control Functions, is amended as shown in Table 5.

Table 5 — DO-181E Section 2.1.7.c amendment

A1.2.3.1.6 RTCA document DO-181E, Section 2.1.7.d, Flight Crew Control Functions, is amended as shown in Table 6.

Table 6 — DO-181E Section 2.1.7.d amendment

A1.2.3.2 Reply Rate Capability Changes

A1.2.3.2.1 This section reduces the minimum reply rate capability of the TABS consistently with the interrogation acceptance based on two assumptions. The following rationale describes how the modified reply rates were chosen.

A1.2.3.2.1.1 Assumption 1. The worst-case Mode C interrogation count in a 100-millisecond interval from 1 ATCRBS radar is approximately 14 interrogations. 4 ATCRBS radar overlapping beam dwells in 1 second is approximately 53 Mode C interrogations. The Mode C interrogation acceptance rate from 10 TCAS I units is approximately 15 interrogations per second. This represents a total demand on the TABS of 68 Mode C replies per second for this example.

A1.2.3.2.1.2 Assumption 2. The worst-case Mode S reply rate is primarily derived from the expected interrogation pattern of a set of 50 nearby TCAS II units all equipped with hybrid surveillance. The radar load from only roll-call interrogations would be small and would require networked sensors, otherwise the Mode S ground interrogation acceptance rate from radar systems would be 0 (zero).

A1.2.3.2.2 Based on assumptions 1 and 2, RTCA document DO-181E Section 2.2.3.4 Reply Rate Capability is changed as follows:

A1.2.3.2.2.1 RTCA document DO-181E, Section 2.2.3.4.1.a, ATCRBS Reply Rate Capability, is amended as shown in Table 7.

Table 7 — DO-181E Section 2.2.3.4.1.a amendment

A1.2.3.2.2.2 RTCA document DO-181E, Section 2.2.3.4.1.c, ATCRBS Reply Rate Capability, is amended as shown in Table 8.

Table 8 — DO-181E Section 2.2.3.4.1.c added

A1.2.3.2.2.3 RTCA document DO-181E, Section 2.2.3.4.2.a, Mode S Reply Rate Capability, is amended as shown in Table 9.

Table 9 — DO-181E Section 2.2.3.4.a amendment

A1.2.3.2.2.4 RTCA document DO-181E, Section 2.2.3.4.2.b, Mode S Reply Rate Capability, is amended as shown in Table 10.

Table 10 — DO-181E Section 2.2.3.4.2.b amendment

A1.2.3.3 Reply Rate Limiting Changes

A1.2.3.3.1 The modifications in this section address reply rate limiting for ATCRBS and Mode S reply rates consistently with the previous section.

A1.2.3.3.2 RTCA document DO-181E, Section 2.2.7.3.1, ATCRBS Reply Rate Limiting, is amended as shown in Table 11.

Table 11 — DO-181E Section 2.2.7.3.1 amendment

A1.2.3.4 RTCA document DO-181E, Section 2.2.13.1.2.c, Variable Direct Data, is amended as shown in Table 12.

Table 12 — DO-181E Section 2.2.13.1.2.c amendment

A1.2.3.5 RTCA document DO-181E, Section 2.2.13.1.2.d, Variable Direct Data, is amended as shown in Table 13.

Table 13 — DO-181E Section 2.2.13.1.2.d amendment

A1.2.3.6 RTCA document DO-181E, Section 2.2.13.1.2.e, Variable Direct Data, is amended as shown in Table 14.

Table 14 — DO-181E Section 2.2.13.1.2.e amendment

A1.2.3.7 Interrogation Acceptance Protocol Changes (All-Call reply capability)

A1.2.3.7.1 The transponder All-Call interrogation reply acceptance requirements are reduced to reply only to ATCRBS Mode C (P1-P3) interrogations. The purpose is to reduce the reply rate of TABS while maintaining TCAS and TAS interoperability. The requirements of this ETSO are identical to RTCA document DO-181E except for the changes shown below.

A1.2.3.7.2 RTCA document DO-181E, Section 2.2.18.2.2.b, Interrogation Acceptance Protocol (Figure 2-12), is amended as shown in Table 15.

Table 15 — DO-181E Section 2.2.18.2.2.b amendment

A1.2.3.7.3 RTCA document DO-181E, Section 2.2.18.2.2.c, Interrogation Acceptance Protocol (Figure 2-12), is amended as shown in Table 16.

Table 16 — DO-181E Section 2.2.18.2.c amendment

A1.2.3.8 RTCA document DO-181E, Section 2.2.18.2.2.g, Interrogation Acceptance Protocol, paragraph g, All-Call Lockout Conditions, is amended as shown in Table 17.

Table 17 — DO-181E Section 2.2.18.2.g amendment

A1.2.3.9 RTCA document DO-181E, Section 2.2.18.2.2.i, Interrogation Acceptance Protocol Stochastic All-Calls, should not be implemented in Class A TABS.

A1.2.3.10 Two new sections are added here to explicitly define interrogation acceptance criteria for TABS.

A1.2.3.10.1 RTCA document DO-181E, Section 2.2.18.2.2.L, Interrogation Acceptance Protocol (Figure 2-12), is added as shown in Table 18.

Table 18 — DO-181E Section 2.2.18.2.2L addition

A1.2.3.10.2 RTCA document DO-181E, Section 2.2.18.2.2.m, Interrogation Acceptance Protocol (Figure 2-12), is added to as shown in Table 19. This change reduces the range at which addressed Mode S ground interrogations would be replied to. The intent is to reduce the reply rate of the TABS. Sensitivity to TCAS interrogations is not affected.

Table 19 — DO-181E Section 2.2.18.2.2.m addition

A1.2.3.11 RTCA document DO-181E, Section 2.2.18.2.3, Interrogation Reply Coordination, is amended as shown in Table 20.

Table 20 — DO-181E Section 2.2.18.2.3 amendment

A1.2.3.12 RTCA document DO-181E, Section 2.2.18.2.4, Lockout Protocol, should not be implemented in Class A TABS.

A1.2.3.13 RTCA document DO-181E, Section 2.2.18.2.5, Multisite Lockout Protocol, should not be implemented in Class A TABS.

A1.2.3.14 RTCA document DO-181E, Section 2.2.18.2.7, Flight Status and Vertical Status Protocols, is amended as shown in Table 21.

Table 21 — DO-181E Section 2.2.18.2.7 amendment

A1.2.3.15 RTCA document DO-181E, Section 2.2.18.2.9, All-Call Reply Protocol, should not be implemented in Class A TABS.

A1.2.3.16 RTCA document DO-181E, Section 2.2.19.1, Minimum Level 2 Transponder Requirements, is amended as shown in Table 22.

Table 22 — DO-181E Section 2.2.19.1 amendment

A1.2.3.17 RTCA document DO-181E, Section 2.2.19.1.3, Information Transfer, should not be implemented in Class A TABS.

A1.2.3.18 RTCA document DO-181E, Section 2.2.19.1.4, Interrogation-Reply Coordination, is amended per Table 23. Equipment using Minimum Level 2 Transponder Requirements, SHALL follow the text in DO-181E as written.

Table 23 — DO-181E Section 2.2.19.1.4 amendment

A1.2.3.19 The Lockout Protocol described in RTCA document DO-181E, Section 2.2.19.1.5, should not be implemented in Class A TABS.

A1.2.3.20 The UM Protocol described in RTCA document DO-181E, Section 2.2.19.1.9, should not be implemented in Class A TABS.

A1.2.3.21 The Comm-A Protocol described in RTCA document DO-181E, Section 2.2.19.1.10, should not be implemented in Class A TABS.

A1.2.3.22 The Broadcast Protocol described in RTCA document DO-181E, Section 2.2.19.1.11, should not be implemented in Class A TABS.

A1.2.3.23 The Air-Initiated Comm-B Protocol described in RTCA document DO-181E, Section 2.2.19.1.12.4, should not be implemented in Class A TABS.

A1.2.3.24 The Comm-B Broadcast Protocol described in RTCA document DO-181E, Section 2.2.19.1.12.5, should not be implemented in Class A TABS.

A1.2.3.25 The Updating the Data Link Capability Report described in RTCA document DO-181E, Section 2.2.19.1.12.6.3, should not be implemented in Class A TABS.

A1.2.3.26 The Change of Aircraft Identification described in RTCA document DO-181E, Section 2.2.19.1.13.e, should not be implemented in Class A TABS.

A1.2.3.27 Linked Comm-A Coding described in RTCA document DO-181E, Section 2.2.19.1.14, should not be implemented in Class A TABS.

A1.2.3.28 The Comm-U/V Protocol described in RTCA document DO-181E, Section 2.2.19.1.16, should not be implemented in Class A TABS.

A1.2.3.29 The Data Handling Interfaces described in RTCA document DO-181E, Section 2.2.19.1.17, should not be implemented in Class A TABS.

A1.2.3.30 The Multisite Message Protocol described in RTCA document DO-181E, Section 2.2.19.2, should not be implemented in Class A TABS.

A1.2.3.31 Surveillance Identifier (SI) requirements contained in RTCA document DO-181E, Section 2.2.24.2, should not be implemented in Class A TABS.

A1.2.3.32 The Elementary Surveillance (ELS) Compliant Transponder requirements in RTCA document DO-181E, Section 2.2.24, do not apply to TABS equipment. TABS SHALL not claim ELS compliance. Changes made to ELS registers do not need to be indicated via a Comm-B broadcast. If one or more of the ELS registers are supported, then Section 2.2.24 requirements SHALL apply except Sections 2.2.24 b 4, 2.2.24 c, 2.2.24.2, 2.2.24.3.2.5, and 2.2.24.3.4, which do not apply.

A1.2.3.33 The Enhanced Surveillance (EHS) Compliant Transponders requirements in RTCA/DO-181E, Section 2.2.25, do not apply to TABS. TABS equipment SHALL not claim EHS compliance. Changes made to EHS registers do not need to be indicated via a Comm-B broadcast. If one or more of the EHS registers are supported, then Section 2.2.25 requirements SHALL apply except Sections 2.2.25.1.2.4 and 2.2.25.2.3, which do not apply. Also, Section 2.2.25, paragraph 6 ‘Transponder capable of supporting EHS…’, must support ELS per A1.2.3.32 of this ETSO.

A1.2.4 Altitude Source Function Requirements (For Class A Devices)

A1.2.4.1 The altitude source function shall meet the performance requirements of ETSO-C88b, Automatic Pressure Altitude Reporting Code-Generating Equipment, dated 5 August 2016. It is recommended that the altitude source provide 25 ft or better resolution.

A1.2.5 ADS-B OUT Function Requirements Derived From EUROCAE ED-102A, including Corrigendum-1, (For Class A Devices) A1.2.5.1 The ADS-B OUT function must be 1090 Extended Squitter (ES) OUT, to support TCAS surveillance. The 1090ES OUT function must meet the Minimum Performance Standards (MPS) qualification and documentation requirements in EUROCAE ED-102A, MOPS for 1090 MHz Extended Squitter Automatic Dependent Surveillance – Broadcast (ADS-B) and Traffic Information Services – Broadcast (TIS-B), dated December, 2009, including Corrigendum-1, Section 2, dated January, 2012, for a Class B0 ADS-B OUT transmitter with the following modifications.

A1.2.5.2 EUROCAE ED-102A, including Corrigendum-1, Section 2, dated January, 2012, Paragraph 2.2.2.1.c, Mode S Transponder Based Transmitters, is amended as shown in Table 24.

Table 24 — ED-102A Section 2.2.2.1.c amendment

A1.2.5.3 The output power SHALL be as specified in EUROCAE ED-102A, including Corrigendum-1, dated January, 2012, Section 2.2.2.2.10.1.a., for Class A0 and B0 equipment. The RF Peak Output power SHALL be at least 18.5 dBW (70 watts).

A1.2.5.4 Broadcast of the ADS-B Surface Position Messages defined in EUROCAE ED-102A including Corrigendum-1, Section 2.2.3.2.4, is optional.

A1.2.5.5 EUROCAE ED-102A including Corrigendum-1, Section 2.2.3.2.7.2, Aircraft Operational Status Messages, is amended as shown in Table 25.

Table 25 — Aircraft Operational Status Message

A1.2.5.6 When TABS is installed with a position source meeting the Class B requirements of this ETSO and transmitting a valid position, the transmitted NIC SHALL be set to 6 (0.5 NM), reference EUROCAE ED-102A including Corrigendum-1, dated January 2012, Section 2.2.8.1.16. The transmitted SIL SHALL be set to 1 (1×1E-3/ h), reference EUROCAE ED-102A including Corrigendum-1, dated January 2012, Section 2.2.5.1.40. When TABS is installed with a position source compliant with ETSO-C145, ETSO-C146 or ETSO-C196, NIC and SIL SHALL be set in accordance with EUROCAE ED-102A including Corrigendum-1, dated January, 2012. When the position is not valid, NIC and SIL SHALL be set to 0 (zero).

A1.2.5.7 The System Design Assurance (SDA), SHALL be set to 1, reference EUROCAE ED-102A, including Corrigendum-1, dated January 2012, Section 2.2.5.1.50. The probability of an undetected fault causing transmission of false or misleading information SHALL be less than or equal to 1E-3.

A1.2.5.8 Navigation Accuracy Category for Position, (NACp) SHALL be derived from the Horizontal Figure of Merit (HFOM) in accordance with EUROCAE ED-102A, including Corrigendum-1, dated January 2012, Section A.1.4.9.9; however, TABS Class B position sources may not provide HFOM directly. When HFOM is not available directly, HFOM SHALL be derived from Horizontal Dilution of Precision (HDOP) according to the following formula: HFOM = 2 * HDOP * User Equivalent Range Error (UERE), where the UERE is 6 metres. This UERE is based on typical single frequency (L1) receiver performance and an assumption of mid-latitude atmospheric propagation. Although the real-time UERE may fluctuate, this assumption is sufficient to support the TABS use case. (Ref. Global Positioning System Signals, Measurements and Performance, by Pratap Misra and Per Enge, copyright 2001).

A1.2.5.9 When a TABS is installed with a position source meeting the Class B requirements of this ETSO and transmitting a valid position, the transmitted Navigation Accuracy Category for Velocity, (NACv) SHALL be set to 1 (10 m/s), reference EUROCAE ED-102A including Corrigendum-1, dated January, 2012, Section 2.2.5.1.19. When position is not valid, NACv SHALL be set to 0 (zero).

A1.2.5.10 Geometric Vertical Accuracy (GVA) SHALL be derived from Vertical Figure of Merit, (VFOM) in accordance with EUROCAE ED-102A including Corrigendum-1, dated January, 2012, Section 2.2.3.2.7.2.8. Class B position sources may not provide VFOM directly. When VFOM is not available directly, VFOM SHALL be derived from Vertical Dilution of Precision (VDOP) according to the following formula: VFOM = 2 * VDOP * UERE, where the UERE is 6 metres.

A1.2.5.11 The Type Code 31, Operational Status Message, subfield ‘Airborne Capability Class Code’, SHALL be changed to indicate the device is a TABS.

A1.2.5.11.1 The Operational Status Message SHALL be modified to indicate that it meets the performance standards of this ETSO. ED-102A, including Corrigendum-1, dated January, 2012, paragraph 2.2.18.4.7 and Figure 2-40, is modified by this ETSO. Message bits 53-54, (ME Bits 21-22), SHALL describe the capabilities of the TABS per Table 26. Set bit 54 to 1 (one) to indicate that either TABS Class A, Class B, or both classes of equipment are installed.

Table 26 — ED-102A Airborne Capability Class Message format

A1.2.6 GNSS Position Source Function Requirements (For Class B Devices)

A1.2.6.1 Manufacturers may use commercial off-the-shelf (COTS) GNSS position sources to meet the performance of this ETSO as long as the sensor meets the requirements in this section. The position source shall be capable of using satellite-based augmentation system (SBAS) corrections and health messages to exclude satellites from the position solution or to correct satellite range errors. In areas where the SBAS is available, the TABS shall use the SBAS corrections and health messages to exclude satellites from the position solution or to correct satellite range errors. In areas where the SBAS is not available or out of service, the TABS may continue to operate. The regional airspace authority will determine what operational impacts this may have on air-to-ground usage of TABS equipment. According to the FAA the GPS constellation experiences a significant ramp error approximately once a year. During these events, a chipset which uses the SBAS will, depending on the received SBAS messages, either correct or exclude the faulty satellite. Refer to RTCA document DO-229E, Minimum Operational Performance Standards for Global Positioning System/Satellite-Based Augmentation System Airborne Equipment, when interpreting SBAS-related requirements.

A1.2.6.2 The GNSS position source SHALL provide a GPS-only solution for use by the TABS ADS-B function. The FAA and EASA have not evaluated the performance of other GNSS systems for use in support of aviation-intended functions. This ETSO will be updated once sufficient analysis has been performed to show that other GNSS are appropriate for use by TABS equipment. Note, the GPS-only solution refers to the use of the GPS satellite constellation, it does not exclude augmentation of the GPS solution, such as provided by SBAS or GBAS systems.

A1.2.6.3 The GNSS horizontal position error SHALL not exceed 30 metres, 95th percentile, when the Horizontal Dilution of Precision (HDOP) is 2.5 or less. The GNSS position source SHALL either transmit a Horizontal Figure of Merit (95 %) (HFOM) or an HDOP metric.

Note: The 30-metre horizontal position fixing error requirement assumes a UERE of 6 metres, consistent with Section A1.2.5.8.

A1.2.6.4 Removed.

A1.2.6.5 The GNSS position source SHALL be capable of transmitting horizontal velocity measurements more accurate than 10 m/s, 95th percentile.

A1.2.6.6 The GNSS position source SHALL not transmit false or misleading data in the presence of broadband interference. There is no minimum interference rejection requirement for TABS equipment and loss of position in the presence of interference is acceptable behaviour.

A1.2.6.7 The GNSS position source SHALL not use SBAS corrections when the SBAS satellite is broadcasting message type 0.

A1.2.6.8 The GNSS position source SHALL exclude satellites with UDREI=15 reported in the SBAS fast corrections.

A1.2.6.9 The GNSS position source SHALL apply SBAS fast and long-term corrections when available.

A1.2.6.10 The GNSS position source SHALL be capable of transmitting geometric altitude, Height Above the Ellipsoid (HAE) measurements more accurate than 45 metres, 95th percentile, when the Vertical Dilution of Precision (VDOP) is 3.7 or less. The GNSS position source SHALL either transmit a Vertical Figure of Merit (95 %) (VFOM) or a Vertical Dilution of Precision (VDOP) metric.

Note: The 45-metre vertical position fixing error requirement assumes a UERE of 6 metres, consistent with Section A1.2.5.10.

A1.2.7 Antenna Function Requirements

A1.2.7.1 The requirements for transponder antennas are specified in ETSO-C112e. The requirements for GNSS antennas are specified in ETSO-C190 and ETSO-C144a. The antennas should be designed to meet the performance specified in the applicable ETSO. However, the TABS may benefit significantly in installation costs from implementations where the antennas are integrated in the TABS equipment. Small degradations in antenna performance may be acceptable as a trade-off for installation cost.

A1.2.7.2 Antennas may be installed internally on aircraft that are transparent to radio frequencies. An internal antenna may not be appropriate on aircraft with a metal hull. If an antenna is installed internally, testing will need to be conducted to ensure the TABS is not negatively impacted and installation guidance must accompany the unit to ensure the system is properly fitted to the aircraft.

A1.2.7.3 Because TABS may be installed on a radio frequency (RF) transparent fuselage near a pilot or passenger, or in a cockpit in close proximity to a pilot or passenger, consideration must be given to antenna placement to ensure it does not pose a hazard to humans or combustible materials. Manufacturers must provide installation guidance describing the minimum safe distance the antenna can be to the nearest human body or if applicable, combustible material. Appendix 3 to this ETSO provides a more in-depth discussion of this subject based on FCC and European documents.

A1.2.8 Form factor and power

A1.2.8.1 An ideal implementation of the TABS would be a single integrated unit with minimal connections to the airframe, such as; mechanical mounting, power, and static air source. Where the equipment might be shared between multiple airframes, the mechanical mounting could incorporate an airframe-specific configuration module (containing such items as the ICAO 24-bit aircraft address), and be designed such that no tools are required to remove or install the TABS.

A1.2.8.2 Low-power consumption design is important. Designs specifically intended for long-term battery operation are ideal. If the TABS is battery powered, it should be designed to provide system integrity commensurate with the failure condition category / classification stated in paragraph 3.2.1.

[Amdt. ETSO/13]

[Amdt. ETSO/16]

A2 Testing Introduction

A2.1 Testing Intent

A2.1.1 This Appendix provides an acceptable means to verify the major functions of the TABS.

A2.1.2 The TABS is not intended to accept and reply to any UF=11 All-Call interrogations. RTCA document DO-181E tests like 2.4.2.1 Step 6 that use the Mode S Only All-Call interrogation (UF=11) will need to use a different interrogation, such as a UF=0 interrogation.

A2.2 Testing Requirements

A2.2.1 The tests defined here are derived from tests in the reference documents or written here to ensure compliance with the intended capabilities of TABS equipment. These tests are one acceptable means to demonstrate that the equipment meets the functional requirements defined in Appendix 1 to this ETSO. Functionality not modified by Appendix 1 should be verified by the test outlined in the applicable standards, e.g. RTCA document DO-181E.

A2.2.2 Table 27 provides notes in italics and parenthesis explaining how to read the tables that modify the text in the source documents.

Table 27 — (Source document reference) (type of change)

A2.2.3 Testing Transponder Function Requirements Derived From DO-181E (For Class A Devices) A2.2.3.1 Testing of the transponder function of the TABS should follow the tests outlined in document RTCA document DO-181E, Minimum Operational Performance Standards for Air Traffic Control Radar Beacon System/Mode Select (ATCRBS/Mode S) Airborne Equipment, dated 17 March 2011, Section 2.3, 2.4, and 2.5, with the following exceptions:

A2.2.3.1.1 Testing of Flight Crew Control Functions

A2.2.3.1.2 Testing should verify that the requirements of RTCA document DO-181E, as modified by paragraph A1.2.3.1.2 of this ETSO, have been properly incorporated.

A2.2.3.1.3 Testing should verify that changes made to paragraph 2.1.7 a, in RTCA document DO-181E, per Section A1.2.3.1.3, have been properly incorporated.

A2.2.3.1.3.1 Testing should verify the requirements of A1.2.3.1.3, by performing the test outlined in RTCA document DO-181E Section 2.5.4.11. Test results should verify that the 4096 code can be set while on the ground. If the 4096 code can be set in flight, testing should verify that the 4096 code can be set while in the air (weight-off-wheels condition) per RTCA/DO-181E Section 2.5.4.11.

A2.2.3.1.3.2 Testing should verify the requirements of A1.2.3.1.3, by performing the test outlined in RTCA/DO-181E Section 2.5.4.11. Testing should verify that a means of selecting and transmitting Mode 3/A code 7700 (emergency) is provided and tested per RTCA document DO-181E Section 2.5.4.11.

A2.2.3.1.3.3 Testing should verify the requirements of A1.2.3.1.3, by performing the test outlined in RTCA document DO-181E Section 2.5.4.11. Testing should also verify that a means of selecting and transmitting an alternate Mode 3/A codes is provided and tested per RTCA document DO-181E Section 2.5.4.11.

A2.2.3.1.4 Testing should verify the requirements of A1.2.3.1.4, by performing the test outlined in RTCA document DO-181E Section 2.5.4.3.b. Test results should verify aircraft without a means of determining air/ground state, report in the air at all times. Aircraft with an automatic means to determine the air/ground state, must verify that the air/ground state is set properly. Perform the test outlined in RTCA document DO-181E Section 2.5.4.3.b. If capable of determining the air/ground state, test results should verify that the aircraft reports in the air when in the air, and on the ground when on the ground.

A2.2.3.1.5 Testing should verify that the requirements of A1.2.3.1.5, have been properly incorporated. If a means of selecting the standby condition is provided, testing should verify return to normal operation from standby condition is within 5 seconds.

A2.2.3.1.6 Testing should verify that the requirements of A1.2.3.1.6, have been properly incorporated. If a means of initiating the IDENT (SPI) feature is installed, testing shall verify it functions properly per RTCA document DO-181E Section 2.5.4.3. (see Also A1.2.3.5and A2.2.3.5).

A2.2.3.2 Testing Reply Rate Capability Changes

A2.2.3.2.1 This section provides test criteria for the reply rate changes based on assumptions made in Section A1.2.3.2.1.

A2.2.3.2.2 Testing should verify that changes made to A1.2.3.2.2 have been correctly incorporated into TABS equipment.

A2.2.3.2.2.1 Testing should verify that the requirements of A1.2.3.2.2.1 of this ETSO have been satisfied. Testing outlined in RTCA document DO-181E, Section 2.3.2.2.3 step 1, should verify that the transponder be able to continuously generate at least 100 ATCRBS 15-pulse replies per second.

A2.2.3.2.2.2 Testing should that verify the requirements of A1.2.3.2.2.2 of this ETSO have been satisfied. Testing outlined in RTCA document DO-181E, Section 2.3.2.2.3 step 3, should verify that the transponder is capable of a peak reply rate of 150 ATCRBS 15-pulse replies per second for a duration of 100 milliseconds.

A2.2.3.2.2.3 Testing should verify that the changes made to RTCA document DO-181E Section 2.2.3.4.2.a have been correctly incorporated into TABS equipment per A1.2.3.2.2.3.

A2.2.3.2.2.3.1 Testing should verify that the requirements of RTCA document DO-181E, Section 2.2.3.2.4.2.a, as modified by paragraph A1.2.3.2.2.3 of this ETSO have been satisfied. Testing outlined in RTCA document DO-181E, Section 2.3.2.2.3 step 2, should verify that the transponder provides at least 29 short Mode S replies in any 1-second interval.

A2.2.3.2.2.3.2 Testing should verify that the requirements of RTCA document DO-181E, Section 2.2.3.2.4.2.a, as modified by paragraph A1.2.3.2.2.3 of this ETSO have been satisfied. Testing outlined in RTCA document DO-181E, Section 2.3.2.2.3 step 3, should verify that the transponder provides at least 10 short Mode S replies in a 100-millisecond interval.

A2.2.3.2.2.3.3 Testing should verify that the requirements of RTCA document DO-181E, Section 2.2.3.2.4.2.a, as modified by paragraph A1.2.3.2.2.3 of this ETSO have been satisfied. Testing outlined in RTCA document DO-181E, Section 2.3.2.2.3 step 4, should verify that the transponder provides at least 5 short Mode S replies in a 25-millisecond interval.

A2.2.3.2.2.3.4 Testing should verify that the requirements of RTCA document DO-181E, Section 2.2.3.2.4.2.a, as modified by paragraph A1.2.3.2.2.3 of this ETSO have been satisfied. Testing outlined in RTCA document DO-181E, Section 2.3.2.2.3 step 5, should verify that the transponder provides at least 3 short Mode S replies in a l.6-millisecond interval.

A2.2.3.2.2.4 Testing should verify that the changes made to RTCA document DO-181E, Section 2.2.3.4.2.b, have been correctly incorporated into TABS equipment per A1.2.3.2.2.4.

A2.2.3.2.2.4.1 Testing should verify that the requirements of RTCA/DO-181E, Section 2.2.3.2.4.2.b, as modified by paragraph A1.2.3.2.2.4 of this ETSO have been satisfied. Testing outlined in RTCA document DO-181E, Section 2.3.2.2.3 step 2, should verify that the transponder provides at least 10 of the 29 Mode S replies as long-format replies in any 1-second interval.

A2.2.3.2.2.4.2 Testing should verify that the requirements of RTCA document DO-181E, Section 2.2.3.2.4.2.b, as modified by paragraph A1.2.3.2.2.4 of this ETSO have been satisfied. Testing outlined in RTCA document DO-181E, Section 2.3.2.2.3 step 3, should verify that the transponder provides at least 4 of the 10 Mode S replies as long-format replies in a 100-millisecond interval.

A2.2.3.2.2.4.3 Testing should verify that the requirements of RTCA document DO-181E, Section 2.2.3.2.4.2.b, as modified by paragraph A1.2.3.2.2.4 of this ETSO have been satisfied. Testing outlined in RTCA document DO-181E, Section 2.3.2.2.3 step 4, should verify that the transponder provides at least 3 of the 5 Mode S replies as long-format replies in a 25-millisecond interval.

A2.2.3.2.2.4.4 Testing should verify that the requirements of RTCA document DO-181E, Section 2.2.3.2.4.2.b, as modified by paragraph A1.2.3.2.2.4 of this ETSO have been satisfied. Testing outlined in RTCA document DO-181E, Section 2.3.2.2.3 step 5, should verify that the transponder provides at least 2 of the 4 Mode S replies as long-format replies in a l.6-millisecond interval.

A2.2.3.3 Testing Reply Rate Limiting Changes

A2.2.3.3.1 Testing should verify that the requirements of RTCA document DO-181E, Section 2.2.7.3.1, as modified by paragraph A1.2.3.3.1 of this ETSO have been satisfied. Testing outlined in RTCA document DO-181E, Section 2.4.2.2.5 step 1, should be performed to verify that the unit does not reply to Mode A interrogations.

A2.2.3.3.2 Testing should verify that the requirements of RTCA document DO-181E, Section 2.2.7.3.1, as modified by paragraph A1.2.3.3.2 of this ETSO have been satisfied. Testing outlined in RTCA document DO-181E, Section 2.4.2.2.5 step 1, should be performed to verify the unit is capable of between 100 continuous ATCRBS Mode C replies per second and the maximum continuous rate of which the transponder is capable, or 200 replies per second, whichever is less, without regard to the number of pulses in each reply. Sensitivity reduction SHALL apply only to the receipt of ATCRBS interrogations.

A2.2.3.4 Testing should verify that the requirements of RTCA document DO-181E, Section 2.2.13.1.2.c, as modified by paragraph A1.2.3.4 of this ETSO have been satisfied. Testing should show that airborne status is set to in the air unless the aircraft is air/ground determination capable. If the aircraft can determine air/ground state, testing should show that this capability is determined on the ground when on the ground and in the air when in the air.

A2.2.3.5 Testing should verify that the requirements of RTCA document DO-181E, Section 2.2.13.1.2.d, as modified by paragraph A1.2.3.5 of this ETSO have been satisfied. If the aircraft is capable of providing SPI, follow the test outlined in A2.2.3.1.6 of this ETSO to verify that it functions properly per RTCA document DO-181E Section 2.5.4.3 (see also, Section A1.2.3.1.6 and A2.2.3.1.6).

A2.2.3.6 Testing should verify that the requirements of RTCA document DO-181E, Section 2.2.13.1.2.e, as modified by paragraph A1.2.3.6 of this ETSO have been satisfied. Testing should show the aircraft ID loaded while on the ground is broadcast. If aircraft ID can be changed in flight, testing should verify that aircraft ID can be changed in flight and the new aircraft ID is broadcast.

A2.2.3.7 Testing of Interrogation Acceptance Protocol Changes (All-Call reply capability) A2.2.3.7.1 Except where noted here, testing of the Interrogation Acceptance Protocol capability should follow that called out in RTCA document DO-181E. Testing of the Interrogation Acceptance Protocol capability should be modified from those called out in RTCA document DO-181E to meet the changes made in A1.2.3.7.1.

A2.2.3.7.2 Testing should verify that the requirements of RTCA document DO-181E, Section 2.2.18.2.2.b, as modified by paragraph A1.2.3.7.2 of this ETSO have been satisfied. Various tests in RTCA document DO-181E Section 2.4 utilise the Mode S Only All-Call interrogation and the expected reply to execute the test procedure. A discrete interrogation should be used as a substitute for these test procedures. Testing outlined in RTCA document DO-181E, Section 2.5.4.2, should verify that UF=11 interrogations are not accepted.

A2.2.3.7.3 Testing should verify that the requirements of RTCA document DO-181E, Section 2.2.18.2.2.c, as modified by paragraph A1.2.3.7.3 of this ETSO have been satisfied. Testing outlined in RTCA document DO-181E, Section 2.5.4.2, should verify that an ATCRBS/Mode S All-Call interrogation (1.6-microseconds P4) is not accepted. The pulse decoder tests in Section 2.4.2.5 for ATCRBS/Mode S All-Call interrogation acceptance shall be modified to verify that no ATCRBS/Mode S All-Call interrogations that meet the criteria for acceptance in RTCA document DO-181E, Section 2.2.6.2, produce a reply.

A2.2.3.8 Testing of the requirements of RTCA document DO-181E, Interrogation Acceptance Protocol, per Sections 2.5.4.4 and 2.5.4.5, are not required per A1.2.3.8 of this ETSO.

A2.2.3.9 Testing of the requirements of RTCA document DO-181E, Stochastic All-Calls, per 2.5.4.13, is not required per A1.2.3.9 of this ETSO.

A2.2.3.10 Testing should verify the modified Mode S MTL requirements added to RTCA document DO-181E, per Section A1.2.3.10. Test to ensure that paragraphs 2.2.18.2.2.L and 2.2.18.2.2.m have been properly incorporated.

A2.2.3.10.1 Testing outlined in RTCA document DO-181E, Section 2.4.2, should verify that ATCRBS Mode A interrogations (P1-P3 spacing 8 microseconds) are not accepted per A1.2.3.10.1. Various tests in RTCA document DO-181E, Section 2.4, utilise Mode A interrogations to execute the test procedure. Mode C interrogations should be used as a substitute for these test procedures. The pulse decoder tests in RTCA document DO-181E, Section 2.4.2.5, for Mode A interrogation acceptance shall be modified to verify that no Mode A interrogations that meet the criteria for acceptance in RTCA document DO-181E, Section 2.2.6.2, produce a reply. The requirement for recovery from a Mode A interrogation per A1.2.3.10.1 shall be tested according to RTCA document DO-181E, Section 2.4.2.6 step 1, except using a Mode A interrogation from the master and a Mode C interrogation from the slave.

A2.2.3.10.2 Testing should verify the requirements added to RTCA document DO-181E, paragraph 2.2.18.2.2.m, have been properly incorporated per Section A1.2.3.10.2. Verify the requirement added by this ETSO, by performing the test procedure in RTCA document DO-181E, Section 2.4.2.1 step 6, using a UF=0 to verify the Mode S MTL in Section 2.2.2.4.b and UF=4, 5, 20 and 21 to verify the modified MTL per A1.2.3.10.2.

A2.2.3.11 Testing should verify that the requirements of RTCA document DO-181E, Interrogation Reply Coordination, Section 2.2.18.2.3, as modified by A1.2.3.11 of this ETSO are satisfied. Testing outlined in RTCA document DO-181E, Section 2.5.4.2, shall be modified to verify that the unit does not reply to ATCRBS Mode A interrogations. Test ATCRBS Mode A/Mode S All-Calls, ATCRBS Mode C/Mode S All-Calls or UF=11 interrogations per testing outlined in A2.2.3.7 and A2.2.3.10.

A2.2.3.12 Testing of RTCA document DO-181E, Lockout Protocol, Section 2.2.18.2.4, is not required since TABS devices do not reply to All-Call interrogations per A1.2.3.12 of this ETSO. Testing using interrogations in RTCA document DO-181E, Section 2.5.4.4, should be performed to verify the unit properly replies to interrogations containing lockout commands from ground interrogations.

A2.2.3.13 Testing of RTCA document DO-181E, Multisite Lockout Protocol, Section 2.2.18.2.5, is not required since TABS devices do not reply to All-Call interrogations per A1.2.3.13 of this ETSO. Testing using interrogations in RTCA document DO-181E, Section 2.5.4.5, should be performed to verify that the unit properly replies to interrogations containing multisite lockout commands from ground interrogations.

A2.2.3.14 Testing should verify that the requirements of RTCA document DO-181E, Flight Status and Vertical Status Protocols, Section 2.2.18.2.7, as modified by A1.2.3.14 of this ETSO are satisfied. Testing outlined in RTCA document DO-181E Section 2.5.4.7 should be performed to verify that the unit sets the flight status bits properly consistently with the capabilities provided for Mode 3/A code entry per A1.2.3.1.3.

A2.2.3.15 Testing the requirement of RTCA document DO-181E, All-Call Reply Protocol, Section 2.2.18.2.9, as modified by A1.2.3.15 is not required. Testing outlined in RTCA document DO-181E, Section 2.5.4.8, does not need to be performed since the TABS does not support the All-Call Protocol.

A2.2.3.16 Testing should verify the Level 2 Transponder Requirements of RTCA document DO-181E, Minimum Level 2 Transponder Requirements, Section 2.2.19.1, as modified by A1.2.3.16 of this ETSO are satisfied. Testing outlined in RTCA document DO-181E Section 2.5.3 should be performed to verify that the unit performs per design specifications. Also, testing outlined in RTCA document DO-181E, Section 2.5.4.17, should be performed to verify that the unit does not process DF=16 messages.

A2.2.3.17 No test is required to verify the requirements of RTCA document DO-181E, Information Transfer, Section 2.2.19.1.3, per A1.2.3.17.

A2.2.3.18 Testing should verify that the requirements of RTCA document DO-181E, Interrogation-Reply Coordination, Section 2.2.19.1.4, as modified by A1.2.3.18 are met. Use tests in A2.2.3.7 and A2.2.3.10 in this ETSO to verify the TABS does not reply to ATCRBS Mode A, ATCRBS/Mode S All Calls and UF=11 interrogations.

A2.2.3.19 Testing of the requirements of RTCA document DO-181E, Lockout Protocol, Section 2.2.19.1.5, per Section 2.5.4.4, are not required per A1.2.3.19 of this ETSO. Testing should verify the TABS does not perform the UM Protocol per RTCA document DO-181E, Section 2.5.4.18.

A2.2.3.20 Since TABS do not support the Comm-B protocol except for GICB extraction requests, the requirements of RTCA/DO-181E, UM Protocol, Section 2.2.19.1.9, do not apply, per A1.2.3.20. Using a subset of the interrogations identified in RTCA document DO-181E, Section 2.5.4.18, select 12 interrogations with UF 4, 5, 20 and 21 and containing DI=0, 1 and 7 and verify that the reply contains UM field of 0 (zero).

A2.2.3.21 Testing of the requirements of RTCA document DO-181E, Comm-A Protocol, Section 2.2.19.1.10, per Section 2.5.4.15, is not required per A1.2.3.21 of this ETSO. Testing should verify that the TABS does not perform the Com-A Protocol per RTCA document DO-181E, Section 2.5.4.15.

A2.2.3.22 Testing of the requirements of RTCA document DO-181E, Broadcast Protocol, Section 2.2.19.1.11, as modified by A1.2.3.22 is not required since TABSs do not support this protocol.

A2.2.3.23 Testing of the requirements of RTCA document DO-181E, Air-Initiated Comm-B Protocol, Section 2.2.19.1.12.4, per Section 2.5.4.18, is not required per A1.2.3.23. To verify GICB extraction requirements, perform the portion of the test procedure of RTCA/DO-181E, Section 2.5.4.18 using interrogation patterns 1 to 24, to test the transponder in state 1 of the test matrix to verify proper reply content.

A2.2.3.24 Testing the requirements of RTCA document DO-181E, Comm-B Broadcast Protocol, Section 2.2.19.1.12.5, per 2.5.4.21 is not required per A1.2.3.24.

A2.2.3.25 Testing should verify the requirements of RTCA document DO-181E, Updating the Data Link Capability Report, Section 2.2.19.1.12.6.3, as modified by A1.2.3.25. Testing should verify that the TABS does not perform the Updating the Data Link Capability Report per RTCA document DO-181E, Section 2.5.4.33.

A2.2.3.26 Testing should verify the requirements of RTCA document DO-181E, Change of Aircraft Identification, Section 2.2.19.1.13.e, as modified by A1.2.3.26. Testing should verify that the TABS does not perform the Change of Identification per RTCA document DO-181E, Section 2.5.4.19.

A2.2.3.27 Testing the requirements of RTCA document DO-181E, Linked Comm-A Coding, Section 2.2.19.1.14, per 2.5.4.15, is not required per A1.2.3.27.

A2.2.3.28 Testing the requirements of RTCA document DO-181E, Comm-U/V Protocol, Section 2.2.19.1.16, per 2.5.4.17, as modified by A1.2.3.28 is not required.

A2.2.3.29 Testing the requirements of RTCA/DO-181E, Data Handling Interfaces, Section 2.2.19.1.17, per 2.5.4.20, as modified by A1.2.3.29 is not required.

A2.2.3.30 Testing the requirements of RTCA document DO-181E, Multisite Message Protocol, Section 2.2.19.2, per Section 2.5.4.5, as modified by A1.2.3.30 is not required.

A2.2.3.31 Testing the requirements of RTCA document DO-181E, Surveillance Identifier (SI), Section 2.2.24.2, per 2.6.2, as modified by A1.2.3.31 is not required.

A2.2.3.32 Testing the requirements of RTCA/DO-181E, Elementary Surveillance Capability, Section 2.2.24 as modified by A1.2.3.32, is not required. If one or more ELS registers are supported, test per RTCA/DO-181E, Section 2.6.

A2.2.3.33 Testing the requirements of RTCA document DO-181E, Enhanced Surveillance Capability, Section 2.2.25.3.2, as modified by A1.2.3.33 is not required. If the unit is Enhanced Surveillance Capability capable test per RTCA document DO-181E, Section 2.7.

A2.2.4 Testing Altitude Source Function Requirements

A2.2.4.1 Testing of the Altitude Source Function should follow that called out in ETSO-C88b, Automatic Pressure Altitude Reporting Code Generating Equipment, dated August 5, 2016.

A2.2.5 Testing ADS-B OUT Function Requirements (For Class A Devices)

A2.2.5.1 Testing should verify the ADS-B system performs its intended function per EUROCAE ED-102A, MOPS for 1090 MHz Extended Squitter Automatic Dependent Surveillance — Broadcast (ADS-B) and Traffic Information Services — Broadcast (TIS-B), dated December 2009, including Corrigendum 1, dated January 2012, except as modified by Section A1.2.5. Testing should follow the tests outlined in EUROCAE ED-102A, including Corrigendum 1, dated January 2012, Sections 2.3 and 2.4 with the following exceptions:

A2.2.5.2 Per Section A1.2.5.2, testing of transponder functions should follow the requirements in Sections A1.2.3 and A2.2.3 of this ETSO.

A2.2.5.3 Testing should verify the System RF Peak Power Output has a peak output level of at least 18.5 dBW (70 watts) per A1.2.5.3, reference EUROCAE ED-102A, including Corrigendum-1, dated January, 2012, RF Peak Power, Section 2.2.2.2.10.1.a. Testing outlined in ED-102A, Section 2.3.2.2.6.1 step 5, should verify that the unit under test provides a peak output power level of at least 18.5 dBW (70 watts).

A2.2.5.4 If the optional ADS-B Surface Position Messages function is provided, per Section, A1.2.5.4, testing should verify the ADS-B Surface Position Message is correctly populated and broadcast per EUROCAE ED-102A, Section 2.4.3.2.1.2.2.

A2.2.5.5 If the optional Typecode 31 subtype 1 Aircraft Operational Status Messages is provided per Section A1.2.5.5, testing should verify that the Aircraft Operational Status Messages is correctly populated and broadcast per EUROCAE ED-102A Section 2.4.3.2.7.2 A2.2.5.6 Per Section A1.2.5.6, testing should verify that NIC=6, and SIL=1 when using position from a Class B position source using test procedures in EUROCAE ED-102A, including Corrigendum 1, dated January 2012, Sections 2.4.8.1.5 and 2.4.5.1.40.

A2.2.5.7 Testing should verify that the System Design Assurance (SDA) is set to 1 to verify the requirement in Section A1.2.5.7, reference EUROCAE ED-102A, including Corrigendum 1, dated January 2012, System Design Assurance (SDA), Section 2.2.5.1.50.

A2.2.5.8 Per Section A1.2.5.8, testing should verify that Navigation Accuracy Category for Position (NACp) is set according to EUROCAE ED-102A including Corrigendum-1, dated January, 2012, Section 2.4.3.2.7.1.3.8. Testing should verify that the NACp is set appropriately when the position source is providing HDOP and not HFOM.

A2.2.5.9 If a TABS Class B position source is installed, verify that Navigation Accuracy Category Velocity (NACv) is set to 1 (10 m/s) per A1.2.5.9.

A2.2.5.10 Verify that Geometric Vertical Accuracy (GVA) is set per A1.2.5.10. Testing outlined in EUROCAE ED-102A, including Corrigendum 1, dated January, 2012, Section 2.4.3.2.7.2.8, should verify that GVA is set appropriately when the position source is providing VDOP and not VFOM.

A2.2.5.11 Verify Type Code 31, Airborne Capability Class Message, indicates that the unit under test is a TABS per A1.2.5.11.

A2.2.6 Testing of GNSS Position Source Function Requirements (For Class B Devices) A2.2.6.1 A TABS incorporating a position source that is compliant with ETSO-C129, ETSO-C145, ETSO-C146 or ETSO-C196 must also meet the additional ADS-B criteria defined in AMC1 ACNS.D.ADSB.070 of CS-ACNS, to include any required testing. GNSS position sources that are not compliant with an existing GNSS ETSO will need to meet the requirements in paragraph A1.2.6 of this ETSO and verify it meets the minimum requirements by performing the tests outlined in Section A2.2.6 of this ETSO. The following tests were derived from a reduced set of requirements and associated tests found in RTCA document DO-229E.

A2.2.6.2 GPS Only Solution.

A2.2.6.2.1 Per paragraph A1.2.6.2, verify that the position source provides a GPS-SBAS or GPS Only solution for use by Class A TABS.

A2.2.6.3 Position Accuracy Tests.

A2.2.6.3.1 Two tests are used to verify the horizontal position accuracy to ensure the requirement in paragraph A1.2.6.3 is met. The first test is a 24-hour static scenario using live satellite signals. The second test uses a GNSS simulator to generate a scenario incorporating both static and dynamic aircraft manoeuvres.

A2.2.6.3.2 24-Hour Accuracy Test.

A2.2.6.3.2.1 The equipment SHALL be tested over a 24-hour period using live GPS satellite signals at a surveyed location. The equipment SHALL use an antenna representative of what will be used in an actual airborne installation. The horizontal position error SHALL be computed for each position estimate output by the equipment.

A2.2.6.3.2.2 Monitor the sensor-provided HFOM and VFOM, or HFOM and VFOM derived from the sensor-provided HDOP and VDOP per paragraphs A1.2.5.8 and A1.2.5.10. In order to pass the test, the horizontal position error must be less than 30 metres for at least 95 % of the samples and the horizontal accuracy reported must be greater than the actual position error for at least 95 % of the samples. In order to pass the test, the vertical position error must be less than 45 metres for at least 95 % of the samples and the vertical accuracy reported must be greater than the actual position error for at least 95 % of the samples.

A2.2.6.3.2.3 The horizontal position error SHALL not exceed 0.5 NM at any time during the test.

A2.2.6.3.2.4 Only those position outputs that are reported as valid by the equipment need to be considered for the accuracy evaluation. In order to pass the test, 99.9 % of the position outputs must be reported as valid, excluding those position reports prior to the first position fix.

A2.2.6.3.3 GPS Simulator-based Accuracy Tests.

A2.2.6.3.3.1 The equipment SHALL be tested using a GPS simulator scenario that includes both static and dynamic aircraft manoeuvres. The horizontal and vertical position errors SHALL be computed for each position estimate output by the equipment.

A2.2.6.3.3.2 Monitor the sensor-provided HFOM and VFOM, or HFOM and VFOM derived from the sensor-provided HDOP and VDOP per paragraphs A1.2.5.8 and A1.2.5.10. In order to pass the test, the horizontal position error must be less than 30 metres for at least 95 % of the samples and the horizontal accuracy reported must be greater than the actual position error for at least 95 % of the samples. In order to pass the test, the vertical position error must be less than 45 metres for at least 95 % of the samples and the vertical accuracy reported must be greater than the actual position error for at least 95 % of the samples.

A2.2.6.3.3.3 The horizontal position error SHALL not exceed 0.5 NM at any time during the test.

A2.2.6.3.3.4 Simulator Scenario Details

A2.2.6.3.3.4.1 Only those position outputs that are reported as valid by the equipment need to be considered for the accuracy evaluation. In order to pass the test, 99.9 % of the position outputs must be reported as valid, excluding those position reports prior to the first position fix.

A2.2.6.3.3.4.2 The simulator scenario SHALL use the standard 24-satellite constellation in RTCA document DO-229E Appendix B. The initial position and time should be chosen to ensure the satellite geometry supports the test pass-fail criteria, and the HDOP is close to 2.5 and the VDOP is close to 3.7.

A2.2.6.3.3.4.3 The simulation SHALL include both stationary and dynamic portions, as follows:

A2.2.6.3.3.4.3.1 At least 10 minutes of stationary position.

A2.2.6.3.3.4.3.2 A sequence of different manoeuvres, including acceleration to a constant velocity, climbs, descents, and turns.

A2.2.6.3.3.4.3.2.1 A series of turns should be included to ensure a constantly changing velocity to expose any effects of filtering on the position output.

A2.2.6.3.3.4.3.3 At least 10 minutes of accelerated manoeuvres SHALL be simulated.

A2.2.6.3.3.4.3.4 Aircraft dynamics are as follows: ground speed = 200 kt, horizontal acceleration=0.58 g, vertical acceleration of 0.5 g.

A2.2.6.3.3.4.4 The simulated satellite signals SHALL be set to -134 dBm while position measurements are taken. Signal powers may be increased at the beginning of the scenario to allow for initial acquisition.

A2.2.6.3.3.4.5 Simulated signals SHALL include ranging errors for atmospheric effects (troposphere and ionosphere) that adhere to approved models. Refer to DO-229E, Appendix A, Section A.4.2.4 and IS-GPS-200G, dated 5 September 2012.

A2.2.6.3.3.4.6 No interference needs to be simulated.

A.2.2.6.4 Reserved.

A2.2.6.5 Velocity Accuracy Tests.

A2.2.6.5.1 The velocity accuracy tests specified in AC 20-138D Appendix 4, Sections 4-2, 4-3 and 4-4, SHALL be performed per the requirement in A1.2.6.5 and show the unit provides an accuracy of 10 m/s or less, at least 95 % of the time. It is assumed that the GPS position source does not provide a velocity accuracy output and the TABS will broadcast NACv = 1. Only the tests required to demonstrate a NACv = 1 need be run.

A2.2.6.6 Interference Tests.

A2.2.6.6.1 The equipment SHALL be tested using simulated GPS signals mixed with an interfering signal of gradually increasing power until the equipment loses position to verify the requirement outlined in paragraph A1.2.6.6. The horizontal position accuracy will be evaluated.

A2.2.6.6.2 Simulator Scenario Details.

A2.2.6.6.2.1 Use the same simulator scenario set-up found in A2.2.6.3.3.4 with the following exceptions:

A2.2.6.6.2.2 The interfering signal SHALL be broadband noise with bandwidth of 20 MHz centred on 1575.42 MHz. The initial power spectral density SHALL be -170.5 dBm/Hz (-97.5 dBm total power).

A2.2.6.6.2.3 The scenario may need to be extended to allow sufficient time for increasing interference power.

A2.2.6.6.3 Test Procedure

A2.2.6.6.3.1 Step 1: The interfering signal SHALL initially be turned off.

A2.2.6.6.3.2 Step 2: The simulator scenario SHALL be engaged and the satellites’ RF SHALL be turned on.

A2.2.6.6.3.3 Step 3: The equipment SHALL be powered on and initialized. It is assumed that the receiver has obtained a valid almanac for the simulator scenario to be tested prior to conducting these tests.

A2.2.6.6.3.4 Step 4: The receiver SHALL be allowed to reach steady state. When the receiver has reached steady state, an interfering broadband noise signal of -170.5 dBm/Hz SHALL be applied.

A2.2.6.6.3.5 Step 5: The interference power SHALL be maintained until the accuracy has reached steady state. Position measurements and validity indications SHALL be recorded during this interval.

A2.2.6.6.3.6 Step 6: The power of the interfering signal SHALL be increased by 2 dB and maintained for 200 seconds.

A2.2.6.6.3.7 Step 7: Go to Step 5 and repeat until the receiver is unable to maintain a position fix.

A2.2.6.6.4 Pass-Fail Criteria

A2.2.6.6.4.1 The horizontal position errors SHALL be computed for each position estimate output by the equipment.

A2.2.6.6.4.2 The horizontal position error SHALL not exceed 0.5 NM at any time during the test.

A2.2.6.6.4.3 Only those position outputs that are reported as valid by the equipment need to be considered for the accuracy evaluation. There is no minimum interference rejection requirement for TABS equipment, and loss of position in the presence of interference is acceptable behaviour.

A2.2.6.7 Verification of SBAS Message Type 0

A2.2.6.7.1 Test to verify that the GNSS position source does not use SBAS corrections when the SBAS satellite is broadcasting message type 0 per A1.2.6.7.

A2.2.6.7.2 Simulator Scenario Details

A2.2.6.7.2.1 The simulator scenario SHALL use the standard 24-satellite constellation in RTCA document DO-229E Appendix B.

A2.2.6.7.2.2 A single SBAS satellite SHALL be simulated with a fast corrections (MT 2-5) update rate of 6 seconds.

A2.2.6.7.2.3 At 500 seconds into the scenario, the SBAS satellite SHALL start broadcasting message type 0 for 60 seconds. The message type 0 broadcast SHALL contain message type 2 data (if appropriate for the SBAS service being simulated).

A2.2.6.7.2.4 The scenario SHALL have a static user position.

A2.2.6.7.2.5 The simulated satellite signals SHALL be set to a nominal power level (-128 dBm).

A2.2.6.7.2.6 Simulated signals SHALL include ranging errors for atmospheric effects (troposphere and ionosphere) that adhere to approved models. Refer to DO-229E Appendix A Section A.4.2.4 and IS-GPS-200G, dated 5 September 2012.

A2.2.6.7.2.7 No interference needs to be simulated.

A2.2.6.7.3 Test Procedure

A2.2.6.7.3.1 Step 1: The simulator scenario SHALL be engaged and the satellites’ RF SHALL be turned on.

A2.2.6.7.3.2 Step 2: The equipment SHALL be powered on and initialised. It is assumed that the receiver has obtained a valid almanac for the simulator scenario to be tested prior to conducting the tests.

A2.2.6.7.3.3 Step 3: Monitor the receiver output for the indication of SBAS use. Verify that the receiver indicates that SBAS is not in use before an SBAS satellite has been acquired.

A2.2.6.7.3.4 Step 4: Allow the receiver to reach steady-state navigation. Verify that the receiver indicates that SBAS is in use before proceeding to the next step.

A2.2.6.7.3.5 Step 5: 500 seconds into the scenario, the SBAS satellite SHALL start broadcasting message type 0.

A2.2.6.7.3.6 Step 6: Monitor the receiver output for the indication of SBAS use. Verify that the receiver indicates that SBAS is not used within 8 seconds.

A2.2.6.8 Exclusion of satellites identified by SBAS as unhealthy

A2.2.6.8.1 Test to verify that the GNSS position source excludes satellites with UDREI=15 reported in the SBAS fast corrections per A1.2.6.8. The ability of the position source to exclude unhealthy satellites based on the SBAS UDREI will be tested by injecting a ramp error on a satellite measurement and subsequently broadcasting an SBAS UDREI of 15 (‘do not use’) for that satellite.

A2.2.6.8.2 UDREI = 15 in fast corrections message (MT 2-5, 24)

A2.2.6.8.2.1 The equipment SHALL be tested to verify that the UDREI data contained in the SBAS fast corrections messages (MT 2-5, 24) is used to exclude unhealthy satellites.

Note: The test does not assume that the receiver outputs an indication that the unhealthy satellite has been removed from the position solution. Instead, it uses a pass criterion based on horizontal position error.

A2.2.6.8.2.2 Simulator Scenario Details

A2.2.6.8.2.2.1 The simulator scenario SHALL use the standard 24-satellite constellation in RTCA document DO-229E Appendix B.

A2.2.6.8.2.2.2 A single SBAS satellite SHALL be simulated with a fast corrections (MT 2-5, 24) update rate of 6 seconds. The integrity information message (MT 6) SHALL not be broadcast.

A2.2.6.8.2.2.3 The simulation start time and location SHALL be such that the resulting HDOP is close to 5.0.

A2.2.6.8.2.2.4 The simulation SHALL use nominal aircraft dynamics, defined to be ground speed = 200 knots and horizontal acceleration = 0.58 g. These dynamics can be simulated as a series of turns.

A2.2.6.8.2.2.5 The scenario SHALL allow the receiver time to achieve steady-state navigation before introducing any satellite errors.

A2.2.6.8.2.2.6 The scenario SHALL introduce a ramp error on each simulated GPS satellite individually, as follows:

A2.2.6.8.2.2.6.1 Step 1: A 5-m/s ramp error SHALL be introduced on the simulated GPS satellite.

A2.2.6.8.2.2.6.2 Step 2: 6 seconds after the introduction of the ramp error, the simulated SBAS satellite SHALL broadcast a UDREI of 15 for the GPS satellite in the fast correction message.

A2.2.6.8.2.2.6.3 Step 3: The ramp error SHALL be applied until one of the following conditions occur:

1.The horizontal position error of a valid position output exceeds 0.5 NM; or

2.The ramp error exceeds 2 000 m; or

3.The affected GPS satellite is excluded from the solution.

A2.2.6.8.2.2.6.4 Step 4: Allow the receiver time to return to steady state before repeating Steps 1 to 3 on the next satellite.

A2.2.6.8.2.2.7 The simulated satellite signals SHALL be set to -134 dBm while position measurements are taken. Signal powers may be increased at the beginning of the scenario to allow for initial acquisition.

A2.2.6.8.2.2.8 Simulated signals SHALL include ranging errors for atmospheric effects (troposphere and ionosphere) that adhere to approved models. Refer to DO-229E, Appendix A, Section A.4.2.4 and IS-GPS-200G dated 5 September 5 2012.

A2.2.6.8.2.2.9 No interference needs to be simulated.

A2.2.6.8.2.3 Pass-Fail Criteria

A2.2.6.8.2.3.1 The test SHALL be run on two different space-time scenarios. The two scenarios SHALL be sufficiently separated to ensure that different satellite geometry is presented to the receiver.

A2.2.6.8.2.3.2 The horizontal position errors SHALL be computed for each position estimate output by the equipment during the test.

A2.2.6.8.2.3.3 The horizontal position error SHALL not exceed 0.5 NM at any time during the test.

A2.2.6.8.2.3.4 Only those position outputs that are reported as valid by the equipment need to be considered for the accuracy evaluation.

A2.2.6.9 Testing GNSS Position Source SBAS Fast and Long-Term Corrections

A2.2.6.9.1 Application of Fast Corrections (MT 2-5, 24) and Long-Term Corrections (MT 24, 25). The equipment SHALL be tested to verify that fast corrections and long-term corrections are applied properly per A1.2.6.9.

A2.2.6.9.2 Simulator Scenario Details

A2.2.6.9.2.1 The simulator scenario SHALL use the standard 24-satellite constellation in RTCA document DO-229E Appendix B.

A2.2.6.9.2.2 A single SBAS satellite SHALL be simulated with a fast corrections (MT 2-5, 24) update rate of 6 seconds and standard long-term corrections (MT 24, 25) update rate of 120 seconds.

A2.2.6.9.2.3 The simulation start time and location SHALL be such that the resulting HDOP is close to 5.0.

A2.2.6.9.2.4 The simulation SHALL use nominal aircraft dynamics, defined to be ground speed = 200 kt and horizontal acceleration = 0.58 g. These dynamics can be simulated as a series of turns.

A2.2.6.9.2.5 The scenario SHALL introduce a bias and ramp error on a single satellite selected so that the range error will result in the maximum horizontal position error if not corrected by SBAS. The SBAS long-term corrections will be applied to correct the bias error. At each 6-second update, SBAS fast corrections will be provided to correct the ramp error for the affected satellite, as follows:

A2.2.6.9.2.5.1 Step 1: A 70-metre bias SHALL be introduced on the simulated GPS satellite. Provide SBAS long-term corrections to correct the bias term. The bias magnitude was chosen to approximate the maximum value that can be corrected by the δaf0 term in a type 25 message (using velocity code 0).

A2.2.6.9.2.5.2 Step 2: Start the scenario broadcasting MT25 with the correction for the bias error introduced on the selected satellite.

A2.2.6.9.2.5.3 Step 3: Allow the receiver time to acquire the GPS and SBAS satellites and obtain a steady-state differential fix, including sufficient time to acquire a type 25 message for the selected GPS satellite.

A2.2.6.9.2.5.4 Step 4: Inject a 5-m/s ramp error on the selected satellite in the same direction as the bias error.

A2.2.6.9.2.5.5 Step 5: At each 6-second update, provide SBAS fast corrections equivalent to the size of the growing ramp error.

A2.2.6.9.2.5.6 Step 6: The ramp error SHALL be applied until the ramp error plus bias error reaches 325 metres. Maintain the error of 325 metres for 5 minutes.

A2.2.6.9.2.6 The simulated satellite signals SHALL be set to -134 dBm while position measurements are taken. Signal powers may be increased at the beginning of the scenario to allow for initial acquisition.

A2.2.6.9.2.7 Simulated signals SHALL include ranging errors for atmospheric effects (troposphere and ionosphere) that adhere to approved models. Refer to DO-229E Appendix A Section A.4.2.4 and IS-GPS-200G dated September 5, 2012.

A2.2.6.9.2.8 No interference needs to be simulated.

A2.2.6.9.3 Pass-Fail Criteria

A2.2.6.9.3.1 The horizontal and vertical position errors SHALL be computed for each position estimate output by the equipment during the test.

A2.2.6.9.3.2 Monitor the sensor-provided HFOM and VFOM, or HFOM and VFOM derived from the sensor-provided HDOP and VDOP per paragraphs A1.2.5.8 and A1.2.5.10. Compare the HFOM against the horizontal position error for each valid position estimate. Compare the VFOM against the vertical position error for each valid position estimate. In order to pass the test, the horizontal and vertical position accuracy output must be greater than the actual position error at least 95 % of the time. Analyse the position estimates to determine whether the fast corrections and long-term corrections are being applied correctly.

A2.2.6.9.3.3 Only those position outputs that are reported as valid by the equipment need to be considered for the accuracy evaluation.

A2.2.6.9.3.4 The test only needs to be run using a single space/time scenario.

A2.2.6.10 Test the GNSS position source requirements in Section 0 by running the test outlined in Section A2.2.6.3.3.

[Amdt ETSO/13]

[Amdt ETSO/16]

A3 Environmental Test Considerations

A3.1 The environmental tests and performance requirements described in this subsection provide a laboratory means of determining the overall performance characteristics of the equipment under conditions that are representative of those that may be encountered in actual aeronautical operations.

A3.2 The following test procedures must be run when performing environmental testing on Class B equipment. Class B equipment only needs to be tested under DO-160D change 3 or later Environmental Test, Section 4 Temperature and Altitude, and Section 5 Temperature Variation Testing.

A3.3 The test procedure provided below is considered satisfactory for use in determining the performance of the equipment under environmental conditions. Although specific test procedures are cited, it is recognised that other methods may be preferred. These alternative procedures may be used if the manufacturer can show that they provide at least equivalent information. In such cases, the procedures cited herein should be used as one criterion in evaluating the acceptability of the alternative procedures.

Note: The intent of this section is to minimise the testing of commercial off-the-shelf (COTS) devices.

A3.4 Class B Equipment System Test

A3.4.1 Equipment Required: A representative antenna of what will be installed in an actual airborne TABS.

A3.4.2 Figure 1 provides a representation of the test setup.

[Figure or form omitted from this preview — available in the Avioverse workspace library.]

Figure 1 — Test Set-up

A3.4.3 Measurement Procedure:

A3.4.3.1 Set the test equipment to measure the output of the position source.

A3.4.3.1.1 Verify that the position information output by the GPS to the TABS is correct for:

A3.4.3.1.1.1 The latitude and longitude of the surveyed location when connecting the device to a live (e.g. rooftop) antenna, or;

A3.4.3.1.1.2 The output by the GPS simulator for the scenario outlined in Section A2.2.6.3.3 A3.4.3.1.2 Using the test set-up in A3.4.2, monitor the sensor-provided HFOM, or HFOM derived from the sensor-provided HDOP per paragraph A1.2.5.8. This output SHALL be compared against the horizontal position error for each valid position estimate. In order to pass the test, the horizontal position accuracy output must be greater than the actual position error for at least 95 % of the samples. The horizontal position error SHALL not exceed 0.5 NM at any time during the test.

[Amdt ETSO/13]

[Amdt ETSO/16]