Appendix A A-8 potential impact of an erroneous position report caused by an equipment malfunction.
The definitions and probabilities associated with the supported failure effect are defined in AC 25.1309-1, AC 23.1309-1(),and AC 29-2 (Changes 1-3 incorporated). The SDA includes the position source, ADS-B equipment, and any intermediary devices that process the position data. § 91.227 requires an SDA of 2 or 3 as defined in Table A-6.
Table A-6. System Design Assurance SDA Value Supported Failure Condition Note 2 Probability of Failure Causing Transmission of False or Misleading Information Note 3,4 Software & Hardware Design Assurance Level Note 1,3 0 Unknown/ No safety effect > 1x10-3 Per-hour or Unknown N/A 1 Minor ≤ 1x10-3 Per-hour D 2 Major ≤ 1x10-5 Per-hour C 3 Hazardous ≤ 1x10-7 Per-hour B Note 1: Software design assurance pursuant to RTCA/DO-178C, Software Considerations in Airborne Systems and Equipment Certification, or equivalent.
Airborne electronic hardware design assurance pursuant to RTCA/DO-254, Design Assurance Guidance for Airborne Electronic Hardware, or equivalent.
Note 2: Supported failure classification defined in AC 25.1309-1(), AC 23.1309-1(), and AC 29-2().
Note 3: Because the broadcast position can be used by any ADS-B IN equipped aircraft or by ATC, the provisions in AC 23.1309-1() that allow reduction in failure probabilities and design assurance level for aircraft under 6,000 pounds do not apply for the ADS-B OUT system.
Note 4: Includes probability of transmitting false or misleading latitude, longitude, or associated position accuracy and integrity metrics.
A.2.30 TCAS Installed and Operational.
This parameter indicates whether the aircraft is fitted with a TCAS II and if the TCAS II is turned on and operating in a mode that can generate resolution advisory alerts. The TCAS installed and operational parameter is required to be transmitted by § 91.227.
A.2.31 TCAS Traffic Status.
This parameter indicates if a TCAS II equipped aircraft is currently generating a TCAS resolution advisory. The TCAS traffic status parameter is required to be transmitted by § 91.227 if the aircraft is TCAS II equipped.
A.2.32 Trajectory Change Report Capability.
Appendix A A-9 This information is permanently set to “zero” in TSO-C166b or TSO-C154c equipment.
No installation interface is required. Trajectory change reports are reserved for future use.
A.2.33 Vertical Rate.
The vertical rate is the barometric or geometric rate at which the aircraft is climbing or descending, measured in feet per minute. The vertical rate is typically generated by an air data computer or GNSS position source, or equipment that blends barometric vertical rate with inertial vertical rate and/or GNSS vertical rate.
A.2.34 Version Number.
The applicable TSO Minimum Operational Performance Standard (MOPS) level is communicated through the version number, which is fixed at the time the ADS-B equipment is manufactured. Version 2 applies to ADS-B equipment that meets MOPS documents RTCA/DO-260B with corrigendum 1 or RTCA/DO-282B with corrigendum
1. ADS-B equipment outputting version 2 or higher is required by § 91.227.
Appendix B B-1 APPENDIX B. IDENTIFYING AND QUALIFYING ADS-B POSITION SOURCES B.1 Purpose.
This appendix defines the minimum requirements for position sources interfaced to ADS-B systems. The appendix also defines appropriate position source qualification methods when the existing GNSS TSOs do not contain specific requirements or test procedures. The position source manufacturer should provide design data where appropriate, preferably in the GNSS equipment installation manual, so the installer can properly interface the position source to the ADS-B system. Position source suppliers must ensure any supplied data is incorporated into the article design, and changes to any documented characteristics result in a change to the part number.
B.2 Organization.
This appendix includes general guidance that applies to all position sources, as well as GNSS-specific guidance. The appendix also provides high-level requirements for tightly-coupled GNSS/IRU position sources and non-GNSS position sources. Unless otherwise specified, all references in this AC to TSO-C129, TSO-C145, TSO-C146, and TSO-C196 refer to any revision of the TSO.
B.3 General Guidance for All Position Sources.
B.3.1 Position.
The position source must provide a latitude and longitude output. Requirements and test procedures in TSO-C129/145/146/196 are sufficient and GNSS equipment with Technical Standard Order Authorization (TSOA) for the aforementioned TSOs require no additional qualification for the position output.
B.3.2 Horizontal Velocity.
The position source must output north/south and east/west velocities. We recommend the position source also output the velocity in a ground speed and track angle format.
B.3.3 Position Accuracy (Vertical).
The position source should output a vertical position accuracy metric. The vertical position accuracy metric must have been qualified during the system’s TSOA or design approval. This output must describe the vertical position accuracy with 95 percent probability under fault-free conditions.
B.3.4 Position Accuracy (Horizontal).
The position source must have a horizontal position accuracy output, and the output must have been qualified during the system’s TSOA or design approval. This output must describe the radius of a circle in the horizontal plane, with its center being at the true position that describes the region assured to contain the indicated horizontal position with at least 95 percent probability under fault-free conditions.
Appendix B B-2 B.3.5 Position Integrity (Horizontal).
The position source must have a horizontal position integrity output qualified during the system’s TSOA or design approval. This integrity output should describe the radius of a circle in the horizontal plane, with its center being at the true position that describes the region assured to contain the indicated horizontal position with at least
99.99999 percent probability under fault-free avionics conditions. Position sources that degrade from a 99.99999 percent probability to a 99.999 percent probability (such as a tightly-coupled inertial/GNSS system after the loss of GNSS) can still be installed;
however, they will not meet § 91.227 following the degradation. In this case, the position source must have a way of indicating the change to the ADS-B equipment.
Additionally, if the change of probability is due to a change in position source, the new position source must meet all of the requirements in this appendix.
B.3.5.1 Mode.
If interpretation of the integrity output of the position source can change due to a change in the position source mode, the position source must have a way of communicating that change of mode to the ADS-B equipment.
Additionally, the position source manufacturer should provide a description of the modes and a description of how the position source outputs the mode indication.
B.3.5.2 Validity Limit.
If the integrity value of the output cannot be trusted beyond a certain limit, indicate this limitation in the design documentation.
B.3.5.3 Integrity Fault.
The position source must be able to identify, and output, an indication of an integrity fault. This indication should occur within 8 seconds of output of an erroneous position. The position source manufacturer must provide information on how this integrity fault is output.
B.3.6 Position Integrity (Probability).
The position source manufacturer must provide information describing the basis for the probability of exceeding the horizontal integrity containment radius. This basis must indicate the probability of exceeding the integrity containment radius as well as the sampling duration (per-hour or per-sample).
B.3.7 SIS Error Detection.
The position source should provide a means to detect a SIS error when the system uses a SIS. The probability of missed detection for a faulty SIS should be less than 1x10-3.
GNSS equipment provides the appropriate SIS error detection.
B.3.8 Velocity Accuracy.
The position source should have a velocity accuracy output that was qualified in conjunction with the system’s TSOA or design approval. Instead of a dynamic output, the position source manufacturer may demonstrate a worst case velocity accuracy that
Appendix B B-3 can be assumed based on testing. A test for GNSS position sources is contained in the latest revision of AC 20-138, appendix 4. The position source manufacturer may propose a test method for non-GNSS sources or an alternate test for GNSS sources during the TSOA or design approval.
B.3.9 Design Assurance.
The position source must support a major or greater failure effect. This includes software compliant with RTCA/DO-178C, Level C, and airborne electronic hardware (AEH) compliant with RTCA/DO-254, Level C. For airborne electronic hardware determined to be simple, RTCA/DO-254, section 1.6 applies. Because the broadcast position can be used by any ADS-B IN equipped aircraft or by ATC, the provisions in AC 23.1309-1() that allow reduction in failure probabilities and design assurance level for aircraft under 6,000 pounds do not apply for the ADS-B OUT system. The overall probability of a position source malfunction causing a position to be output that exceeds the output integrity radius must be less than 1x10-5 per-hour.
B.3.10 Geometric Altitude.
The position source must have a geometric altitude output. The geometric altitude must be referenced to the WGS-84 ellipsoid.
B.3.11 Update Rate.
The position source must output a new position at least once per second. Faster position update rates reduce latency of the transmitted position and are encouraged.
B.3.12 Position Source Latency.
The position source manufacturer must provide position source latency information.
Specifically, the manufacturer must provide the amount of position source total latency and uncompensated latency. Because the latency requirements are based on the entire ADS-B OUT system, and not just the position source, the following position source latency targets are only guidelines. Position source uncompensated latency should be less than 200 ms, compensated latency should be less than 500 ms, and total latency should be less than 700 ms.
Note 1: System latency requirements are described in section 3.1.3 and Appendix C of this AC.
Note 2: This section addresses position latency only.
B.3.13 Position, Velocity, and Accuracy Time of Applicability.
For each position output by the source, a velocity, horizontal position accuracy metric, and horizontal velocity accuracy metric must also be output. All measurements and metrics must have the same time of applicability. A horizontal position integrity metric must also be output, but its time of applicability may lag the position. Refer to TSO-C145, TSO-C146, or TSO-C196 for additional information on the integrity time to alert.
B.3.14 Time Mark.
Appendix B B-4 Position sources should output a time mark identifying the Coordinated Universal Time (UTC) time of applicability of the position. The time mark can be used by the ADS-B equipment to reduce uncompensated latency.
B.3.15 Availability.
§ 91.225 and § 91.227 do not define an availability requirement; however, it is a significant operational factor when selecting the position source (refer to Table B-2, Estimated GNSS Availabilities (Minimum Threshold Constellation), below).
B.4 GNSS Position Sources.
Compliance to the applicable TSOs for GNSS position sources does not guarantee that the unit is suitable as an ADS-B position source. The information in this section describes an acceptable means to demonstrate compliance with ADS-B requirements not addressed by GNSS TSOs when using GNSS position sources for ADS-B.
B.4.1 Position.
GNSS position sources must provide a latitude and longitude output. Requirements and test procedures in TSO-C129/145/146/196 are sufficient and GNSS equipment with TSOA for the aforementioned TSOs require no additional qualification for the position output. Some GNSS position outputs are referenced to the center of navigation of the aircraft. Manufacturers should document under what conditions the position is output in this manner. Installers must configure the ADS-B installation to account for any position offset from the surveillance reference point or GNSS antenna position as applicable.
Note: The intent is to output position, velocity, and HFOM in a consistent manner for time of applicability (refer to RTCA/DO-229D, Minimum Operational Performance Standards for Global Positioning System/Wide Area Augmentation System Airborne Equipment, sections 2.1.2.6 and 2.1.2.6.2).
B.4.1.1 TSO-C129.
The requirements outlined for 2D accuracy in section (a)(3)(xvi) of TSO-C129 do not ensure full compliance for the GNSS unit. Additional means of compliance for this TSO require GNSS manufacturers to substantiate that the latitude/longitude is output and referenced to WGS-84 coordinate system.
B.4.1.2 TSO-C129a.
The requirements outlined for 2D accuracy in section (a)(3)(xvi) of TSO-C129a do not ensure full compliance for the GNSS unit. Additional means of compliance for this TSO require GNSS manufacturers to substantiate that the latitude/longitude is output and referenced to WGS-84 coordinate system.
Appendix B B-5 B.4.1.3 TSO-C145/146 Rev a Class 1.
Means of compliance for this TSO are defined in RTCA/DO-229C, section 2.1.2.6.
B.4.1.4 TSO-C145/146 Rev a Class 2/3.
Means of compliance for this TSO are defined in RTCA/DO-229C, sections 2.1.4.8 and 2.1.5.8.
B.4.1.5 TSO-C145/146 Rev b/c/d Class 1.
Means of compliance for this TSO are defined in RTCA/DO-229D, section 2.1.2.6.
B.4.1.6 TSO-C145/146 Rev b/c/d Class 2/3.
Means of compliance for this TSO are defined in RTCA/DO-229D, sections 2.1.4.8 and 2.1.5.8.
B.4.1.7 TSO-C196/196a.
Means of compliance for this TSO are defined in RTCA/DO-316, Minimum Operational Performance Standards for Global Positioning System/Aircraft Based Augmentation System, section 2.1.2.6.
B.4.2 Position Source Latency.
GNSS position source manufacturers must provide position source latency information.
B.4.2.1 TSO-C129.
Means of compliance for this TSO require GNSS manufacturers to document the position source latency from time of measurement (TOM) to time of position output. If this latency exceeds 0.9 seconds, it may not support the 2-second ADS-B transmission latency at the aircraft level.
B.4.2.2 TSO-C129a.
Means of compliance for this TSO require GNSS manufacturers to document the position source latency from TOM to time of position output. If this latency exceeds 0.9 seconds, it may not support the 2-second ADS-B transmission latency at the aircraft level.
B.4.2.3 TSO-C145/146 Rev a Class 1.
Means of compliance for this TSO are defined in RTCA/DO-229C, section 2.1.2.6.2.
B.4.2.4 TSO-C145/146 Rev a Class 2/3.
Means of compliance for this TSO are defined in RTCA/DO-229C, sections 2.1.2.6.2 and 2.1.5.8.2.
B.4.2.5 TSO-C145/146 Rev b/c/d Class 1.
Appendix B B-6 Means of compliance for this TSO are defined in RTCA/DO-229D, section 2.1.2.6.2.
B.4.2.6 TSO-C145/146 Rev b/c/d Class 2/3.
Means of compliance for this TSO are defined in RTCA/DO-229D, sections 2.1.2.6.2 and 2.1.5.8.2.
B.4.2.7 TSO-C196/196a.
Means of compliance for this TSO are defined in RTCA/DO-316, section 2.1.2.6.2.
B.4.3 Availability.
B.4.3.1 Analysis has shown the following estimated availability for TSO GPS receivers using a 2-degree antenna mask angle (refer to Table B-2), assuming the minimum threshold GPS satellite constellation. The Minimum Threshold Constellation is the probability of slots filled with healthy satellites. For Table B-1, the FAA uses the modified interagency forum on operational requirements (IFOR) constellation probabilities that provides a conservative estimate of predicted GNSS availability. The modified IFOR probabilities are not guaranteed by the U.S. Air Force, but are intended to be consistent with the Global Positioning System Standard Positioning Service Performance Standard, revision 4, dated September 2008. Modified IFOR threshold constellation state probabilities based on this performance standard (a 0.99999-percent probability of 20 healthy satellites or satellite pairs in expanded slot configuration) are shown in Table B-1.
Table B-1. Modified IFOR Threshold Constellation State Probabilities Number of Healthy Satellites Probability That Exactly a Given Number of Satellites Are Healthy Probability That at Least a Given Number of Satellites Are Healthy 24 0.72% 0.72% 23 0.17% 0.89% 22 0.064% 0.954% 21 0.026% 0.98% 20 0.01999% 0.99999% 19 0.000005% 0.999995% 18 0.000005% 1.0000%
Appendix B B-7 B.4.3.2 The FAA plans to integrate the availability of backup surveillance systems with ADS-B, including SSR and Wide Area Multilateration, to mitigate the impact of loss of GNSS performance due to current limitations of operator GNSS receivers and the health of the constellation. Backup surveillance will not be available in all airspace, and operators should select an ADS-B positioning source that provides the necessary availability for their route of flight. The FAA plans to implement a preflight GPS service availability determination system to assist operators in determining surveillance availability for ADS-B before flight. This tool will consider the operator’s GNSS equipage and the GPS constellation that is predicted to be available at the planned flight time. The tool will also consider the status of existing backup surveillance capability along with the required positioning performance for the separation standard ATC is authorized to apply along the operator’s defined route of flight.
Table B-2. Estimated GNSS Availabilities (Minimum Threshold Constellation) Positioning Service (Receiver Standard) Predicted Availability (ADS-B Compliance) GPS (TSO-C129) (SA On) ≥ 89.0% GPS (TSO-C196) (SA Off) ≥ 99.0% GPS/SBAS (TSO-C145/TSO-C146) ≥ 99.9% B.4.4 Horizontal Position Integrity.
GNSS position sources must have a horizontal position integrity (such as HIL or HPL) output qualified during the system’s TSOA or design approval to determine NIC.
B.4.4.1 TSO-C129.
The requirements outlined for Class A, B, and C equipment provide horizontal integrity through RAIM algorithms under RTCA/DO-208 change 1, Minimum Operational Performance Standards for Airborne Supplemental Navigation Equipment Using Global Positioning System (GPS), section 2.2.1.13. However, there is no requirement to compute or output HPL. To properly comply with the ADS-B requirements, additional means of compliance for this TSO require GNSS manufacturers to provide substantiation data showing that the equipment outputs a 1x10-7/hr HPL based on the RAIM algorithm at least once per second that meets a 10-second time to alert. This AC recommends an 8-second time to alert. The protection level value is acceptable as an HPL if the equipment performs the test in RTCA/DO-208 change 1, section 2.5.2.5 using this protection level value for comparison against the alarm limit.
Equipment using the least-squares residual RAIM method recommended in RTCA/DO-208 change 1, appendix F provides an acceptable HPL.
Appendix B B-8 B.4.4.2 TSO-C129a.
The requirements outlined for Class A, B, and C equipment provide horizontal integrity through RAIM algorithms under RTCA/DO-208 change 1, section 2.2.1.13. However, there is no requirement to compute or output HPL. To properly comply with the ADS-B requirements, additional means of compliance for this TSO require GNSS manufacturers to provide substantiation data showing that the equipment outputs a 1x10-7/hr HPL based on the RAIM algorithm at least once per second that meets a 10-second time to alert. This AC recommends an 8-second time to alert. The protection level value is acceptable as an HPL if the equipment performs the test in RTCA/DO-208 change 1, section 2.5.2.5 using this protection level value for comparison against the alarm limit.
Equipment using the least-squares residual RAIM method recommended in RTCA/DO-208 change 1, appendix F provides an acceptable HPL.
B.4.4.3 TSO-C145/146 Rev a Class 1.
Means of compliance for this TSO are defined in RTCA/DO-229C, sections 2.1.2.6, 2.1.2.2.2, and 2.1.3.2.2. A summary of the latter requirements can be found in RTCA/DO-229C, section 2.1.1.13.1.
B.4.4.4 TSO-C145/146 Rev a Class 2/3.
Means of compliance for this TSO are defined in RTCA/DO-229C sections 2.1.2.6, 2.1.2.2.2, 2.1.3.2.2, 2.1.4.2.2, and 2.1.5.2.2. A summary of the latter requirements can be found in RTCA/DO-229C, section 2.1.1.13.1.
B.4.4.5 TSO-C145/146 Rev b/c/d Class 1.
Means of compliance for this TSO are defined in RTCA/DO-229D, sections 2.1.2.6, 2.1.2.2.2, and 2.1.3.2.2. Related requirements can be found in RTCA/DO-229D, sections 2.1.1.4 and 2.1.4.9.
B.4.4.6 TSO-C145/146 Rev b/c/d Class 2/3.
Means of compliance for this TSO are defined in RTCA/DO-229D, sections 2.1.2.6, 2.1.2.2.2, 2.1.3.2.2, 2.1.4.2.2, and 2.1.5.2.2. Related requirements can be found in RTCA/DO-229D, sections 2.1.1.4 and 2.1.4.9.
B.4.4.7 TSO-C196/196a.
Means of compliance for this TSO are defined in RTCA/DO-316, sections 2.1.2.6, 2.1.2.2.2, and 2.1.3.2.
B.4.5 Position Integrity (Probability).
GNSS position source manufacturers must provide information describing the basis for the probability of exceeding the horizontal integrity containment radius.
Appendix B B-9 B.4.5.1 TSO-C129.
Means of compliance for TSO-C129 are defined in RTCA/DO-208 change 1, section 2.2.1.13.1, referring to table 2-1.
B.4.5.2 TSO-C129a.
Means of compliance for TSO-C129a are defined in RTCA/DO-208 change 1, section 2.2.1.13.1, referring to table 2-1.
B.4.5.3 TSO-C145/146 Rev a Class 1.
Means of compliance for this TSO are defined in RTCA/DO-229C, section 2.1.2.2.2.1 for Satellite-Based Augmentation System (SBAS) based integrity. This requirement references appendix J, section J.2.1, defining position integrity. (Integrity probability is for HPLSBAS only).
For additional guidance on an acceptable scaling method, GNSS manufacturers can refer to RTCA/DO-229C, appendix U, section 4.
FDE requirements can be found in section 2.1.2.2.2.2.2.
B.4.5.4 TSO-C145/146 Rev a Class 2/3.
Means of compliance for this TSO are defined in RTCA/DO-229C, section 2.1.2.2.2.1 for SBAS-based integrity. This requirement references appendix J, section J.2.1, defining position integrity. (Integrity probability is for HPLSBAS only). For additional guidance on an acceptable scaling method, GNSS manufacturers can refer to RTCA/DO-229C, appendix U, section 4. FDE requirements can be found in section 2.1.2.2.2.2.2.
B.4.5.5 TSO-C145/146 Rev b/c/d Class 1.
Means of compliance for this TSO are defined in RTCA/DO-229D, section 2.1.2.2.2.1 for SBAS-based integrity. This requirement references to appendix J, section J.3.1, defining position integrity. (Integrity probability is for HPLSBAS only). For additional guidance on an acceptable scaling method, GNSS manufacturers can refer to RTCA/DO-229D appendix U, section 4. FDE requirements can be found in section 2.1.2.2.2.2.2.
B.4.5.6 TSO-C145/146 Rev b/c/d Class 2/3.
Means of compliance for this TSO are defined in RTCA/DO-229D, section 2.1.2.2.2.1 for SBAS-based integrity. Appendix J, section J.3.1 provides a background definition for position integrity. (Integrity probability is for HPLSBAS only). For additional guidance on an acceptable scaling method, GNSS manufacturers can refer to RTCA/DO-229D, appendix U, section 4. FDE requirements can be found in section 2.1.2.2.2.2.2.
B.4.5.7 TSO-C196/196a.
Means of compliance for this TSO are defined in RTCA/DO-316, section 2.1.2.2.2.2. For additional guidance on an acceptable scaling
Appendix B B-10 method, GNSS manufacturers can refer to RTCA/DO-316, appendix U, section 4.
B.4.6 Integrity Fault Alerts.
GNSS position source manufacturers must provide design data on the maximum time the position source can take to indicate an integrity fault. If the fault indication is mode specific, data on all modes must be included. It is recommended that the indication of an integrity fault be provided within 8 seconds across all modes. All revisions of TSO-C145, TSO-C146, and TSO-C196 GNSS equipment meet this requirement. No revisions of TSO-C129 GNSS equipment meet this requirement without meeting further qualifications outlined below. Receivers compliant with ARINC Characteristic 743A-5, GNSS Sensor, dated May 2009, represent the condition where a satellite fault has been detected but the receiver was unable to exclude the faulted satellite by setting bit 11 of label 130. This bit must be interpreted to set the position invalid regardless of the indicated HIL or HPL.
B.4.6.1 TSO-C129.
The requirements in RTCA/DO-208 change 1, section 2.2.1.13.1 cover the time to alarm for different phases of flight. To properly comply with the overall 12-second integrity fault output for ADS-B, additional means of compliance for TSO-C129 require GNSS manufacturers to provide information in the installation instructions describing the equipment integrity fault latency output with interface instructions and/or limitations for meeting the 12-second allocation set by § 91.227.
B.4.6.2 TSO-C129a.
The requirements in RTCA/DO-208 change 1, section 2.2.1.13.1 cover the time to alarm for different phases of flight. To properly comply with the overall 12-second integrity fault output for ADS-B, additional means of compliance for TSO-C129a require GNSS manufacturers to provide information in the installation instructions describing the equipment integrity fault latency output with interface instructions and/or limitations for meeting the 12-second allocation set by this AC.
B.4.6.3 TSO-C145/146 Rev a Class 1.
Means of compliance for this TSO are defined in RTCA/DO-229C, sections 2.1.1.13 and 2.1.2.2.2.2.1 through 2.1.2.2.2.2.4.
B.4.6.4 TSO-C145/146 Rev a Class 2/3.
Means of compliance for this TSO are defined in RTCA/DO-229C, sections 2.1.1.13, 2.1.2.2.2.2.1 through 2.1.2.2.2.2.4, and 2.1.4.2.2.2.1 through 2.1.4.2.2.2.3.
B.4.6.5 TSO-C145/146 Rev b/c/d Class 1.
Means of compliance for this TSO are defined in RTCA/DO-229D, sections 2.1.1.13 and 2.1.2.2.2.2.1 through 2.1.2.2.2.2.4.