Radar Vectors
Advisory Circular Cancelled Issued Sep 27, 2010 AIR-130 180 pages Copy saved Nov 18, 2026

AC 20-138B Airworthiness Approval of Posistioning and Navigation Systems

This advisory circular (AC) provides guidance material for the airworthiness approval of installed positioning and navigation equipment. Positioning and navigation equipment may be used for a variety of functions such as navigation, automatic dependent surveillance, and/or terrain awareness and warning systems. This AC addresses the following avionics: Global positioning system (GPS) equipment including those using GPS augmentations. Area navigation (RNAV) equipment integrating data from multiple navigation sensors. RNAV equipment intended for required navigation performance (RNP) operations. Barometric vertical navigation (baro-VNAV) equipment. This AC does not address new satellite constellations that are planned or currently under construction. This AC will be updated when sufficient documentation exists to support multiconstellation equipment.

This document is cancelled. It may have been replaced. Check the official source before relying on it.

Official source ↗ Open PDF

U.S. Department of Transportation Federal Aviation Administration

Advisory Circular

Subject: Airworthiness Approval of Positioning and Navigation Systems

Date: 9/27/10 Initiated by: AIR-130

AC No: 20-138B This advisory circular (AC) provides guidance material for the airworthiness approval of installed positioning and navigation equipment. Positioning and navigation equipment may be used for a variety of functions such as navigation, automatic dependent surveillance, and/or terrain awareness and warning systems. This AC addresses the following avionics:

 Global positioning system (GPS) equipment including those using GPS augmentations.

 Area navigation (RNAV) equipment integrating data from multiple navigation sensors.

 RNAV equipment intended for required navigation performance (RNP) operations.

 Barometric vertical navigation (baro-VNAV) equipment.

This AC does not address new satellite constellations that are planned or currently under construction. This AC will be updated when sufficient documentation exists to support multiconstellation equipment.

Susan J. M. Cabler Assistant Manager, Aircraft Engineering Division

ii

Table of Contents

Chapter 1. General Information … 1

1-1. Purpose … 1 1-2. Audience … 2 1-3. Cancellation … 2

Chapter 2. Technical Standard Order Authorization (TSOA) and Airworthiness Approval

Considerations - General … 3 2-1. Guidance for TSOA/Letter of DesignApproval (LODA) and Airworthiness Approvals … 3 2-2. TSOA … 3 2-3. STC-Approved Model List (AML) … 4 2-4. Type Certificate … 4

Chapter 3. TSO Authorization … 5

Chapter 3. TSO Authorization … 5

3-1. TSO-C129(AR)/C196 … 5 3-2. TSO-C145(AR)/C146(AR) … 6 3-3. TSO-C161a/C162a … 9 3-4. RNAV Multi-Sensor Equipment … 9 3-5. Multiple TSO Authorizations … 10

Chapter 4. Equipment Performance - Advisory Vertical Guidance … 11

4-1. Introduction … 11 4-2. Implementations … 11 4-3. Limitatations … 13

Chapter 5. Equipment Performance - GNSS … 15

Chapter 5. Equipment Performance - GNSS … 15

5-1. Introduction … 15 5-2. GPS (TSO-C129(AR) and TSO-C196 receivers) … 16 5-2.1 Antennas … 16 5-2.2 Sensors … 17 5-2.3 Prediction Program … 17 5-3. GPS/SBAS (TSO-C145/C146(AR) receivers) … 19 5-3.1 Antenna … 19 5-3.2 Sensor and Sensor/Navigation Computer Configuration … 20 5-3.3 Navigation Database - Data Conversion for GPS/SBAS LNAV/VNAV Approaches … 21 5-4. GPS/GBAS (TSO-C161a/C162a receivers) … 21 5-4.1 Antennas … 21 5-4.2 VHF Data Broadcast Receiving Equipment (TSO-C162a) … 22 5-4.3 Sensor/Navigation Computer (TSO-C161a) … 22 5-5. GNSS Upgrades … 23 5-5.1 Adding Additional GNSS equipment … 23 5-5.2 Replacing GNSS Equipment … 23

iii

5-5.3 GPS/SBAS Upgrade … 24 5-5.4 GNSS Antenna Re-Use/Replacement … 24 5-5.5 Marking … 25 5-6. Navigation Database … 26 5-6.1 Database Installation Instructions … 26 5-6.2 Database Process … 26 5-7. GNSS Geometric Altitude … 26

Chapter 6. Equipment Performance - RNAV Multi-Sensor Equipment … 27

Chapter 6. Equipment Performance - RNAV Multi-Sensor Equipment … 27

6-1. Introduction … 27 6-2. Navigation Database … 27 6-2.1 Database Installation Instructions … 27 6-2.2 Database Process … 27 6-3. GNSS … 27 6-4. DME/DME … 28 6-4.1 Reasonableness Checks … 31 6-4.2 Performance Confirmation … 32 6-4.3 Multi-Sensor System FMS … 33 6-5. VOR/DME … 33 6-6. INS/IRU … 36 6-7. INS/IRU – GNSS Integration … 36 6-8. INS/IRU - DME/DME Integration … 38

Chapter 7. Equipment Performance - RNP (General) … 40

Chapter 7. Equipment Performance - RNP (General) … 40

7-1. Introduction … 40 7-2. Special Characteristics of RNP Instrument Approaches … 41 7-3. Special Characteristics of RNP 1 Operations … 41

Chapter 8. Equipment Performance - RNP Approach … 43

8-1. Introduction … 43 8-2. Aircraft and System Requirements … 43 8-3. Performance and Functional Requirements for RNP Systems … 44 8-4. System Eligibility and Approval for RNP Operations … 48

Chapter 9. Equipment Performance - RNP Terminal … 51

Chapter 9. Equipment Performance - RNP Terminal … 51

9-1. Introduction … 51 9-2. Aircraft and System Requirements for RNP Terminal Operations … 51 9-3. System Performance Monitoring and Alerting … 52 9-4. System Eligibility and Approval for RNP 1 Operations … 56

Chapter 10. Equipment Performance - Baro-VNAV … 58

Chapter 10. Equipment Performance - Baro-VNAV … 58

10-1. General Limitations for Operations under IFR … 58 10-2. Baro-VNAV Equipment Performance for Operations under IFR … 58

Chapter 11. General Installation Considerations … 63

11-1. Introduction … 63 11-2. Failure Classification … 63

iv

11-3. Software Considerations … 64 11-4. Hardware Considerations … 64 11-5. Installed Equipment Compatibility … 64 11-6. Installation Instructions … 64 11-7. Environmental Considerations … 65 11-8. General Human Factors Considerations … 65

Chapter 12. General Installation Considerations - Antennas … 68

Chapter 12. General Installation Considerations - Antennas … 68

12-1. Antenna placement … 68 12-2. Anti-Ice Protection … 69 12-3. Antenna Cables … 69 12-4. Structure … 69

Chapter 13. General Installation Considerations - Sensors … 70

13-1. Introduction … 70 13-2. Positioning and Navigation Configuration Strapping … 70 13-3. Navigation Source Selection … 70 13-4. Dual Positioning and Navigation Installations … 71 13-5. Intermixing RNAV equipment … 71 13-6. Interface to FGS … 72 13-7. Interface to Magnetic/True Switch … 73 13-8. Interface to Air Data and Inertial Reference Systems … 74 13-9. Antenna/Sensor Compatibility … 74 13-10. Interference - Electromagnetic Compatibility (EMC) … 75 13-11. Interface Requirements … 75

Chapter 14. Installation Considerations - GNSS … 77

Chapter 14. Installation Considerations - GNSS … 77

14-1. Introduction … 77 14-2. Navigation Displays … 77 14-3. Failure Indications … 78 14-4. Documenting Effects of GNSS Outage … 79 14-5. GPS Equipment … 79 14-6. GPS/SBAS Equipment … 80 14-6.1 Limitations … 80 14-6.2 LP Approach … 81 14-6.3 Update Rate … 81 14-6.4 Performance Monitoring … 81 14-6.5 System Status … 82 14-6.6 Annunciations … 82 14-6.7 Accessibility … 83 14-6.8 GPWS/TAWS Glideslope Warning … 83 14-7. GPS/GBAS VDB Receiver … 83 14-7.1 Interference – EMC … 83 14-7.2 Compatibility with other systems … 84 14-7.3 VDB aircraft implementation loss … 84 14-8. GPS/GBAS Navigation Computer Receiver … 84 14-8.1 GPS/GBAS equipment intended for Category I … 84

v

14-8.2 GPS/GBAS stand-alone or MMR equipment intended for Category I … 85 14-8.3 Performance and Performance Monitoring … 86 14-8.4 Integrity … 86 14-8.5 Continuity of Navigation … 86 14-8.6 Fault Detection and Annunciation … 86 14-8.7 System Status … 87 14-8.8 Annunciation … 87 14-8.9 Accessibility … 87 14-8.10 Glidepath Capture … 88 14-8.11 Equipment Qualification … 88 14-8.12 Interoperability … 88 14-8.13 GPS/GBAS GPWS/TAWS Glideslope Warning … 88 14-9. Special Use Mission Equipment - Not for Navigation … 89

Chapter 15. Installation Considerations - RNAV Multi-Sensor Equipment … 90

Chapter 15. Installation Considerations - RNAV Multi-Sensor Equipment … 90

15-1. Introduction … 90 15-2. Interface to Primary Navigation Display … 90 15-2.1 Non-numeric Deviation Displays … 90 15-2.2 Map Displays … 91 15-3. Interface to Remote Annunciator … 91 15-4. Unique Software Considerations … 92

Chapter 16. Installation Considerations - RNP … 93

Chapter 16. Installation Considerations - RNP … 93

16-1. Introduction … 93 16-2. Flight Technical Error … 93 16-3. Radius to Fix (RF) Legs … 93 16-4. Interface to FGS … 94

Chapter 17. Installation Considerations - Baro-VNAV … 95

17-1. Failure Protection … 95 17-2. Manufacturer’s Instructions … 95 17-3. Annunciations … 95 17-4. Software Changes … 95 17-5. Integration with GNSS-Provided Vertical Guidance … 96

Chapter 18. Installed Performance - Data Submittal … 98

Chapter 18. Installed Performance - Data Submittal … 98

18-1. Introduction … 98 18-2. Project Specific Certification Plan … 98 18-3. TSO Technical Data … 98 18-4. Review the installation manual … 99 18-5. Structural Analysis … 99 18-6. Power Supply … 100 18-7. Environment … 100 18-8. Database … 100 18-9. Operations manual or AFMS/RFMS … 100 18-10. Stand-Alone Navigation Equipment … 100 18-11. Ground and Flight Test Plans (functional and EMI/EMC testing) … 101

vi

Chapter 19. Installed Performance - Test (General) … 102

Chapter 19. Installed Performance - Test (General) … 102

19-1. Intended Function … 102 19-2. Power Supply … 102 19-3. Accuracy … 102 19-4. Human Factors … 102

Chapter 20. Installed Performance - Test (GNSS) … 103

20-1. Ground Test - GPS, GPS/SBAS, and GPS/GBAS … 103 20-1.1 Interference … 103 20-1.2 Antenna to Aircraft Navigation Reference Offset … 103 20-1.3 Sensor Installation … 104 20-1.4 Stand-Alone Navigation Equipment Installation … 104 20-2. Flight Test - GPS, GPS/SBAS, and GPS/GBAS … 104 20-2.1 Equipment Installation … 104 20-2.2 LPV and Precision Approaches … 105 20-2.3 GPS/GBAS VDB Receiver Installation … 106

Chapter 21. Installed Performance - Test (RNAV Mult-Sensor Equipment) … 107

Chapter 21. Installed Performance - Test (RNAV Mult-Sensor Equipment) … 107

21-1. Ground Test … 107 21-2. Flight Test … 107 21-2.1 Interface to FGS … 108 21-2.2 GNSS Precision Approach … 109

Chapter 22. Installed Performance - Test (Baro-VNAV) … 110

22-1. Introduction … 110 22-2. Ground Test … 110 22-2.1 Lab/Bench Tests and Equipment Data Evaluation … 110 22-2.2 Aircraft Installation Data Evaluation … 110 22-3. Flight Test … 111 22-3.1 Functional Flight Test … 111 22-3.2 Navigation Error Flight Test … 112 22-4. Follow-on Approval … 113

Appendix 1. GPS Oceanic/Remote Navigation … A1-1

Appendix 1. GPS Oceanic/Remote Navigation … A1-1

A1-1. GPS Oceanic/Remote Navigation … A1-1 A1-2. Approval Process … A1-1 A1-3. Equipment Performance … A1-2

Appendix 2. RNP AR Operations … A2-1

A2-1. Introduction … A2-1 A2-2. Performance Requirements … A2-1 A2-3. RNP AR General Requirements … A2-3 A2-4. Requirements for RNP AR Approaches with RF Legs … A2-13 A2-5. Requirements for RNP AR Approach values less than 0.3 … A2-14 A2-6. Requirements for Approaches with a Missed Approach Less Than RNP 1 … A2-16 A2-7. Navigation Data Validation Program … A2-18 A2-8. Installation Considerations for RNP AR … A2-20

Appendix 2. RNP AR Operations … A2-1

vii

Appendix 3. RNP Advanced Features … A3-1

A3-1. Introduction … A3-1 A3-2. Radius to Fix Leg Capability … A3-1

Appendix 4. GNSS Velocity Tests to Support ADS-B … A4-1

A4-1. Introduction … A4-1 A4-2. Velocity Accuracy and Velocity Figure of Merit Tests … A4-1 A4-3. Horizontal Velocity Accuracy Test Conditions Commensurate with NACV = 1 … A4-1 A4-4. Horizontal Accuracy Pass/Fail Determination … A4-3 A4-5. Horizontal Velocity Figure of Merit Pass/Fail Determination … A4-4 A4-6. Vertical Velocity Accuracy Test Conditions Commensurate with NACV = 1 … A4-4 A4-7. Vertical Velocity Accuracy Pass/Fail Determination … A4-6 A4-8. Vertical Velocity Figure of Merit Pass/Fail Determination … A4-6 A4-9. Additional Tests to Demonstrate Accuracy Commensurate with NACV = 2 … A4-7

Appendix 5. Sample Airplane/Rotorcraft Flight Manual Supplement … A5-8

Appendix 5. Sample Airplane/Rotorcraft Flight Manual Supplement … A5-8

A5-1. Introduction … A5-8

Appendix 6. Installation of GNSS Equipment for VFR Use Only … A6-1

A6-1. Introduction … A6-1 A6-2. General … A6-1 A6-3. Applicability … A6-1 A6-4. Technical Instructions … A6-1

Appendix 7. Definitions and Acronyms … A7-1

Appendix 7. Definitions and Acronyms … A7-1

A7-1. Definitions … A7-1 A7-2. Acronyms … A7-3

Appendix 8. Related Documents … A8-1

A8-1. FAA Advisory Circulars … A8-1 A8-2. FAA Technical Standard Orders … A8-3 A8-3. RTCA, Inc. Documents (RTCA DO) documents … A8-4 A8-4. Other Documents … A8-5 A8-5. How to Get Related Documents … A8-6

Appendix 8. Related Documents … A8-1

List of Tables Table 1. Effective Noise Density for All GNSS Sources … 15 Table 2. Acceptable Standard Antennas … 25 Table 3. DME Usable Range … 29 Table 4. 2D Accuracy Requirements for Equipment Using a Single Co-located VOR/DME … 35 Table 5. Error Elements … 36 Table 6. Vertical Path Performance Limit for Baro-VNAV … 59 Table 7. Vertical Path Deviations … 60 Table 8. Typical Hazard Classifications … 63 Table 9. RNP FTE Performance … 93 Table 10. INS/IRU Accuracy After Loss of Radio Updating … 108

viii

Table 11. Tailwind Component (VKTW) for Turn Calculations … A2-7 Table 12. Platform Dynamics for Horizontal Velocity Accuracy Test … A4-2 Table 13. Platform Dynamics for Vertical Velocity Accuracy Test … A4-5

List of Figures

Figure 1. Minimum Straight Path Before DA … A2-17

Chapter 1. General Information.

1-1. Purpose. This advisory circular (AC) provides guidance material for the airworthiness approval of installed positioning and navigation equipment. Positioning and navigation equipment may be used for a variety of functions such as navigation, automatic dependent surveillance, and/or terrain awareness and warning systems. This AC addresses the following equipment:

a. Global positioning system (GPS) sensors or stand-alone navigation equipment, including those incorporating aircraft-based augmentation system (ABAS), satellite-based augmentation system (SBAS), or ground-based augmentation system (GBAS).

b. Area navigation (RNAV) integrating data from multiple navigation sensors such as global navigation satellite system (GNSS), inertial reference units (IRU), and distance measuring equipment (DME).

c. RNAV intended for required navigation performance (RNP) operations, including advanced functions and RNP authorization required (AR) formerly referred to as special aircraft and aircrew authorization required (SAAAR).

Note: RNP AR was previously named RNP SAAAR. The name has been changed to RNP AR for international harmonization, but might not yet be standardized throughout all documents. d. Barometric vertical navigation (baro-VNAV) equipment.

e. This AC does not address new satellite constellations that are planned or currently under construction. This AC will be updated when sufficient documentation exists to support multi-constellation equipment.

f. This AC incorporates the airworthiness considerations contained in AC 90-101A, Approval Guidance for RNP Procedures with SAAAR, and AC 90-105, Approval Guidance for RNP Operations and Barometric Vertical Navigation in the U.S. National Airspace System, as a necessary first step to consolidating all the positioning and navigation equipment and RNP airworthiness guidance into one AC. Future AC 90-101 and AC 90-105 revisions will remove the airworthiness guidance. This AC will not replace the operational guidance found in the RNP 90-series ACs. However, this AC does replace the ACs listed in paragraph 1-3 by incorporating and updating the information they contained.

g. This AC is not mandatory and is not a regulation. This AC describes an acceptable means, but not the only means, to comply with applicable regulations.

h. This AC provides guidance information intended for new approvals. This AC is not intended to modify, change or cancel existing equipment design or airworthiness approvals.

Equipment with existing approvals can continue to be installed within the provisions of their original design and airworthiness certification.

i. The guidance in this AC cannot ensure compliance with all Title 14 of the Code of Federal Regulations (CFR) parts 23, 25, 27, and 29 airworthiness regulations for every possible installation configuration. The applicant remains responsible for regulatory compliance and should work closely with their geographic aircraft certification office (ACO) to ensure regulatory compliance. Mandatory terms such as “must” used in this AC are only applicable when following the compliance method outlined.

j. In lieu of following this method without deviation, the applicant may elect to follow an alternate method, provided the alternate method is also found by the Federal Aviation Administration (FAA) to be an acceptable means of complying with the requirements of the federal aviation regulations 14 CFR.

1-2. Audience. This AC is for aircraft manufacturers, avionics manufacturers, installation shops, or other applicants seeking design and/or airworthiness approval for the positioning and navigation systems described in this document.

1-3. Cancellation. This AC supersedes the ACs listed below. Equipment previously approved per the guidance in the superseded ACs is still valid for the operations and conditions stated in their approvals. The following documents are cancelled:

a. AC 20-129, Airworthiness Approval of Vertical Navigation (VNAV) Systems for use in the U.S. National Airspace System (NAS) and Alaska.

b. AC 20-130A, Airworthiness Approval of Navigation or Flight Management Systems Integrating Multiple Navigation Sensors.

c. AC 20-138A, Airworthiness Approval of Global Navigation Satellite System (GNSS) Equipment.

d. AC 25-4, Inertial Navigation Systems.

Chapter 2. Technical Standard Order Authorization (TSOA) and Airworthiness

Chapter 2. Technical Standard Order Authorization (TSOA) and Airworthiness

Approval Considerations - General.

2-1. Guidance for TSOA/Letter of DesignApproval (LODA) and Airworthiness Approvals. Title 14 CFR part 21; subparts D, E, and O provide the regulatory basis defining changes to type certificates (TC) (major/minor changes to aircraft type design), supplemental type certificates (STC), and TSOAs. The regulations and technical standard orders (TSOs) can be found at: http://rgl.faa.gov. This chapter provides general guidance on TSOA/LODA and airworthiness approval considerations specific to positioning and navigation equipment.

2-2. TSOA. a. Several TSOs have been written for positioning and navigation-related equipment and components (see appendix 8 of this AC). New TSO’s will be written to address modernized GPS and other GNSSs once appropriate equipment standards are in place. It is beneficial to involve the ACO (both engineers and flight test pilots) in equipment evaluations as early as possible for four primary reasons:

(1) Obtaining a TSOA/LODA does not ensure that the equipment will satisfy all of the applicable operational requirements and/or airworthiness regulations when it is installed.

(2) The design of positioning and navigation equipment has become increasingly more complex and workload intensive with no standardized interface with the pilot. The human factors evaluation of the equipment is subjective.

(3) There is not one, single standard for interfacing positioning and navigation equipment to other equipment on-board the aircraft such as displays, autopilots, and terrain warning systems. Positioning and navigation equipment manufacturers should develop compatibility data relative to other equipment for inclusion within the installation manual.

(4) The installed intended function for the equipment needs to be compatible with the original design for the system, including software and hardware design assurance levels. For example, a decision by the positioning and navigation equipment manufacturer to develop system software to RTCA, Inc. document (RTCA)/(DO)-178B, Software Considerations in Airborne Systems and Equipment Certification, dated December 1, 1992, Level C, may limit installation eligibility if that equipment contributes to failure conditions of other systems that perform critical functions to a higher software level.

b. It is recommended that the positioning and navigation equipment manufacturer elect to obtain an STC for equipment installation concurrent with obtaining the TSOA/LODA. This has proven to be an effective method to aid installations.

Note: Any applicant may apply for an equipment installation STC. It is not this paragraph’s intent to limit positioning and navigation STCs for installation solely to avionics manufacturers.

c. The installation manual and other data accepted during the TSO process can be used as a source of acceptable data to support an installation airworthiness compliance finding.

2-3. STC-Approved Model List (AML). a. All STC applicants are encouraged to use an AML for aircraft makes/models (including 14 CFR parts 23, 25, 27, and 29 aircraft) with similar characteristics and compatible equipment configurations to streamline the approval of subsequent installations. Applicants and ACOs need to contact the applicable directorate for specific policy and guidance information on obtaining an STC-AML.

b. Using the STC-AML method can simplify follow-on installations for makes/models on the AML. The installer needs access to the STC approved data; apply the approved data; and comply with the detailed installation instructions. The installer then needs only complete FAA Form 337, Major Repair and Alteration (Airframe, Powerplant, Propeller, Appliance), identifying the nature of the change to return the aircraft to service (see AC 43.9-1 (latest revision), Instructions for Completion of FAA Form 337).

c. GPS and GPS/SBAS equipment airworthiness approval is not considered novel or unusual per 14 CFR § 21.16 and applicants can use designees during the STC process.

2-4. Type Certificate. Positioning and navigation equipment manufacturers are also encouraged to work with TC holders. This has also proven to be an effective method to aid installations.

Chapter 3. TSO Authorization.

3-1. TSO-C129(AR)/C196.

a. TSO-C129a, Airborne Supplemental Navigation Equipment Using the Global Positioning System (GPS), and TSO-C196, Airborne Supplemental Navigation Sensors for Global Positioning System Equipment Using Aircraft-Based Augmentation, both define an acceptable standard for GPS equipment without ground-based or space-based augmentations. Both TSO-C129 all revisions (AR) and TSO-C196 equipment require other positioning and navigation systems appropriate to the operation on-board the aircraft due to equipment limitations.

b. TSO-C196 defines GPS sensor equipment that incorporates many processing improvements found in the GPS/SBAS equipment minimum operational performance standards (MOPS); but, without the GPS/SBAS requirements. Two improvement examples are: a requirement for the receiver to properly account for satellite range error if it is reflected in the User Range Accuracy index (commonly referred to as being “Selective Availability aware”); and requirements to ensure performance is not degraded due to an increasing radio frequency noise environment as other satellite systems become available.

(1) TSOA/LODA applicants may wish to have a previously approved TSO-C145b/c, Airborne Navigation Sensors Using the Global Positioning System (GPS) Augmented by the Wide Area Augmentation System (WAAS), sensor approved as a TSO-C196 sensor. It is acceptable for these TSO-C196 applicants to take certification credit by re-using data developed during a previous TSO-C145b/c TSOA/LODA approval. RTCA/DO-316, Minimum Operational Performance Standards for Global Positioning System/Aircraft-Based Augmentation System Airborne Equipment, dated April 14, 2009, implemented by TSO-C196 was developed from RTCA/DO-229D, Minimum Operational Performance Standards for Global Positioning System/Wide Area Augmentation System (GPS/WAAS) Airborne Equipment, dated December 3, 2006, implemented by TSO-C145b/c. RTCA/DO-229D meets or exceeds the performance requirements for TSO-C196. The original RTCA/DO-178B documentation can be re-used if there are no software changes.

(2) Applicants seeking a TSO-C196 TSOA/LODA based on a previously approved TSO-C145b/c sensor must maintain separate part numbers for each unit. It is not acceptable to have both a TSO-C145b/c and TSO-C196 TSOA/LODA simultaneously (see paragraph 3-5.b(4)).

Note: Maintaining separate part numbers might only require different software part numbers. (3) It is acceptable for TSOA/LODA applicants with TSO-C145b/c sensors to simply disable the GPS/SBAS tracking loops in their equipment to qualify as a TSO-C196 sensor.

(4) TSOA/LODA applicants with TSO-C145a sensors will need to show requirements traceability between RTCA/DO-229C and RTCA/DO-316 along with data applicability to receive appropriate certification credit. In particular, applicants will need to

show compliance to any RTCA/DO-316 requirements not in RTCA/DO-229C; and requirements that are more stringent such as enroute/terminal mode accuracy and the broadband external interference noise environment.

c. There is no plan to withdraw TSO-C129(AR) authorizations or TSO-C129a. Manufacturers can continue production according to their TSOA/LODA or submit new designs for approval according to TSO-C129a and the equipment is still eligible for installation in accordance with the guidance in this AC.

Note: TSO-C129/C129a does not provide sufficient performance for all operational applications. d. It is possible to receive a TSO-C129a Class A incomplete system TSOA/LODA for displays or navigation computers provided they meet the applicable requirements in RTCA/DO-208, with Change 1, Minimum Operational Performance Standards for Airborne Supplemental Equipment Using Global Positioning System (GPS), dated September 21, 1993, as modified by TSO-C129a and are linked by part number to specific GPS sensors in the TSO application documentation.

e. TSO-C129a will take precedence when adding an incomplete system TSO-C129a Class A TSOA/LODA to an FMS with an existing TSO-C115b, Airborne Area Navigation Equipment Using MultiSensor Inputs, TSOA/LODA if there are any conflicts between the two TSOs.

Note: Paragraph 3-1.e is intended for new applications. There is no intent to invalidate older equipment may have received an incomplete system TSOA/LODA per TSO-C129. 3-2. TSO-C145(AR)/C146(AR). a. TSO-C145c/C146c defines an acceptable standard for GPS/SBAS equipment. There is no equipment limitation for GPS/SBAS-equipped aircraft to have other positioning and navigation systems on-board. Additionally, RTCA/DO-229D referenced by the GPS/SBAS TSOs will remain as the MOPS for single-frequency GPS/SBAS equipment. Future multifrequency/multi-system equipment will have a separate MOPS and TSO.

b. There is no plan to withdraw authorizations to the earlier TSO revisions, so manufacturers of TSO-C145a/C146a or TSO-C145b/C146b equipment can continue production according to their TSOA/LODA; and the equipment is still eligible for installation in accordance with the guidance in this AC.

c. The difference between revisions ‘b’ and ‘c’ to the GPS/SBAS TSOs is eliminating a 3 decibel (dB) broadband intra-system noise credit for operational Class 1 and Class 2 equipment in RTCA/DO-229D. TSO-C145b/C146b operational Class 3 and Class 4 equipment fully complies with the requirements in TSO-C145c/C146c and is automatically eligible for a revision ‘c’ authorization, i.e., no further evaluation is necessary.

d. TSO-C145b/C146b operational Class 1 and Class 2 equipment that did not claim the 3dB noise credit is also eligible for a revision ‘c’ authorization. The TSOA/LODA holder only needs to provide substantiation that they did not take the noise credit during the original certification.

e. Displays or navigation computers (such as flight management systems (FMSs)) may receive a TSO-C146c Class 1, 2, or 3 (functional Class Gamma) incomplete system TSOA/LODA provided they meet the applicable Class Gamma requirements in RTCA/DO- 229D and are linked by part number to specific GPS/SBAS sensors in the TSO application documentation. This is an effective method to aid GPS/SBAS installation approvals to make a complete system (sensor, navigation computer, display) at the aircraft level.

(1) FMSs are not required to have an incomplete system TSO-C146c Class Gamma TSOA/LODA to provide or process GPS/SBAS navigation functions such as flight path deviation data and GPS/SBAS alerts. It is sufficient to use TSO-C115b plus an alternate method to demonstrate compliance with the applicable RTCA/DO-229D performance requirements. However, an incomplete system TSO-C146c Class Gamma TSOA/LODA provides an established means for the installed FMS to demonstrate navigation computer compliance for credit as a GPS/SBAS system.

Note 1: FMSs that do not meet the applicable RTCA/DO-229D Class Gamma performance requirements can still receive Position/Velocity/Time (PVT) inputs from a TSO-C145(AR) sensor and apply them consistent with their existing approvals. Using a TSO-C145(AR) sensor can remove certain performance limitations (see paragraphs 5-5.2.b and 5-5.2.c). Note 2: TSOA/LODA applicants may request deviations to TSO-C146c or RTCA/DO-229D performance requirements for the FMS if they demonstrate an equivalent level of safety. (2) TSO-C146c will take precedence when adding an incomplete system TSO-C146c Class Gamma TSOA/LODA to an FMS with an existing TSO-C115b TSOA/LODA if there are any conflicts between the two TSOs.

(3) FMSs already incorporating GPS and baro-VNAV capability may qualify as TSO-C146c Class Gamma-2 navigation computer systems when receiving inputs from a TSO-C145c Class Beta-2 or Class Beta-3 sensor. The incomplete system TSO-C146c Class Gamma approval would be added to the TSO-C115b approval or replace the TSO-C129(AR) approval if one exists. Applicants are encouraged to seek an incomplete system Class Gamma- 2 navigation computer approval for these FMSs (or Class Gamma-1 for FMSs that don’t process vertical deviations) to provide full SBAS-based capability for enroute through lateral navigation (LNAV)/vertical navigation (VNAV).

Note: Several issues must be considered for FMSs integrating both baro-VNAV and GPS/SBAS to provide

LNAV/VNAV capability. For example; unambiguous navigation source and approach service level annunciation, discontinuities or jumps when switching from baro-VNAV to GPS/SBAS vertical guidance, and prioritizing when to use which source (see paragraphs 6-3.c, 15-2.a), and 17-5). (4) Localizer performance without vertical guidance (LP)/ localizer performance with vertical guidance (LPV) is considered a severe major/hazardous failure condition for misleading information (see paragraph 11-2.a). Applicants may consider a Class Gamma-3 incomplete system TSOA/LODA to provide LP/LPV navigation computer functions if the FMS incorporates level B software. Otherwise, applicants may consider a Class Delta-4 configuration when integrating LP/LPV capability if the FMS does not incorporate level B software since this configuration doesn’t require the FMS to process LP/LPV data (see paragraphs 3-2.e(5) and 3-2.e(6) below). The FMS could still operate as a Class Gamma-2 navigation computer for GPS/SBAS functions other than LP/LPV; or according to its TSO-C115b/C129(AR) authorization.

(5) For Class Delta-4 integrations, FMSs in typical federated avionics architectures do not need an incomplete system TSO-C146c Class Delta-4 TSOA/LODA since the FMS does not provide or process flight path deviation data or GPS/SBAS alerting functions during the final approach segment. The complete system (sensor, Class Delta-4 LP/LPV final approach segment capability, and display) will be confirmed at the time of installation.

(a) The FMS may provide an interface for pilot control of the Class Delta-4 equipment and may host database information such as the Final Approach Segment (FAS) data block for input to the Class Delta-4 equipment. The Class Delta-4 TSOA/LODA holder must list the specific compatible FMS(s), or provide a detailed description of the database information needed and the data format to establish FMS compatibility as a limitation in the installation manual.

(b) Non-federated FMS architectures, such as integrated modular avionics, may have the Class Delta-4 LP/LPV final approach segment capability residing within the FMS functions or components. These FMSs will need an incomplete system TSO-C146c Class Delta-4 TSOA/LODA and appropriate software level for the Class Delta-4 performance requirements listed in RTCA/DO-229D that they provide.

Note: Applicants with non-federated FMS architectures may also consider pursuing incomplete system TSO-C146c Class Gamma approval for the navigation computer functions/components. (6) An FMS that is part of an aircraft-level TSO-C146c Class Delta-4 integration normally provides the RNAV capability for the initial and intermediate approach segments to place the aircraft in proper position for the Class Delta-4 GPS/SBAS equipment to conduct the LP/LPV final approach segment. The FMS can also provide RNAV capability for the missed approach segment.

Note: RNAV capability for the initial, intermediate, and missed approach segments can be accomplished by the FMS according to its TSO-C115b and/or TSO-C129(AR) approval. However, the FMS will be limited to its approved functions per those TSOs or as modified if receiving PVT inputs from a TSO-C145(AR) sensor (see paragraphs 5-5.2.b and 5-5.2.c). 3-3. TSO-C161a/C162a. a. TSO-C161a, Ground Based Augmentation System Positioning and Navigation Equipment, defines an acceptable standard for GPS/GBAS equipment that provides precision approach capability and PVT information to navigation management equipment. TSO-C162a, Ground Based Augmentation System Very High Frequency Data Broadcast Equipment, defines an acceptable standard for GPS/GBAS equipment designed to receive a very high frequency data broadcast (VDB) and output the VDB messages to GPS/GBAS positioning and navigation equipment.

b. TSO-C161a and TSO-C162a invoke only the requirements in RTCA/DO-253C, Minimum Operational Performance Standards for GPS Local Area Augmentation System Airborne Equipment, dated December 16, 2008, that are needed to support Category I (CAT I) precision approach and, if applicable, the GPS/GBAS positioning service. The equipment may output PVT based on either the GPS/GBAS positioning service, or PVT from GPS or GPS/SBAS. The PVT based on GPS/GBAS is only available when the ground station supports the positioning service. TSO-C161a equipment must also obtain either TSO-C129a, TSO-C145, TSO-C146, or TSO-C196 TSOA. Requirements in RTCA/DO-253C needed to support precision approaches beyond CAT I are not invoked in these TSOs as these requirements have not been validated. Once validated, the FAA will either publish TSO revisions or new TSOs.

c. TSO-C161a and TSO-C162a compliant equipment does not address any RNAV capability. A partial missed approach capability is an option in the GPS/GBAS equipment but is not required (see note). RNAV capability for the initial, intermediate, and missed approach segments must be addressed during the aircraft GPS/GBAS integration (see paragraph 14-8.1).

Note: Equipment meeting the RTCA/DO-253C precision and navigation (PAN) requirements can include an optional capability to provide guidance for the initial, straight-out portion of the missed approach segment. However, this capability doesn’t provide guidance for the complete missed approach segment. 3-4. RNAV Multi-Sensor Equipment. a. TSO-C115b defines an acceptable certification standard for obtaining design and production approval for multi-sensor navigation systems or FMSs integrating data from multiple navigation sensors. There is no plan to withdraw TSO authorizations granted under TSO-C115a. Manufacturers of TSO-C115a equipment can continue production according to their TSOA/LODA. However, integrating GNSS into the multi-sensor navigation equipment is

considered a major change and requires an application for a TSO-C115b TSOA/LODA.

(1) TSO-C115b only addresses TSO-C129 Class B and C sensors because it was published prior to TSO-C129a, TSO-C145(AR), TSO-C161(AR), and TSO-C196. It is acceptable to integrate any GNSS sensor with TSO-C115b equipment.

(2) Applicants with equipment that has an existing TSO-C115b approval may add an incomplete system TSO-C129a Class A or TSO-C146c Class Gamma TSOA/LODA for the navigation computer functions. The navigation computer requirements in TSO-C129a or TSO-C146c will take precedence if there are any conflicts with the requirements in TSO-C115b (deviations to TSO-C115b need to be approved). See paragraphs 3-1 and 3-2 respectively for additional information on TSO-C129a and TSO-C146c incomplete system TSOA/LODAs.

b. Multi-sensor systems must also comply with the appropriate TSO requirements for the individual sensor; for example, TSO-C66c, Distance Measuring Equipment(DME) Operating Within the Radio Frequency Range of 960 to 1215 Megahertz, for DME equipment. Refer to AC 90-100 (latest revision), U.S. Terminal and Enroute Area Navigation (RNAV) Operations, for operational approval of terminal and enroute area navigation systems for use in the United States national airspace system.

Note: The multi-sensor navigation system must comply with TSO-C115b (or a later revision) when integrating GNSS sensors. It is not acceptable to use equipment certified to earlier revisions (see paragraph 3-5.b(1)). 3-5. Multiple TSO Authorizations. a. Multiple TSO authorizations may be granted for equipment that accomplishes multiple functions. However, the number of TSO markings on positioning and navigation equipment should be minimized to avoid confusion during installation and approval.

b. The following combinations of TSO authorizations must not be granted, as the TSOs either contradict each other or are superfluous to a TSO with broader scope:

(1) TSO-C115/C115a with TSO-C129(AR), TSO-C145(AR)/C146(AR), TSO-C196, or TSO-C161a/C162a).

(2) TSO-C129(AR) Class A with TSO-C146(AR) Class Gamma.

(3) TSO-C129(AR) Class B or Class C with TSO-C145(AR), TSO-C146(AR) or TSO-C196.

(4) TSO-C196 with TSO-C145(AR) or TSO-C146(AR).

Note: The intent is that combinations not specifically prohibited by paragraphs 3-5.b(1) through 3-5.b(4) are acceptable.

Chapter 4. Equipment Performance - Advisory Vertical Guidance. 4-1. Introduction. Positioning and navigation equipment may provide vertical path deviation guidance indications on a non-essential, not-required basis as an aid to help pilots meet barometric altitude restrictions. Equipment that has this capability typically uses GNSS or baro-VNAV, but may use any method to generate the vertical path information. Advisory vertical guidance does not provide approved vertical guidance deviation indications for operational credit. Only vertical guidance deviation indications for LNAV/VNAV or LPV approach procedures are approved for operational credit.

Note 1: Advisory vertical guidance is an optional capability implemented at the equipment manufacturer’s discretion for enroute, terminal, and/or approach operations; not a requirement for positioning and navigation equipment. Note 2: Paragraph 4-1 does not apply to instrument landing system (ILS). Note 3: We recommend that equipment manufacturers provide a means for pilots to inhibit advisory vertical guidance to support nonprecision approach training requirements. 4-2. Implementations. a. It is acceptable to provide advisory vertical guidance as a descent aid during oceanic/remote, enroute, and terminal operations.

b. GPS equipment without GPS-provided approved vertical capability (TSO-C129(AR), TSO-C196, TSO-C145/C146(AR) Operational Class 1) and no baro-VNAV integration in the aircraft may provide advisory vertical guidance deviation indications on any approach using the LNAV line of minima.

c. Some aircraft integrations may use GPS equipment without GPS-provided approved vertical capability (TSO-C129(AR), TSO-C196, TSO-C145/C146(AR) Operational Class 1) to provide lateral path deviation indications and an approved baro-VNAV installation to provide vertical path deviation indications for an approach to the LNAV/VNAV line of minima.

(1) This integration constitutes approved vertical guidance to conduct a charted instrument approach procedure to the LNAV/VNAV line of minima and should not be confused with advisory vertical guidance applications.

(2) There may be occasions where it is operationally advantageous to use the LNAV line of minima rather than the LNAV/VNAV minima during an instrument approach procedure. It is acceptable for approved baro-VNAV installations to provide advisory vertical

guidance when using the LNAV line of minima. However, during these operations, the flight crew must use the primary barometric altimeter as the primary reference for compliance with all altitude restrictions associated with the instrument approach procedure; including compliance with all associated step-down fixes.

Note 1: Baro-VNAV integrations may use non-GPS RNAV position sources to generate lateral path deviations for approaches that do not require GPS. Note 2: Baro-VNAV is subject to temperature and pressure altitude (i.e., correct altimeter setting) performance limitations that could potentially cause advisory vertical path guidance to fall below step-down fixes on LNAV approaches. d. During RNAV (GPS) instrument approach operations, TSO-C145/C146(AR) Operational Class 2 equipment may provide advisory vertical guidance when the procedure defines only the LNAV line of minima (i.e., procedures without a charted LNAV/VNAV and/or LPV line of minima). GPS/SBAS Operational Class 2 equipment is not capable of performing LP approaches, but may provide advisory vertical guidance for the LNAV line of minima on instrument approach procedures that define both an LNAV and LP line of minima. GPS/SBAS Operational Class 2 equipment may not provide advisory vertical guidance on instrument approach procedures with an LNAV line of minima published with LNAV/VNAV and/or LPV lines of minima. The reason is due to potential confusion over advisory versus approved vertical guidance and which line of minima applies. This human factors issue is even more critical when GPS/SBAS equipment “fails-down” to LNAV minima during the final approach segment if vertical guidance is lost during an LNAV/VNAV approach.

Note: There is no intent to preclude using baro-VNAV advisory vertical guidance for an LNAV approach provided it is selected prior to the final approach fix. See paragraph 17-5 when integrating baro-VNAV with GPS/SBAS vertical guidance. e. During RNAV (GPS) instrument approach operations, TSO-C145/C146(AR) Operational Class 3 equipment may provide advisory vertical guidance when the procedure defines only the LNAV and/or LP line of minima (i.e., procedures without a charted LNAV/VNAV and/or LPV line of minima). GPS/SBAS Operational Class 3 equipment may not provide advisory vertical guidance on instrument approach procedures with an LNAV line of minima published with LNAV/VNAV and/or LPV lines of minima. The reason is due to potential confusion over advisory versus approved vertical guidance and which line of minima applies. This human factors issue is even more critical for GPS/SBAS equipment that has a “fail-down” mode to LNAV minima during the final approach segment.

Note 1: LP approach procedures will never be published with other lines of minima that contain approved vertical guidance (i.e., LNAV/VNAV or LPV). LNAV and LP lines of minima can be published on the same approach

chart; and, it is acceptable to provide advisory vertical guidance during approach operations using these lines of minima. Note 2: There is no intent to prevent using baro-VNAV advisory vertical guidance for an LNAV approach provided it is selected prior to the final approach fix. See paragraph 17-5 when integrating baro-VNAV with GPS/SBAS vertical guidance.

f. TSO-C146(AR) Operational Class 4 (Functional Class Delta) equipment provides an “ILS look-alike” capability for LPV and LP only. GPS/SBAS Operational Class 4 equipment indicates LP by flagging the vertical guidance indications. It is acceptable for Class Delta equipment to provide advisory vertical guidance during approach procedures to LP minimums. However, it is not acceptable for Operational Class 4 equipment to provide advisory vertical guidance when the equipment “fails-down” from LPV to LNAV minima during the final approach segment due to potential confusion over advisory versus approved vertical guidance and which line of minima applies.

Note: Per RTCA/DO-229D it is not appropriate for GPS/SBAS Operational Class 4 equipment to “fail-down” from LP to LNAV. g. Advisory vertical guidance may be provided during very high frequency omni-directional range (VOR) and non-directional beacon (NDB) instrument approach operations (including overlays with “or GPS” in the title) and also for older GPS instrument approach operations titled “GPS RWY XX”.

4-3. Limitatations. a. There are no TSO requirements or MOPS standards regarding advisory vertical guidance minimum performance or how advisory vertical guidance is generated (see notes). Positioning and navigation equipment manufacturers can generally use their discretion when choosing to implement this capability. However, the equipment manufacturers cannot claim any operational or certification credit for advisory vertical guidance. When implementing advisory vertical guidance, the equipment manufacturer must provide an equipment limitation in the installation/instruction manual for inclusion in the airplane flight manual supplement (AFMS)/rotorcraft flight manual supplement (RFMS) and may also include the information in the operations manual. The limitation should state the following or be equivalent:

“Advisory vertical guidance deviation information is only an aid to help pilots comply with altitude restrictions. When using advisory vertical guidance, the pilot must use the primary barometric altimeter to ensure compliance with all altitude restrictions, particularly during instrument approach operations.”

Note 1: RTCA/DO-229D, referenced by the GPS/SBAS TSOs, does provide some cursory requirements related to advisory vertical guidance.

Note 2: The pilot using the primary barometric altimeter to ensure compliance with altitude restrictions is generally considered the mitigation for misleading or erroneous advisory vertical guidance information (i.e., 14 CFR XX.1309 compliance). However, each installation should be individually evaluated. b. The AFMS/RFMS and/or installation manual limitation does not preclude positioning and navigation equipment from outputting advisory vertical guidance deviations to an autopilot provided applicable autopilot requirements are satisfied. However, demonstrating autopilot compatibility or compliance is beyond the scope of this AC (see the latest revision of AC23-17, Systems and Equipment Guide for Certification of Part 23 Airplanes, AC 25.1329-1, Approval of Flight Guidance Systems, AC27-1, Certification of Normal Category Rotorcraft, or AC29-2, Certification of Transport Category Rotorcraft, for autopilot guidance information).

c. Positioning and navigation equipment manufacturers should consider providing a method to differentiate advisory vertical guidance indications from those used for approved vertical guidance to reduce potential crew confusion. If practical, the vertical deviation indications for each mode of vertical guidance should be unique and distinct.

Chapter 5. Equipment Performance - GNSS. 5-1. Introduction. a. GNSS The TSOs and MOPS for various types of GNSS equipment have been published over a span of several years. Despite efforts to harmonize all the GNSS documents, there are differences among the documents because of this publishing time gap; particularly for characterizing the broadband external interference noise environment. The broadband external interference noise is defined in RTCA/DO-235B, Assessment of Radio Frequency Interference Relevant to the GNSS L1 Frequency Band, dated March 1, 2008. Table 1 below summarizes the effective noise density for acquisition, tracking, and re-acquisition that GNSS equipment manufacturers should use when certifying new equipment. Equipment not meeting the effective noise density in table 1 (e.g., TSO-C129) may experience performance degradation as more GNSS satellites are launched. Equipment intended for use beyond 2020 in applications such as ADS-B should be qualified using the effective noise density shown in table 1.

Receiver Function Effective Noise Density (dBm/Hz) Initial Acquisition (GPS

Only)*

-172.2

GPS Tracking and Re-

acquisition

-171.9

SBAS Tracking and Re-

acquisition

-172.8

Table 1. Effective Noise Density for All GNSS Sources

b. It is acceptable to run GPS/SBAS testing separately using a total GNSS noise (IGNSS) of -172.8 dBm/Hz for accuracy verification and/or collection of the GPS/SBAS message loss rate data.

c. TSO-C145b/c, TSO-C146b/c and TSO-C196 equipment use a slightly earlier broadband external interference noise standard that is very close to the table 1 effective noise density. This equipment should not experience any difficulty with the increasing noise environment. However, manufacturers should use the values listed in table 1 when conducting the test scenarios described in RTCA/DO-229D and RTCA/DO-316 respectively.

Note: The respective MOPS and TSOs will be updated with the latest noise standards during the next revision cycle. d. TSO-C145a/C146a equipment complies with RTCA/DO-229C that uses the broadband external interference noise characterized by a previous RTCA/DO-235 revision. TSO-C145a/C146a equipment may experience performance degradation when other GNSS services are launched because future interference management and prevention will be based on the RTCA/DO-235B-defined broadband external interference noise environment.

e. TSO-C129(AR) equipment has no broadband external interference noise requirements comparable to RTCA/DO-235B. This equipment is more likely to experience

performance degradation when other GNSS services are launched because future interference management and prevention will be based on the RTCA/DO-235B-defined environment.

5-2. GPS (TSO-C129(AR) and TSO-C196 receivers). a. TSO-C129(AR) and TSO-C196 GPS equipment may be used on RNAV ‘T’ and ‘Q’ routes and for RNAV approaches to LNAV minimums within the contiguous United States. AC 90-100 (latest revision), contains specific information on performance requirements for RNAV routes.

b. Equipment requirements for ‘T’ and ‘Q’ routes in Alaska differ due to infrastructure and other unique characteristics of Alaskan airspace. Special Federal Aviation Regulation (SFAR) 97 does not permit using TSO-C129(AR) and TSO-C196 equipment on ‘T’ or ‘Q’ routes. However, there is an ongoing program to either revise or delete the SFAR 97 requirements. See enroute charts, Notices to Airman Publication (NTAP), and Notice to Airmen (NOTAMs) for latest equipment requirements in Alaska.

5-2.1 Antennas. a. It is recommended that receiver manufacturers seeking antennas for equipment certified to TSO-C129(AR) and TSO-C196 use antennas compliant with the applicable antenna TSOs described below (see paragraph 5-5.4 for a complete discussion on antenna re-use/replacement). However, combinations where both the antenna and receiver were certified together under TSO-C129/C129a will need a new certification if antennas meeting the original requirements are no longer available. Using a different antenna specification constitutes a major design change that requires a new TSOA/LODA.

(1) Either passive or active antennas are acceptable for TSO-C129(AR) and TSO-C196 GPS equipment. The current TSOs for passive and active antennas are listed below; but antennas previously certified to TSO-C144 are also acceptable (see Table 2).

(2) TSO-C144a, Passive Airborne Global Navigation Satellite System (GNSS) Antenna, that references RTCA/DO-228, Change 1, paragraph 2.2.1, defines an acceptable passive GPS antenna. A passive antenna is defined as one that does not include a low noise power amplifier as part of the antenna assembly.

(3) TSO-C190, Active Airborne Global Navigation Satellite System (GNSS) Antenna, that references RTCA/DO-301, Active Airborne Global Navigation Satellite System (GNSS) Antenna, dated December 13, 2006, defines an acceptable active GPS antenna. An active antenna is defined as one that includes a low noise power amplifier as part of the antenna assembly.

b. To aid compatibility findings, antenna manufacturers should identify the antenna minimum DC supply current, and nominal amplifier gain/tolerance for active antennas in the installation instructions. Receiver manufacturers need this information to define installation instructions that integrate the antenna and receiver. Additionally, the antenna manufacturer should identify the antenna minimum radiation pattern gain at 5 degrees and the antenna minimum gain/equivalent input noise temperature (G/T) ratio in the installation instructions so

that receiver manufacturers can take advantage of performance better than the minimum MOPS requirement. Documenting the improved performance facilitates the antenna/receiver installation and integration.

5-2.2 Sensors. a. TSO-C129(AR) and TSO-C196 are positioning and navigation systems with equipment limitations for the aircraft to have other navigation equipment available appropriate to the operation and for alternate airport flight planning (see paragraph 14-5).

Note: TSO-C129(AR) Class A equipment is a sensor/navigation computer combination. b. TSO-C129(AR) systems will not have an equipment limitation for the aircraft to have other navigation equipment in oceanic and remote areas provided additional requirements are met (see appendix 1).

c. TSO-C196 systems will not have an equipment limitation for the aircraft to have other navigation equipment in oceanic and remote areas provided the operator obtains a fault detection and exclusion (FDE) prediction program (see paragraph 5-2.3).

d. The intent for TSO-C196 equipment is to take advantage of signal processing improvements found in RTCA/DO-229D without the GPS/SBAS requirements. TSO-C196 equipment is intended as a direct replacement for Class B & C sensors certified to TSO-C129(AR). Additionally, TSO-C145(AR) equipment can also replace TSO-C129(AR) Class B & C equipment.

Note 1: Applicants will have to establish sensor/antenna compatibility when replacing TSO-C129(AR) sensors with either TSO-C196 or TSO-C145(AR) sensors.

Note 2: GPS/SBAS TSO-C146(AR) Class Gamma equipment is considered the direct replacement for a Class A sensor/navigation computer combination certified to TSO-C129(AR). 5-2.3 Prediction Program. a. GPS satellite failures have a non-intuitive impact on operational capability unlike conventional ground-based navigation aids that have a direct correlation between a facility outage (VOR fails) and the loss of an operational capability (VOR approach is unavailable). The operator is responsible for considering the effects of satellite outages during flight planning. Flight Standards defines the operational requirements to review NOTAMs, publish aeronautical information, or perform pre-departure receiver autonomous integrity monitoring (RAIM) or FDE availability checks. Prediction programs and availability assessments are essential to enabling the operator to fulfill this responsibility. The FAA provides these services through NOTAMs for TSO-C145(AR)/C146(AR) equipment for domestic navigation operations. The FAA plans to provide these services for all GNSS TSO equipment to support

ADS-B out. Paragraph 5-2.3 applies to operations that require a prediction program.

b. The following guidelines apply to any prediction program applicable to a particular model TSO-C129(AR) or TSO-C196 receiver that is intended to assess the operational impact of satellite outages for flight planning purposes. Some operators are required to have an approved prediction program. A prediction program with the characteristics described below is acceptable.

Note: The guidelines also apply to prediction programs for TSO-C145/C146(AR) if the equipment is intended for oceanic/remote operations without limitations (see appendix 1 and paragraph 5-3.2.a. c. TSO-C129(AR) equipment may have either a fault detection only algorithm or an FDE algorithm. TSO-C196 equipment is required by RTCA/DO-316 to have an FDE algorithm. The prediction program must include the appropriate capability for the intended receiver.

d. Operational guidance on predictive RAIM requirements may be found in the Aeronautical Information Manual (or other FAA guidance). The best performance model most likely comes from the original GPS equipment manufacturer.

Note: The FAA/Volpe prediction website did not include FDE prediction capability at the time this AC was published. However, the FAA/Volpe website is scheduled to include FDE prediction capability soon. e. The prediction program can be provided on any processing platform (in the GPS equipment or not).

f. The prediction program software should be developed in accordance with at least RTCA/DO-178B level D guidelines or equivalent.

g. The program should use either an algorithm identical to that used in the airborne equipment, or an algorithm based on assumptions for RAIM or FDE prediction that give a more conservative result.

h. The program should calculate RAIM or FDE availability based on the same satellite mask angle used in the equipment, but not less than 2 degrees for enroute/terminal operations or 5 degrees for approach.

i. The program should have the capability to manually or automatically designate GPS satellites which are expected to be out-of-service for the intended flight.

j. The program should allow the user to select the intended route (including declared alternates) and the time and duration of the flight. The program should identify the maximum RAIM or FDE outage time, and any predicted navigation capability outages.

(1) For approach operations, the maximum RAIM or FDE outage duration cannot exceed 5 minutes.

(2) For RNAV 1 and 2 operations, the maximum RAIM or FDE outage duration cannot exceed 5 minutes when TSO-C129(AR) or TSO-C196 receivers are used as the only means of RNAV 1 and 2 compliance.

(3) For oceanic/remote operations, the maximum FDE outage duration cannot exceed 25 minutes for RNP-4 operation, 34 minutes for RNP-10 operation, and 51 minutes for minimum navigation performance standards (MNPS) operation

Note: Prediction programs must use FDE for oceanic/remote operations. See appendix 1. k. For approach predictions, the program should allow the user to select the destination and expected time of arrival, and provide a RAIM or FDE availability prediction over an interval of at least +15 minutes computed in intervals of 5 minutes or less about the ETA.

l. Prediction programs supporting ADS-B out should meet the requirements in 14 CFR § 91.227. The program should identify the maximum RAIM or FDE outage time, and any predicted surveillance capability outages.

5-3. GPS/SBAS (TSO-C145/C146(AR) receivers). 5-3.1 Antenna. a. This paragraph provides guidance on acceptable GPS/SBAS antennas. See table 2 for a list of acceptable standard antenna TSOs matched with GPS/SBAS receiver TSO revision and operational class.

b. TSO-C190, that references RTCA/DO-301, defines an acceptable GPS/SBAS antenna.

Note: RTCA/DO-229D, paragraph 2.1.1.10 allows receiver manufacturers to designate manufacturer-specified antennas that take advantage of unique antenna performance rather than using the “standard” antenna defined by TSO-C190. c. A number of “passive” and “active” antennas were authorized under TSO-C144 for TSO-C145a/C146a compliant GPS/SBAS receivers. These antennas remain acceptable for those receiver installations according to their original TSOA/LODA. Receiver manufacturers are encouraged to use a TSO-C190 antenna whenever a replacement becomes necessary for a TSO-C144 antenna.

d. Major modifications to TSO-C145a/146a receivers that require a new TSOA/LODA upgrade to TSO revision ‘c’ (for operational class 2, 3, and 4) must use either a TSO-C190 or a receiver manufacturer-specified antenna that meets current requirements in RTCA/DO-229D

(such as, sensitivity and dynamic range, geostationary orbit satellite (GEO) bias, broadband interference, and group delay).

5-3.2 Sensor and Sensor/Navigation Computer Configuration. a. GPS/SBAS equipment has two different TSOs depending on whether the equipment is designed as a position sensor only; or, a sensor/navigation computer combination. TSO-C145c defines an acceptable standard for GPS/SBAS sensors (Class Beta) while TSO-C146c defines a complete sensor/navigation computer configuration (Class Gamma) and an “ILS look-alike” (Class Delta). Both TSOs reference RTCA/DO-229D for operations within and outside of the GPS/SBAS service provider coverage area. When outside of a GPS/SBAS service provider’s coverage area the receivers can revert to using FDE for integrity. The receiver will use GPS/SBAS integrity or FDE; whichever provides the best protection level. GPS/SBAS equipment will not have any limitations in oceanic and remote areas provided the operator obtains an FDE prediction program (see paragraph 5-2.3).

Note: GPS/SBAS equipment may continue using GEO data and range measurements when outside the GPS/SBAS service provider’s coverage area per the requirements in RTCA/DO-229D (RTCA/DO-229C for TSO revision ‘a’ equipment). b. GPS/SBAS equipment that complies with the standards implemented by TSO-C145(AR)/C146(AR) does not have an equipment limitation for the aircraft to be equipped with other navigation systems appropriate to the operation. With GPS/SBAS equipment it is also acceptable to flight plan an alternate using an RNAV approach to LNAV minimums at the alternate airport rather than a ground-based approach aid (see paragraph 14-6.1). Additionally, GPS/SBAS equipment may be used on RNAV ‘T’ and ‘Q’ routes within the contiguous United States and Alaska. AC 90-100 (latest revision), contains specific information on performance requirements for RNAV routes. These capabilities should be clearly indicated in receiver manufacturer’s operating instructions.

c. Although GPS/SBAS does not have an equipment limitation for other navigation systems onboard the aircraft, the receiver manufacturer’s operating instructions should encourage operators to retain back-up navigation systems to guard against outages or interference events.

d. GPS/SBAS equipment that complies with the ‘b’ or ‘c’ TSO revision has the capability to do LP approaches. TSO-C145a/C146a manufacturers may provide LP capability in their equipment. LP approaches use the horizontal accuracy and integrity values of LPV but do not provide vertical guidance. The intent is to provide LP approaches only at locations where some issue prevents implementing LPV vertical guidance; so, LP should be the exception rather than the rule. Therefore, LP is not operationally similar to a localizer-only approach on an ILS because LP and LPV are mutually exclusive. That is, LP and LPV lines of minima will never be on the same approach chart.

5-3.3 Navigation Database - Data Conversion for GPS/SBAS LNAV/VNAV Approaches. a. For LNAV/VNAV approaches collocated with LPV approaches, GPS/SBAS equipment must use the final approach segment (FAS) data block to define the final approach segment as described in RTCA/DO-229D. But, a FAS data block is not provided for stand-alone LNAV/VNAV approaches. The vertical path for such approaches is defined by the threshold location, threshold crossing height, and glidepath angle. However, the altitude of the threshold is published as the height above/below mean sea level (MSL), rather than as the height above/below the WGS-84 ellipsoid. Therefore, the published MSL height (interpreted as a height above/below the WGS-84 geoid) must be converted to height above/below the WGS-84 ellipsoid prior to being used. Actual decision altitude (DA) must be based on the barometric altimeter.

b. The data conversion is not considered alteration of data per RTCA/DO-200A, Standards for Processing Aeronautical Information, dated September 28, 1998, paragraph 2.4.2, since it changes the reference system but not the actual vertical location.

c. Receiver manufacturers may consider performing the conversion within the GPS/SBAS equipment or using a database process that provides threshold crossing height directly as height above/below the WGS-84 ellipsoid for GPS/SBAS approaches. However, GPS/SBAS integrations with baro-VNAV will need to address the issue of WGS-84 ellipsoid versus MSL height. This can be done through conversion or storing threshold data as both WGS-84 ellipsoid and MSL height to use for GPS/SBAS or baro-VNAV as appropriate.

5-4. GPS/GBAS (TSO-C161a/C162a receivers). The GPS/GBAS equipment supports Category I precision approach and, optionally, a GPS/GBAS differentially corrected positioning service (DCPS). When the GPS/GBAS avionics supports both levels of service, whether or not the DCPS is available is determined by the GPS/GBAS ground station. All GPS/GBAS ground stations provide precision approach service; but, not all ground stations are expected to provide DCPS.

5-4.1 Antennas. a. TSO-C190 that references RTCA/DO-301, defines an acceptable GPS/GBAS antenna.

b. TSO-C162a GPS/GBAS equipment also requires a VHF antenna to receive the GPS/GBAS satellite, path, and ground facility information broadcast. Installed antennas approved for ILS localizer/VOR can be used to receive the VDB signals. Unlike ILS ground antenna arrays, a GBAS VHF data broadcast transmitter may be located anywhere on the airport or in its vicinity. This means the VHF broadcast must be received from any direction. The ILS localizer/VOR antennas may, or may not, be included under TSO-C162a. See paragraphs 12-1.d, 14-7, and 20-2.b for installation considerations.

Note: RTCA/DO-253C gives GPS/GBAS equipment manufacturers an option for an antenna/receiver

combination or a receiver only. Both can be certified by TSO-C162a. 5-4.2 VHF Data Broadcast Receiving Equipment (TSO-C162a). The equipment should comply with the RTCA/DO-253C, section 2 requirements as modified by TSO-C162a. The equipment receives the GBAS VDB and outputs the VDB messages to the sensor/navigation computer (see section 5-4.3). TSO-C162a equipment must be used with TSO-C161a, or equivalent, equipment to provide Category I precision approach guidance or PVT based on GPS/GBAS.

5-4.3 Sensor/Navigation Computer (TSO-C161a). a. Category I Precision Approach.

(1) The equipment should comply with the RTCA/DO-253C, section 2 requirements as modified by TSO-C161a. The equipment outputs lateral and vertical deviations relative to an approach path defined in the VHF data broadcast. The entire precision approach must be contained within the region defined by the broadcast parameter Dmax. Outside of Dmax, the avionics may not use the differential corrections and the GPS/GBAS equipment will not provide deviations.

(2) GPS/GBAS approaches will not have LNAV/VNAV or LNAV minimums published with the GBAS landing system (GLS) procedure. There is no fail-down option if guidance is lost during a GPS/GBAS final approach.

b. Position Output.

(1) When the GPS/GBAS ground station does not support positioning service, the GPS/GBAS airborne receiver PVT solution must comply with either TSO-C129(AR) class B1 or C1, TSO-C196, or TSO-C145(AR) receiver outputs.

(2) When the GPS/GBAS ground station supports positioning service and the distance (slant range) between the aircraft and the GPS/GBAS reference point is less than or equal to the maximum GPS/GBAS usable distance, Dmax, the GPS/GBAS airborne receiver PVT solution should comply with either TSO-C161a, TSO- C129(AR) class B1 or C1, TSO-C196, or TSO-C145(AR) receiver outputs (i.e., GPS/GBAS-provided PVT possible).

(3) When the GPS/GBAS ground station supports positioning service and the distance (slant range) between the aircraft and the GPS/GBAS reference point is greater than the maximum GPS/GBAS usable distance, Dmax, the GPS/GBAS airborne receiver PVT solution should comply with either TSO- C129(AR) class B1 or C1, TSO-C196, or TSO-C145(AR) receiver outputs (i.e., no GPS/GBAS-provided PVT).

Note: The GPS/GBAS positioning service coverage region is defined by Dmax for GPS/GBAS ground stations supporting differential positioning service.

5-5. GNSS Upgrades. GNSS equipment installations have become very complex due to compatibility issues with the wide range of other installed equipment such as displays, flight guidance systems (FGS), terrain warning systems, etc. GNSS TSOs typically do not include requirements or standards related to installation compatibility or standardized outputs as part of the design and production approval. Therefore, it is recommended that, concurrent with their design and production approvals, equipment manufacturers also pursue an airworthiness approval that includes detailed installation instructions and equipment compatibility lists. See chapter 3 for more information regarding design, production and airworthiness approvals and paragraph 14-2.a for guidance on navigation displays during retrofit installations.

Note: GPS and GPS/SBAS equipment airworthiness approval is not considered novel or unusual per 14 CFR § 21.16 and applicants can use designees during the STC process. 5-5.1 Adding Additional GNSS equipment. Compatibility must be established between the existing GNSS equipment and whatever new GNSS equipment is added. As an example, some installation applicants may retain existing TSO-C129(AR) equipment and add GPS/SBAS equipment. In this instance, the original TSO-C129(AR) installation should not be re-evaluated, except for modifications made as part of the GPS/SBAS installation. The re-evaluation should be to the affected functions or performance. For example, if the equipment shares a GNSS antenna there will be additional signal loss for the original equipment and compliance to the original TSO-C129(AR) installation instructions should be verified.

5-5.2 Replacing GNSS Equipment. a. The TSO-C196 sensor is intended as a direct replacement for a TSO-C129(AR) Class B or C sensor provided the installation applicant or TSOA/LODA holder ensures compatibility with the display and navigation computer. The complete sensor/navigation computer/display system will continue to have the limitations noted in paragraphs 5-2.2.a and 14-5.

b. It is also possible to use either a TSO-C145(AR) sensor or a combined TSO-C145(AR)/C146(AR) Class Delta-4 sensor to replace a TSO-C129(AR) Class B or Class C sensor provided the installation applicant or TSOA/LODA holder ensures compatibility with the display and navigation computer. In such a sensor replacement, the aircraft operator can derive additional benefits and navigation capability such as removing the limitations noted in paragraphs 5-2.2.a and 14-5. However, the benefits do not automatically extend to enabling GPS/SBAS-provided LNAV/VNAV or LP/LPV capability. See paragraph 3-2 for compliance to TSO-C146c and the appropriate sections of RTCA/DO-229D as a complete system in the aircraft.

c. Using a TSO-C145(AR) or TSO-C196 sensor as a direct replacement for a TSO-C129(AR) sensor may be advantageous to remove performance or operational limitations

other than those associated with redundant navigation sources onboard the aircraft even though the complete system remains TSO-C129(AR). For example, the sensor processing improvements obviate the need to perform a RAIM prediction check 2 NM (nautical miles) prior to the final approach fix (FAF) as required by TSO-C129(AR).

Note: RTCA/DO-229D and RTCA/DO-316 both have a fault detection prediction requirement that applicants can use to perform the prediction check if needed for integration compatibility. But, the equipment requirement is there primarily to support an operational requirement for pre-departure fault detection checks when flying outside of the GPS/SBAS service provider’s coverage area. 5-5.3 GPS/SBAS Upgrade. It is possible to upgrade TSO-C196 equipment to TSO-C145c compliance. Receiver manufacturers who provide an upgrade path are encouraged to use an STC-AML to streamline the installation approvals (see paragraph 2-3).

Note: It may be difficult to upgrade TSO-C129(AR) or TSO-C145a/C146a equipment to TSO-C145c/C146c compliance. Proposed upgrades for this equipment to TSO-C145c/C146c will have to be carefully evaluated. 5-5.4 GNSS Antenna Re-Use/Replacement. a. There are no re-use or replacement possibilities for antennas certified under TSO-C129/C129a as part of the receiver TSOA/LODA. For receiver/antenna combinations certified by this method to use a different antenna design or specification is a major design change that invalidates the original TSOA/LODA.

b. For a TSO-C129/C129a receiver, it is possible to replace the original antenna if the antenna was certified to a separate antenna TSO. In this case, a TSO-C190 antenna, or antennas approved under TSO-C144(AR), can be used as replacements for any class of TSO- C129/C129a receiver.

c. For TSO-C196 receivers it is possible to re-use or replace both “active” and “passive” antennas approved under TSO-C144(AR). TSO-C190 “active” antennas can be used as well.

d. For TSO-C145/C146(AR) operational Class 1 receivers; and, all classes of TSO-C145a/C146a receivers (see note below), it is possible to re-use both “passive” and “active” antennas approved under TSO-C144(AR). TSO-C145/C146(AR) operational Class 1 receivers are limited to enroute through LNAV approaches.

(1) The standards for equipment previously certified to TSO-C145a/C146a do permit using either TSO-C144 “passive” or “active” antennas for all receiver operational classes. However, receiver manufacturers are encouraged to use a TSO-C190 antenna when

replacing the original antenna.

(2) If the receiver manufacturer chooses to not use a TSO-C190 antenna, they should use a TSO-C144 “active” antenna that complies with the intra-system noise environment, test procedures/methodologies, and 25 nanosecond differential group delay requirements found in RTCA/DO-301. Failure to do so may cause performance degradation due to GEO bias and an increasing broadband interference noise environment.

e. For TSO-C145b/C146b/C145c/C146c operational Class 2, 3, or 4 receivers, “Passive” TSO-C144(AR) antennas cannot be re-used. TSO-C190 describes the standard “active” antenna for TSO-C145b/C146b/C145c/C146c operational Class 2, 3, or 4 receivers. It may be possible to re-use an “active” TSO-C144 antenna for these receivers as a manufacturer-specified antenna per RTCA/DO-229D, paragraph 2.1.1.10.

f. In all cases a TSO approval does not guarantee antenna/receiver installation compatibility. Installation compatibility must be established by the antenna or receiver manufacturer and documented in the approved installation instructions. Also, there can be 14 CFR § 21.611 issues related to major versus minor alterations. Each project must be evaluated according to 14 CFR § 21.611 to address the alteration regulatory issues.

TSO-C144(AR)

Passive

TSO-C144

Active

TSO-C190

Antenna Type

Receiver Type

TSO-C129 TSOA Antenna/Receiver

Combination

TSO-C145a/C146a

All Classes

TSO-C145b/C146b/

C145c/C146c

Opn’l Class 1

X

X

X

TSO-C145b/C146b/

C145c/C146c

Opn’l Class 2,3,4

X

X

X

X

X

TSO-C129/C129a

All Classes

TSO-C196

GPS

X

X

X

TSO-C129/C129a

Combined Rec/Ant

X

X

X

See Note See Note See Note

TSO-C144(AR)

Passive

TSO-C144

Active

TSO-C190

Antenna Type

Receiver Type

TSO-C129 TSOA Antenna/Receiver

Combination

TSO-C145a/C146a

All Classes

TSO-C145b/C146b/

C145c/C146c

Opn’l Class 1

X

X

X

TSO-C145b/C146b/

C145c/C146c

Opn’l Class 2,3,4

X

X

X

X

X

TSO-C129/C129a

All Classes

TSO-C196

GPS

X

X

X

TSO-C129/C129a

Combined Rec/Ant

X

X

X

See Note See Note See Note

Table 2. Acceptable Standard Antennas

Note : An active TSO-C144 antenna may be acceptable for TSO-C145b/C146b/C145c/C146c Operational Class 2, 3, & 4 equipment as a receiver manufacturer-specified antenna per RTCA/DO-229D, paragraph 2.1.1.10. 5-5.5 Marking. The marking must be modified to reflect the new configuration and approval when

equipment is upgraded to a new TSO (such as from TSO-C196 to TSO-C145c Operational Class 1). This marking change can be accomplished by a certificated person in accordance with the TSOA/LODA holder’s instructions. A certificated person in this context is defined as one who is authorized under 14 CFR § 43.3, persons authorized to perform maintenance, rebuilding, and alterations.

5-6. Navigation Database. For all combined sensor/navigator GNSS equipment, the navigation database is an essential component for the equipment to perform its intended function. Guidelines pertaining to the navigation database can be found in AC 20-153 (latest revision). Particular attention should be paid to the specification of the data quality requirements as described in RTCA/DO- 200A, appendix B.

5-6.1 Database Installation Instructions. The TSOA/LODA installation instructions/manual must contain a limitation identifying the requirements for the navigation database. This limitation will also be included in the AFMS/RFMS.

5-6.2 Database Process. The RNAV multi-sensor equipment manufacturer is usually the last link in the aeronautical data processing chain, as the format for the data loaded in the final database is typically proprietary. The applicant for a TSOA/LODA must identify an aeronautical data process accessible to the equipment users. AC 20-153 (latest revision), Acceptance of Data Processes and associated Navigation Databases, provides an acceptable method for this aeronautical data process. The approval of the process is included as part of the TSOA/LODA for GNSS equipment.

5-7. GNSS Geometric Altitude. GNSS-provided geometric altitude is not adequate for compliance with air traffic control altitude requirements in the National Airspace System (NAS) or internationally. The primary barometric altimeter must be used for compliance with all air traffic control altitude regulations, requirements, instructions, and clearances. GNSS geometric altitude may be used to increase situation awareness, but must be clearly distinguished from a barometric source. The label GSL may be used to indicate GNSS sea level.

5-8. Terrain Awareness and Warning System (TAWS). GNSS equipment is used to provide positioning inputs to TAWS equipment. Each type of GNSS equipment described in chapter 5 is acceptable as an input to TAWS equipment.

Chapter 6. Equipment Performance - RNAV Multi-Sensor Equipment.

6-1. Introduction. This chapter provides guidance related to the basic functions and performance of a multi-sensor unit. This chapter identifies issues associated with equipment performance that applies to all types of equipment. Each individual sensor must meet the navigation performance and operation criteria contained in the respective TSO and AC applicable to that type sensor.

6-2. Navigation Database. For area navigation equipment, the navigation database is an essential component for the equipment to perform its intended function. Guidelines pertaining to the navigation database can be found in AC 20-153 (latest revision). Particular attention should be paid to the specification of the data quality requirements as described in RTCA/DO-200A, appendix B.

6-2.1 Database Installation Instructions. The TSOA/LODA installation instructions/manual must contain a limitation identifying the requirements for the navigation database. This limitation will also be included in the AFMS/RFMS.

6-2.2 Database Process. The RNAV multi-sensor equipment manufacturer is usually the last link in the aeronautical data processing chain, as the format for the data loaded in the final database is typically proprietary. The applicant for a TSOA/LODA must identify an aeronautical data process accessible to the equipment users. AC 20-153 (latest revision), Acceptance of Data Processes and associated Navigation Databases, provides an acceptable method for this aeronautical data process.

6-3. GNSS. a. When GNSS is integrated in an RNAV multi-sensor system, the GNSS position sensor should comply with the acceptable methods as defined by this AC in paragraph 5-2.2 for GPS not augmented by ground- or space-based systems, paragraph 5-3.2 for GPS/SBAS, and paragraph 5-4.2 for GPS/GBAS. The GNSS position sensor should be installed in accordance with guidelines provided in chapters 11 through 15 and 18 through 21.

Note: See paragraphs 14-6.8 and 14-8.16 for GNSS installation considerations regarding ground proximity warning system (GPWS) or TAWS alerting functions. b. See paragraph 3-2 for TSO compliance guidance on RNAV multi-sensor equipment integrating GPS/SBAS capability. RTCA/DO-229D, section 2, addresses the use of GPS/SBAS vertical position (referenced to WGS-84 ellipsoid) as used on the final approach segment of an LNAV/VNAV or LPV approach procedure or as advisory guidance on an LNAV approach

procedure. It is acceptable to provide advisory vertical guidance for LP approaches using the method described in RTCA/DO-229D for LNAV (see paragraph 4-2.d).

c. See paragraph 3-3 for TSO compliance guidance on RNAV multi-sensor equipment integrating GPS/GBAS capability.

d. Many RNAV multi-sensor systems have implemented baro-VNAV for use in all phases of flight, and baro-VNAV can be used for vertical guidance on an LNAV/VNAV approach procedure.

(1) The RNAV multi-sensor system manufacturer should address the GPS/SBAS and/or GPS/GBAS integration issues associated with equipment designs that also include baro-VNAV capability. In particular the RNAV multi-sensor equipment must provide a smooth guidance transition between baro-VNAV and GPS/SBAS and/or GPS/GBAS vertical guidance and a clear mode annunciation to the pilot.

(2) Paragraph 17-5 of this AC provides additional guidance for baro-VNAV, GPS/SBAS, and GPS/GBAS integrations.

6-4. DME/DME. The FAA is responsible for evaluating DME/DME coverage and availability against a minimum standard DME/DME RNAV system for each route and procedure. This paragraph defines the minimum performance and functions (baseline) for DME/DME RNAV systems intended to support RNAV 1 and RNAV 2 routes, as well as RNAV 1 departure procedures (DPs) and standard terminal arrival routes (STARs).

a. The DME/DME RNAV system must:

(1) Provide position update within 30 seconds of tuning DME navigation facilities.

(2) Auto-tune multiple DME facilities.

(3) Provide continuous DME/DME position updating.

Note: Given a third DME facility or a second pair has been available for at least the previous 30 seconds, there must be no interruption in DME/DME positioning when the RNAV system switches between DME stations/pairs. b. The FAA cannot ensure all DME signals within reception distance of United States airspace meet International Civil Aviation Organization (ICAO) standards. These could include non-United States DME facilities, or Department of Defense (DOD) maintained DME facilities excluded from the NAS database. DME/DME RNAV procedure design will only use DME facilities listed in the airport/facility directory (A/FD). Although a procedure design issue, applicants may mitigate this restriction by:

(1) Having the DME/DME RNAV system only use DME facilities listed in the A/FD.

(2) Require exclusion of non-NAS DME facilities from the aircraft’s navigation database when the RNAV routes or procedures are within reception range of these non-NAS DME facilities.

(3) Demonstrating to the FAA that their RNAV system performs reasonableness checks to detect errors from the non-NAS DME facilities and excludes these facilities from the navigation position solution when appropriate (e.g., using the ARINC 424 coding to preclude tuning co-channel DME facilities when the signals-in-space overlap). See paragraph 6-4.1 for guidance on reasonableness check testing.

c. When needed to generate a DME/DME position, the DME/DME RNAV system (also referred to as a FMS) must use, as a minimum, DMEs with a relative angle between 30 and 150. The FMS may use DME pairs outside these angles (for example, 20 to 160).

d. The RNAV system may use any receivable DME facility (listed in the A/FD) regardless of its location. When needed to generate a DME/DME position, as a minimum, the RNAV system must use an available and valid low altitude and/or high altitude DME anywhere within the following region around the DME facility:

(1) Greater than or equal to 3 NM from the facility;

(2) Less than 40 degrees above the horizon when viewed from the DME facility; and

(3) For facilities with an ARINC 424 figure of merit (FOM), the RNAV system may use the FOM value from table 3 as the acceptable, usable region.

The aircraft’s DME/DME RNAV system must be: If the ARINC 424 FOM is:

Less than or equal to: And less than: 0 40 NM from the facility 12,000 ft above facility elevation 1 70 NM from the facility 18,000 ft above facility elevation 2 130 NM from the facility -- 3 160 NM from the facility -- Table 3. DME Usable Range

Note 1: RNAV systems may use additional DME facilities (for example, a localizer (LOC)/DME facility may be used but is not required to be used for positioning). RNAV systems are not required to use the FOM value. Note 2: RNAV routes and procedures may include new FOMs with expanded service volumes.

(4) A valid DME facility:

(a) Broadcasts an accurate facility identifier signal;

(b) Satisfies the minimum field strength requirements; and

(c) Is protected from other interfering DME signals according to the co-channel and adjacent channel requirements.

e. There is no requirement to use VOR, LOC, NDB, IRU or attitude heading reference system (AHRS) during normal operation of the DME/DME RNAV system.

f. When the RNAV system is using a minimum of two DME facilities that satisfy the criteria in paragraph 6-4, and any other valid DME facilities not meeting that criteria, the 95% position estimation error must be better than or equal to 1.75 NM. A flight technical error (FTE) contribution not exceeding 1.0 NM (95%) may be assumed for RNAV 2 operations.

Note 1: This performance requirement is met for any navigation system that uses two DME stations simultaneously, limits the DME inclusion angle to between 30 and 150 and uses DME sensors that meet the accuracy requirements of TSO-C66c. If the RNAV system uses DME facilities outside the range identified above, the DME signal-in-space error can be assumed to be 0.1 NM 95%. Note 2: When using a minimum of two DME facilities satisfying the criteria above, the 95% position estimation error must be better than or equal to the following equation:

) sin(

) 2 2 ( ) 2 2 ( 2 2 ,2 ,2 ,1 ,1 / 

    

sis air sis air DME DME

   

Single facility reference, where: sis = 0.05 NM air is MAX {(0.085 NM, (0.125% of distance)}

 = inclusion angle (30o to 150o)

g. The RNAV system must ensure co-channel DME facilities do not cause erroneous guidance. This could be accomplished by including VOR reasonableness checking when initially tuning a DME facility, or excluding a DME facility when there is a co-channel DME within line-of-sight. See paragraph 6-4.1 for guidance on testing reasonableness checks.

Note: The DME assessment cannot use a DME facility when there is a co-channel DME facility within line-of-sight. h. The RNAV system must use operational DME facilities. DME facilities listed by NOTAM as unavailable (for example, under test or other maintenance) could still reply to an airborne interrogation. Therefore, non-operational facilities must not be used. An RNAV system may exclude non-operational facilities by checking the identification or inhibiting the use of facilities identified as not operational.

i. Operational mitigations defined to qualify equipment with this AC will not require pilot action during critical phases of flight, pilot monitoring of the RNAV system’s navigation updating source(s), or time intensive programming/ blackballing of multiple DME stations prior to executing a procedure.

Note 1: Blackballing single facilities listed by NOTAM as out-of-service and/or programming route/procedure-defined “critical” DME is acceptable when this mitigation requires no pilot action during a critical phase of flight. A programming requirement also does not imply the pilot should complete manual entry of DME facilities not in the navigation database. Instead, this allows RNAV systems to tune a critical DME, as appropriate to a specific route or procedure. Note 2: The critical phase of flight is normally from the final approach fix on an approach procedure through missed approach, or from field elevation to 2,500 ft above airport elevation on a departure. 6-4.1 Reasonableness Checks. a. Many FMSs perform a reasonableness check to verify valid DME measurements. Reasonableness checks are very effective against database errors or erroneous system acquisition (such as co-channel facilities), and typically fall into two classes:

(1) Those the FMS uses after it acquires a new DME. The FMS compares the aircraft’s position before using the DME to the aircraft’s range to the DME; and

(2) Those the FMS continuously uses, based on redundant information (for example, extra DME signals or IRU data).

b. The reasonableness checks are intended to prevent navigation aids from being used for navigation update in areas where the data can lead to radio position fixing errors due to co-channel interference, multipath, and direct signal screening. In lieu of using radio navigation aid published service volume, the navigation system should provide checks, which preclude use of duplicate frequency navigation aids (NAVAIDs) within range, over-the-horizon

NAVAIDs, and use of NAVAIDs with poor geometry.

c. Under certain conditions, reasonableness checks can be invalid.

(1) Do not assume a DME signal remains valid just because it was valid when acquired.

(2) Do not assume extra DME signals are available. The intent of this baseline is to support operations where the infrastructure is minimal (for example, when only two DMEs are available for parts of the procedure).

d. When an FMS manufacturer uses a reasonableness check to satisfy any criteria in this AC, they must test the effectiveness of the check under stressing conditions. An example of this condition is a DME signal that is valid at acquisition and “ramps off” during the test (similar to what a facility under test might do), when there is only one other supporting DME or two signals of equal strength. A “ramp off” rate would be significantly higher or slower than the normal range of groundspeed.

6-4.2 Performance Confirmation. a. New systems may demonstrate compliance with these criteria as part of the airworthiness approval. For existing systems, the applicant should determine compliance with the equipment and aircraft criteria in this chapter.

b. Aircraft manufacturers (TC holders) incorporating FMS and DME/DME positioning should review the available data for the integrated navigation system, and obtain additional data as appropriate, to determine compliance with the criteria in this AC.

c. Equipment manufacturers (typically DME and FMS TSOA/LODA holders) need to consider DME accuracy. DME sensors have been demonstrated to a variety of performance requirements per TSO-C66. TSO-C66 performance standards have evolved as follows:

(1) TSO-C66: (Aug 1960) RTCA/DO-99.

(2) TSO-C66a: (Sep 1965) RTCA/DO-151, accuracy requirement as total error with 0.1 NM attributed to ground facility, airborne equipment accuracy of 0.5 NM or 3% of distance, whichever is greater, with a maximum of 3 NM.

(3) TSO-C66b: (Nov 1978) RTCA/DO-151a, accuracy requirement as total error with 0.1 NM attributed to ground facility, airborne equipment accuracy of 0.5 NM or 1% of distance, whichever is greater, with a maximum of 3 NM.

(4) TSO-C66c: (Sept 1985) RTCA/DO-189, accuracy requirement as total error for the airborne equipment of 0.17 NM or 0.25% of distance, whichever is greater.

d. The accuracy required by TSO-C66c is adequate to support the criteria in this AC. DME equipment approved under revision ‘c’ does not require further evaluation for RNAV 1 and RNAV 2 operations. Applicants with equipment built to earlier TSO revisions may use the

following process to establish more accurate performance than originally credited to support RNAV 1 and RNAV 2 operations.

(1) Rather than relying on original demonstrated performance, the applicant may elect to review the original TSO or TC/STC test data to determine the demonstrated accuracy and/or make any appropriate changes to qualification tests to determine achieved accuracy.

Note: When conducting accuracy analysis, the DME signal-in-space error can be assumed to be 0.1 NM 95% (both inside and outside the published service volume). If demonstrating accuracy under bench or flight test conditions, the actual accuracy of the bench equipment or ground facility should be considered. (2) New testing should be performed under the same conditions used to demonstrate compliance with the original TSO-C66 standard.

(3) Applicants who have demonstrated more accurate DME performance should state the demonstrated accuracy in a letter to their customers.

6-4.3 Multi-Sensor System FMS. a. The FMS or aircraft manufacturer should review the available data for the integrated navigation system, and obtain additional data as appropriate, to determine compliance with the criteria in paragraph 6-4. Applicants who have determined compliance should state such in the operating instructions or AFMS/RFMS, along with any limitations (for example, if the pilot is expected to manually inhibit the use of facilities that are listed by NOTAM as unavailable). The applicant’s certification may limit the compliance to specific DME systems, or may reference any DME qualified to the accuracy requirements of TSO-C66c.

b. FMS accuracy is dependent on a number of factors, including: latency effects, the selection of DME facilities, the method of combining information from multiple DMEs, and the effects of other sensors used to determine a position. For FMSs using two (or more) DMEs at the same time and limiting the DME include angle to between 30 and 150, the accuracy requirement can be met if the DME sensors meet the accuracy requirements of TSO-C66c. For FMSs without these characteristics, the accuracy should be evaluated under poor DME geometry scenarios and should consider the demonstrated DME sensor accuracy. Poor geometry scenarios may include angles at the limits specified earlier, with or without additional DME facilities available outside those conditions.

c. Identify those conditions that would result in failure to meet the accuracy requirement, and the means to preclude those identified conditions.

6-5. VOR/DME. a. Multi-sensor equipment may incorporate VOR/DME updating and must meet the performance for the route to be flown. However, terminal and enroute RNAV implementation in the United States does not require using VOR, so any use of VOR must include

reasonableness checking and demonstrate that positional accuracy from an erroneous VOR signal-in-space will not exceed 1.75 nm for RNAV 2 and 0.87 nm for RNAV 1 (reference AC 90-100A, appendix 1, paragraph 2.h). This could be accomplished by not using VOR signals when DME/DME will be available or weighting and/or monitoring the VOR signal with DME/DME to ensure it does not mislead position results (for example, through reasonableness checks). See paragraph 6-4.1 for guidance on testing reasonableness checks.

b. For times when the multi-sensor equipment is using data from only a single collocated VOR/DME (such as during an RNAV (VOR/DME) approach), the total maximum position fixing error of the airborne multi-sensor equipment must be equal to or less than that shown in Table 4. To find the cross track (xtk) and along track (atk) error at this point, enter the table with the tangent distance in nautical miles and distance along track in nautical miles from the tangent point.

Along-Track Distance (NM) 0 5 10 15 20 25 30 35 40 50 60 70 80 90 100 110 120 130

0 xtk 0.6 0.8 1.1 1.4 1.7 2.0 2.3 2.6 3.2 3.9 4.5 5.2 5.8 6.4 7.1 7.7 8.4 atk 0.6 0.6 0.6 0.6 0.7 0.7 0.8 0.8 0.9 1.0 1.0 1.1 1.2 1.3 1.4 1.5 1.6

5 xtk 0.6 0.6 0.8 1.1 1.4 1.7 2.0 2.3 2.6 3.3 3.9 4.5 5.2 5.8 6.4 7.1 7.7 8.4 atk 0.6 0.6 0.7 0.7 0.7 0.8 0.8 0.8 0.9 0.9 1.0 1.1 1.2 1.3 1.4 1.5 1.6 1.7

10 xtk 0.6 0.7 0.9 1.1 1.4 1.7 2.0 2.3 2.6 3.3 3.9 4.5 5.2 5.8 6.5 7.1 7.7 8.4 atk 0.8 0.8 0.8 0.8 0.9 0.9 0.9 1.0 1.0 1.1 1.2 1.2 1.3 1.4 1.5 1.6 1.7 1.8

15 xtk 0.6 0.7 0.9 1.1 1.4 1.7 2.0 2.3 2.6 3.3 3.9 4.5 5.2 5.8 6.5 7.1 7.7 8.4 atk 1.0 1.0 1.0 1.1 1.1 1.1 1.2 1.2 1.2 1.3 1.4 1.4 1.5 1.6 1.7 1.7 1.8 1.9

20 xtk 0.6 0.7 0.9 1.2 1.4 1.7 2.0 2.3 2.7 3.3 3.9 4.6 5.2 5.8 6.5 7.1 7.7 8.4 atk 1.3 1.3 1.3 1.3 1.3 1.4 1.4 1.4 1.4 1.5 1.6 1.6 1.7 1.8 1.9 1.9 2.0 2.1

25 xtk 0.7 0.8 1.0 1.2 1.5 1.8 2.1 2.4 2.7 3.3 3.9 4.6 5.2 5.8 6.5 7.1 7.8 8.4 atk 1.5 1.5 1.6 1.6 1.6 1.6 1.6 1.7 1.7 1.7 1.8 1.9 1.9 2.0 2.1 2.1 2.2 2.3

30 xtk 0.7 0.8 1.0 1.2 1.5 1.8 2.1 2.4 2.7 3.3 3.9 4.6 5.2 5.9 6.5 7.1 7.8 8.4 atk 1.8 1.8 1.8 1.8 1.9 1.9 1.9 1.9 2.0 2.0 2.1 2.1 2.2 2.2 2.3 2.4 2.4 2.5

35 xtk 0.8 0.8 1.0 1.3 1.5 1.8 2.1 2.4 2.7 3.3 4.0 4.6 5.2 5.9 6.5 7.1 7.8 8.4 atk 2.1 2.1 2.1 2.1 2.1 2.2 2.2 2.2 2.2 2.3 2.3 2.4 2.4 2.5 2.5 2.6 2.7 2.7

40 xtk 0.8 0.9 1.1 1.3 1.5 1.8 2.1 2.4 2.7 3.3 4.0 4.6 5.2 5.9 6.5 7.1 7.8 8.4 atk 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.5 2.5 2.5 2.6 2.6 2.7 2.7 2.8 2.9 2.9 3.0

50 xtk 0.9 1.0 1.1 1.3 1.6 1.9 2.2 2.5 2.8 3.4 4.0 4.6 5.3 5.9 6.5 7.2 7.8 8.4 atk 2.9 2.9 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.1 3.1 3.2 3.2 3.3 3.3 3.4 3.4 3.5

60 xtk 1.0 1.0 1.2 1.4 1.7 1.9 2.2 2.5 2.8 3.4 4.0 4.7 5.3 5.9 6.6 7.2 7.8 8.5 atk 3.5 3.5 3.5 3.5 3.5 3.6 3.6 3.6 3.6 3.6 3.7 3.7 3.8 3.8 3.8 3.9 3.9 4.0

70 xtk 1.0 1.1 1.3 1.5 1.7 2.0 2.3 2.6 2.9 3.5 4.1 4.7 5.3 6.0 6.6 7.2 7.9 8.5 atk 4.1 4.1 4.1 4.1 4.1 4.1 4.1 4.2 4.2 4.2 4.2 4.3 4.3 4.4 4.4 4.4 4.5 4.5

80 xtk 1.1 1.2 1.4 1.6 1.8 2.1 2.3 2.6 2.9 3.5 4.1 4.7 5.4 6.0 6.6 7.3 7.9 8.5 atk 4.6 4.7 4.7 4.7 4.7 4.7. 4.7 4.7 4.7 4.8 4.8 4.8 4.9 4.9 5.0 5.0 5.0 5.1

90 xtk 1.2 1.3 1.4 1.6 1.9 2.1 2.4 2.7 3.0 3.5 4.2 4.8 5.4 6.0 6.7 7.3 7.9 8.6 atk 5.2 5.2 5.2 5.2 5.2 5.3 5.3 5.3 5.3 5.3 5.4 5.4 5.4 5.5 5.5 5.5 5.6 5.6

100 xtk 1.3 1.4 1.5 1.7 1.9 2.2 2.4 2.7 3.0 3.6 4.2 4.8 5.4 6.1 6.7 7.3 7.9 8.6 atk 5.8 5.8 5.8 5.8 5.8 5.8 5.9 5.9 5.9 5.9 5.9 6.0 6.0 6.0 6.1 6.1 6.1 6.2

110 xtk 1.4 1.5 1.6 1.8 2.0 2.3 2.5 2.8 3.1 3.6 4.2 4.9 5.5 6.1 6.7 7.3 8.0 8.6 atk 6.4 6.4 6.4 6.4 6.4 6.4 6.4 6.4 6.5 6.5 6.5 6.5 6.6 6.6 6.6 6.7 6.7 6.7

120 xtk 1.5 1.6 1.7 1.9 2.1 2.3 2.6 2.8 3.1 3.7 4.3 4.9 5.5 6.1 6.8 7.4 8.0 8.6 atk 6.9 7.0 7.0 7.0 7.0 7.0 7.0 7.0 7.0 7.1 7.1 7.1 7.1 7.2 7.2 7.2 7.3 7.3

130 xtk 1.6 1.7 1.8 2.0 2.2 2.4 2.6 2.9 3.2 3.7 4.3 4.9 5.6 6.2 6.8 7.4 8.0 8.7 atk 7.5 7.5 7.5 7.6 7.6 7.6 7.6 7.6 7.6 7.6 7.7 7.7 7.7 7.7 7.8 7.8 7.8 7.9 Table 4. 2D Accuracy Requirements for Equipment Using a Single Co-located VOR/DME

Note 1: Equipment error assumes a waypoint input resolution of 0.01 minute, and output resolution of 0.01 minute for approach and 0.1 minute otherwise. Note 2: Equipment error assumes the maximum allowable difference between the displayed cross-track deviation and the computed cross-track deviation. Note 3: Multi-sensor equipment accuracy shown in the above table does not necessarily satisfy accuracy requirements for operation in certain airspace. For

T a n g e n t D i s t a n c e N M

Continue reading ↓ 120 of 426 passages shown