AC 20-138D Airworthiness Approval of Positioning and Navigation Systems (Including Change 2)
This revision adds minor clarifications and new guidance material based on issues and questions since revision ‘C’ was published. There are several new changes such as: equipment capability versus installed limitations; clarifying database configuration versus equipment capability; adding step-down fixes to navigation databases; a new appendix for demonstrating radius to fix (RF) leg capability; and, including required navigation performance (RNP) prediction guidance for RNP authorization required approach (RNP AR APCH).
Advisory U.S. Department of Transportation Circular Federal Aviation Administration
Subject: Airworthiness Approval of Date: 4/7/16 AC No: 20-138D Positioning and Navigation Systems Initiated by: AIR-130 Change: 2
1. Purpose. Change 2 adds additional information and clarifications to AC 20-138D, Change 1 along with minor updates.
2. Principal Changes. The page control chart indicates which pages have changed.
PAGE CONTROL CHART
Remove Pages Dated 1-3 8 16-17 30 32-33 49 53-54 58 61-62 66 68 71 73-74 76 78 83-87 93 95-98 103 118 121 123-124 127 132-134
10/10/14 10/10/14 10/10/14 10/10/14 10/10/14 10/10/14 10/10/14 10/10/14 10/10/14 10/10/14 10/10/16 10/10/14 10/10/14 10/10/14 10/10/14 10/10/14 10/10/14 10/10/14 10/10/14 10/10/14 10/10/14 10/10/14 10/10/14 10/10/14
Insert Pages Dated 1-3 8 16-17 30 32-33 49 53-54 58 61-62 66 68 71 73-74 76 78 83-87 93 95-98 103 118 121 123-124 127 132-134
4/7/16 4/7/16 4/7/16 4/7/16 4/7/16 4/7/16 4/7/16 4/7/16 4/7/16 4/7/16 4/7/16 4/7/16 4/7/16 4/7/16 4/7/16 4/7/16 4/7/16 4/7/16 4/7/16 4/7/16 4/7/16 4/7/16 4/7/16 4/7/16
i
137 142 A1-1-A1-2 A2-1-A2-5 A2-7-A2-8
A2-12 A2-15 A3-1-A3-7 A7-13-A7-14 A7-17-A7-18
A8-1-A8-2
A10-1
Susan J. M. Cabler
10/10/14 137 4/7/16 10/10/14 142 4/7/16 10/10/14 A1-1-A1-2 4/7/16 10/10/14 A2-1-A2-5 4/7/16 10/10/14 A2-7-A2-8 4/7/16 10/10/14 A2-12 4/7/16 10/10/14 A2-15 4/7/16 10/10/14 A3-1-A3-6 4/7/16 10/10/14 A7-13-A7-14 4/7/16 10/10/14 A7-17-A7-18 4/7/16 10/10/14 A8-1-A8-2 4/7/16 10/10/14 A10-1 4/7/16
Acting Manager, Design, Manufacturing, &
Airworthiness Division Aircraft Certification Service
ii
Acting Manager, De ign, Manufacturing, &
Airworthiness Division Aircraft Certification rv1ce
Advisory U.S. Department of Transportation Circular Federal Aviation Administration
Subject: Airworthiness Approval of Date: 10/10/14 AC No: 20-138D Positioning and Navigation Systems Initiated by: AIR-130 Change: 1
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.
• 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 is available from the GNSS provider countries and RTCA to support service definition, service performance commitments, and minimum operational performance standards for multi-constellation equipment. ~~~~~
Table of Contents
Chapter 1. General Information … 1
1-1. Purpose … 1 1-2. Audience … 2 1-3. Cancellation … 2 1-4. Frequently Asked Questions … 3
Chapter 2. Technical Standard Order Authorization (TSOA) and Airworthiness Approval
Considerations - General … 10 2-1. Guidance for TSOA/Letter of Design Approval (LODA) and Airworthiness Approvals … 10 2-2. TSOA … 10 2-3. STC-Approved Model List (AML) … 11 2-4. Type Certificate … 11
Chapter 3. TSO Authorization … 12
3-1. TSO-C196(AR) … 12 3-2. TSO-C145(AR)/C146(AR) … 13 3-3. TSO-C161a/C162a … 14 3-4. TSO-C115(AR) … 15 3-5. TSO-C204/C205/C206 … 18 3-6. Multiple TSO Authorizations … 19
Chapter 4. Equipment Performance - Advisory Vertical Guidance … 21
4-1. Introduction … 21 4-2. Implementations … 21 4-3. Limitations … 24
Chapter 5. Equipment Performance - GNSS … 26
5-1. Introduction … 26 5-2. GPS (TSO-C129(AR) and TSO-C196(AR) receivers) … 27 5-2.1 Antennas … 27 5-2.2 Sensors … 28 5-2.3 Prediction Program … 29 5-3. GPS/SBAS (TSO-C145/C146(AR) receivers) … 31 5-3.1 Antenna … 31 5-3.2 Sensor and Sensor/Navigation Computer Configuration … 31 5-3.3 Navigation Database - Data Conversion for GPS/SBAS LNAV/VNAV Approaches … 33 5-4. GPS/GBAS (TSO-C161a/C162a receivers) … 33 5-4.1 Antennas … 33 5-4.2 VHF Data Broadcast Receiving Equipment (TSO-C162a) … 34 5-4.3 Sensor/Navigation Computer (TSO-C161a) … 34 5-5. GNSS Upgrades … 35
ii
5-5.1 Adding Additional GNSS Equipment … 35 5-5.2 Replacing GNSS Equipment … 35 5-5.3 GPS/SBAS Upgrade … 36 5-5.4 GNSS Antenna Re-Use/Replacement … 36 5-5.5 Marking … 38 5-6. Navigation Database … 38 5-6.1 Database Installation Instructions … 38 5-6.2 Database Process … 38 5-7. GNSS Geometric Altitude … 39 5-8. Terrain Awareness and Warning System (TAWS) … 39
Chapter 6. Equipment Performance - RNAV Multi-Sensor Equipment … 40
6-1. Introduction … 40 6-2. Navigation Database … 40 6-2.1 Database Installation Instructions … 40 6-2.2 Database Process … 40 6-3. GNSS … 40 6-4. DME/DME … 41 6-4.1 Reasonableness Checks … 45 6-4.2 Performance Confirmation … 45 6-4.3 Multi-Sensor System FMS … 46 6-5. VOR/DME … 47 6-6. INS/IRU … 49 6-7. INS/IRU – GNSS Integration … 50 6-8. INS/IRU - DME/DME Integration … 51
Chapter 7. Equipment Performance - RNP (General) … 53
7-1. Introduction … 53 7-2. Special Characteristics of RNP Instrument Approaches … 55 7-3. Special Characteristics of RNP 1.0 and RNP 2.0 Operations … 55
Chapter 8. Equipment Performance - RNP Approach … 56
8-1. Introduction … 56 8-2. Aircraft and System Criteria … 56 8-3. Performance and Functional Criteria for RNP Systems … 57 8-4. System Eligibility and Approval for RNP APCH Operations … 62
Chapter 9. Equipment Performance - RNP Enroute and Terminal … 63
9-1. Introduction … 63 9-2. Aircraft and System Criteria for RNP 2.0 and RNP 1.0 … 63 9-3. Performance and Functional Criteria … 65 9-4. System Eligibility and Approval for RNP 2.0 and RNP 1.0 Operations … 69 9-5. Rotorcraft Enroute, Terminal, and Offshore RNP 0.3 … 69 9-5.1 Introduction … 69 9-5.2 Rotorcraft and System Eligibility for Rotorcraft Enroute RNP 0.3 Operations … 69 9-5.3 Performance and Functional Criteria … 70 9-5.4 Approval for Rotorcraft RNP 0.3 Operations … 74
iii
Chapter 10. Equipment Performance – RNP Oceanic … 75
10-1. Introduction … 75 10-2. Aircraft and System Criteria for RNP 10 … 75 10-2.1 Performance Criteria … 75 10-2.2 System Criteria … 76 10-2.3 System Eligibility and Approval for RNP 10 Operations … 79 10-3. Aircraft and System Criteria for RNP 4.0 … 80 10-3.1 Performance and Functional Criteria for RNP 4.0 … 80 10-3.2 System Eligibility and Approval for RNP 4.0 Operations … 85
Chapter 11. Equipment Performance - Baro-VNAV … 86
11-1. General Limitations for Operations under IFR … 86 11-2. Baro-VNAV Equipment Performance for Operations under IFR … 87
Chapter 12. General Installation Considerations … 93
12-1. Introduction … 93 12-2. Failure Classification … 93 12-3. Software Considerations … 94 12-4. Hardware Considerations … 94 12-5. Installed Equipment Compatibility … 95 12-6. Installation Instructions … 95 12-7. Equipment Capability and Installed Limitations … 95 12-8. Final Approach Segment Step-Down Fixes in Navigation Databases … 96 12-9. Magnetic Variation Data and Onboard Database … 98 12-10. Environmental Considerations … 99 12-11. General Human Factors Considerations … 99 12-12. Path Definition and Collocated Navigation Aids … 102 12-13. Runway Position Monitoring … 103
Chapter 13. General Installation Considerations - Antennas … 104
13-1. Antenna Placement … 104 13-1.1 GNSS-Specific Considerations … 104 13-1.2 General Considerations … 105 13-2. Anti-Ice Protection … 105 13-3. Antenna Cables … 105 13-4. Structure … 105 13-5. Additional Guidance … 106
Chapter 14. General Installation Considerations - Sensors … 107
14-1. Introduction … 107 14-2. Positioning and Navigation Configuration Strapping … 107 14-3. Navigation Source Selection … 107 14-4. Dual Positioning and Navigation Installations … 108 14-5. Intermixing RNAV equipment … 108 14-6. Interface to FGS … 109 14-7. Interface to Magnetic/True Switch … 111 14-8. Interface to Air Data and Inertial Reference Systems … 111
iv
14-9. Antenna/Sensor Compatibility … 111 14-10. Interference - Electromagnetic Compatibility (EMC) … 112 14-11. Interface Requirements … 113
Chapter 15. Installation Considerations - GNSS … 114
15-1. Introduction … 114 15-2. Navigation Displays … 114 15-3. Failure Indications … 116 15-4. Documenting Effects of GNSS Outage … 116 15-5. Installed Performance Capability … 117 15-6. GPS Equipment … 117 15-7. GPS/SBAS Equipment … 118 15-7.1 Limitations … 118 15-7.2 LP Approach … 119 15-7.3 Update Rate … 119 15-7.4 Performance Monitoring … 119 15-7.5 System Status … 120 15-7.6 Annunciations … 120 15-7.7 Accessibility … 121 15-7.8 GPS/SBAS Glidepath Low Deviation Alerting Function … 121 15-8. GPS/GBAS VDB Receiver … 121 15-8.1 Interference – EMC … 122 15-8.2 Compatibility with Other Systems … 122 15-8.3 VDB Aircraft Implementation Loss … 122 15-9. GPS/GBAS Navigation Computer Receiver … 122 15-9.1 GPS/GBAS Equipment Intended for Category I … 123 15-9.2 GPS/GBAS Stand-Alone or MMR Equipment Intended for Category I … 123 15-9.3 Performance and Performance Monitoring … 124 15-9.4 Integrity … 124 15-9.5 Continuity of Navigation … 125 15-9.6 Fault Detection and Annunciation … 125 15-9.7 System Status … 125 15-9.8 Annunciation … 125 15-9.9 Accessibility … 126 15-9.10 Glidepath Capture … 126 15-9.11 Equipment Qualification … 126 15-9.12 Interoperability … 127 15-9.13 GPS/GBAS Glidepath Low Deviation Alerting Function … 127 15-10. Special Use Mission Equipment - Not for Navigation … 127
Chapter 16. Installation Considerations - RNAV Multi-Sensor Equipment … 128
16-1. Introduction … 128 16-2. Interface to Primary Navigation Display … 128 16-2.1 Non-numeric Deviation Displays … 129 16-2.2 Map Displays … 129 16-3. Interface to Remote Annunciator … 129 16-4. Unique Software Considerations … 130
v
16-5. Installed Performance Capability … 131
Chapter 17. Installation Considerations - RNP … 132
17-1. Introduction … 132 17-2. Flight Technical Error … 132 17-3. Radius to Fix (RF) Legs … 133 17-4. Interface to FGS … 133
Chapter 18. Installation Considerations - Baro-VNAV … 134
18-1. Failure Protection … 134 18-2. Manufacturer’s Instructions … 134 18-3. Annunciations … 134 18-4. Software Changes … 135 18-5. Integration with GNSS-Provided Vertical Guidance … 135 18-6. Glidepath Low Deviation Alerting Function … 137
Chapter 19. Installed Performance - Data Submittal … 138
19-1. Introduction … 138 19-2. Project Specific Certification Plan … 138 19-3. TSO Technical Data … 138 19-4. Review the installation manual … 139 19-5. Structural Analysis … 139 19-6. Power Supply … 140 19-7. Environment … 140 19-8. Database … 140 19-9. Operations manual or AFMS/RFMS … 140 19-10. Stand-Alone Navigation Equipment … 141 19-11. Ground and Flight Test Plans (functional and EMI/EMC testing) … 141
Chapter 20. Installed Performance - Test (General) … 142
20-1. Intended Function … 142 20-2. Power Supply … 142 20-3. Accuracy … 142 20-4. Human Factors … 142
Chapter 21. Installed Performance - Test (GNSS) … 143
21-1. Ground Test - GPS, GPS/SBAS, and GPS/GBAS … 143 21-1.1 Interference … 143 21-1.2 Antenna to Aircraft Navigation Reference Offset … 143 21-1.3 Sensor Installation … 144 21-1.4 Stand-Alone Navigation Equipment Installation … 144 21-2. Flight Test - GPS, GPS/SBAS, and GPS/GBAS … 144 21-2.1 Equipment Installation … 144 21-2.2 LP/LPV, LPV and GLS … 145 21-2.3 GPS/GBAS VDB Receiver Installation … 146
Chapter 22. Installed Performance - Test (RNAV Multi-Sensor Equipment) … 147
vi
22-1. Ground Test … 147 22-2. Flight Test … 147 22-2.1 Interface to FGS … 149 22-2.2 GNSS Precision Approach … 149
Chapter 23. Installed Performance - Test (Baro-VNAV) … 150
23-1. Introduction … 150 23-2. Ground Test … 150 23-2.1 Lab/Bench Tests and Equipment Data Evaluation … 150 23-2.2 Aircraft Installation Data Evaluation … 150 23-3. Flight Test … 151 23-3.1 Functional Flight Test … 151 23-3.2 Navigation Error Flight Test … 152 23-4. Follow-on Approval … 153
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-2 A2-3. RNP AR General Requirements … A2-4 A2-4. Requirements for RNP AR Approaches with RF Legs … A2-16 A2-5. Requirements for RNP AR Approach values less than 0.3 … A2-17 A2-6. Requirements for Approaches with a Missed Approach Segment Less Than RNP 1.0.A2-18 A2-7. Navigation Data Validation Program … A2-20 A2-8. Installation Considerations for RNP AR … A2-23
Appendix 3. Advanced RNP Functions … A3-1
A3-1. Introduction … A3-1 A3-2. Radius to Fix Leg Capability … A3-2 A3-3. Parallel Offsets … A3-5 A3-4. RNAV Holding … A3-6 A3-5. Scalable RNP … A3-6 A3-6. Fixed Radius Transitions … A3-7 A3-7. Time of Arrival Control … A3-7
Appendix 4. GNSS 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-2 A4-4. Horizontal Accuracy Pass/Fail Determination … A4-4 A4-5. Horizontal Velocity Figure of Merit Pass/Fail Determination … A4-4 A4-6. Vertical Velocity Accuracy Test Conditions Commensurate with NACV = 1 … A4-5 A4-7. Vertical Velocity Accuracy Pass/Fail Determination … A4-7
vii
A4-8. Vertical Velocity Figure of Merit Pass/Fail Determination … A4-7 A4-9. Additional Tests to Demonstrate Accuracy Commensurate with NACV = 2 … A4-8 A4-10. Test to Demonstrate HAE Output and Vertical Position Accuracy Metric … A4-8 A4-11. Test to Demonstrate Horizontal Position Accuracy Metric … A4-9 A4-12. Demonstrating True Track Angle/True Track Angle Validity … A4-11
Appendix 5. Sample Airplane/Rotorcraft Flight Manual Supplement … A5-1
A5-1. Introduction … A5-1 A5-2. Sample AFM(S)/RFM(S) PBN Capabilities and Qualification Basis … A5-9
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. RF leg Demonstration Templates … A7-1
A7-1. Introduction … A7-1 A7-2. Test Procedures Description … A7-3 A7-2.1. Departures … A7-3 A7-2.2. Arrival … A7-5 A7-2.3. Approaches … A7-7 A7-3. Test Guide … A7-15 A7-3.1. Initial Set-Up … A7-16 A7-3.2. Airborne Test Conditions … A7-17
Appendix 8. non-U.S. Constellations with GPS-Based GNSS … A8-1
A8-1. Introduction … A8-1
Appendix 9. Definitions and Acronyms … A9-1
A9-1. Definitions … A9-1 A9-2. Acronyms … A9-3
Appendix 10. Related Documents … A10-1
A10-1. FAA Advisory Circulars … A10-1 A10-2. FAA Technical Standard Orders … A10-3 A10-3. RTCA, Inc. Documents (RTCA/DO) documents … A10-4 A10-4. Other Documents … A10-6 A10-5. How to Get Related Documents … A10-6
List of Tables
Table 1. Effective Noise Density for All GNSS Sources … 26 Table 2. Acceptable Standard Antennas … 37 Table 3. DME Usable Range … 43 Table 4. 2D Accuracy Requirements for Equipment Using a Single Co-located VOR/DME … 48 Table 5. Error Elements … 49
viii
Table 6. Vertical Path Performance Limit for Baro-VNAV … 88 Table 7. Vertical Path Deviations … 89 Table 8. Typical Hazard Classifications … 93 Table 9. RNP FTE Performance … 132 Table 10. INS/IRU Accuracy After Loss of Radio Updating … 148 Table 11. Tailwind Component (VKTW) for Turn Calculations … A2-9 Table 12. Platform Dynamics for Horizontal Velocity Accuracy Test … A4-3 Table 13. Platform Dynamics for Vertical Velocity Accuracy Test … A4-6 Table 14. Alpha Departure Waypoints … A7-4 Table 15. Bravo Departure Waypoints … A7-5 Table 16. Arrival Waypoints … A7-7 Table 17. Approach 1 Waypoints … A7-9 Table 18. Approach 1 Vertical Error Budget … A7-9 Table 19. Approach 2 Waypoints … A7-11 Table 20. Approach 2 Vertical Error Budget … A7-11 Table 21. Approach 3 Waypoints … A7-13 Table 22. Approach 3 Vertical Error Budget … 7-13 Table 23. Approach 4 Waypoints … 7-15
List of Figures
Figure 1. RNAV Depiction … 6 Figure 2. RNP Depiction … 7 Figure 3. Minimum Straight Path Before DA … A2-20 Figure 4. Example Procedure Profiles … A7-2 Figure 5. Alpha Departure … A7-4 Figure 6. Bravo Departure … A7-5 Figure 7. Arrival … A7-6 Figure 8. Approach 1 … A7-8 Figure 9. Approach 2 … A7-10 Figure 10. Approach 3 … A7-12 Figure 11. Approach 4 … A7-14
ix
1-1. Purpose.
--
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).
Note: For standardization within this document, the acronyms GPS/SBAS and GPS/GBAS are used to indicate SBAS augmenting GPS and GBAS augmenting GPS respectively.
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).
Note: RNP AR was previously named RNP special aircraft and aircrew authorization required (SAAAR). The name was changed to RNP AR for international harmonization, but might not yet be standardized throughout all documents.
d. Barometric vertical navigation (baro-VNAV) equipment.
e. Appendix 8 provides preliminary information for manufacturers that wish to add new satellite constellations or additional frequencies to their GNSS capability. This AC will be updated as new documentation is developed for multi-constellation equipment.
f. This AC supersedes the airworthiness considerations contained in all revisions of AC 90-101, Approval Guidance for RNP Procedures with AR, and AC 90-105, Approval Guidance for RNP Operations and Barometric Vertical Navigation in the U.S. National Airspace System. Equipment previously approved per the airworthiness guidance in the 90-series ACs is still valid for the operations and conditions stated in their approvals. This AC does not replace the operational guidance found in the RNP 90-series ACs, but does replace the airworthiness guidance in the 90-series ACs. Also, this AC replaces the ACs listed in paragraph 1-3 by incorporating and updating the information they contained.
1-3. Cancellation.
g. This AC is not mandatory and does not constitute a regulation. This AC describes an acceptable means, but not the only means, to install positioning and navigation equipment. However, if you use the means described in the AC, you must follow it in all important respects.
h. Mandatory terms such as “must” used in this AC are only applicable when following the compliance method outlined. Other terms such as “should” or “recommended” are acceptable compliance methods applicants are encouraged to use. The term “may” is used for optional methods.
i. This AC revision is not intended to modify, change or cancel equipment design or airworthiness approvals previously in existence. However, new installation approvals (TC, ATC, STC or ASTC) should follow the guidance in this AC.
j. The guidance in this AC cannot ensure compliance with 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.
k. 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. This approval is typically achieved through a project specific issue paper.
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.
a. 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:
(1) AC 20-129, Airworthiness Approval of Vertical Navigation (VNAV) Systems for use in the U.S. National Airspace System (NAS) and Alaska.
(2) AC 20-130A, Airworthiness Approval of Navigation or Flight Management Systems Integrating Multiple Navigation Sensors.
(3) AC 20-138D Change 1, Airworthiness Approval of Positioning and Navigation Systems.
1-4. Frequently Asked Questions.
(4) AC 25-4, Inertial Navigation Systems.
b. This AC supersedes the airworthiness considerations in AC 90-45A, Approval of Area Navigation Systems for use in the U.S. National Airspace System. Equipment previously approved per the airworthiness guidance in AC 90-45A is still valid for the operations and conditions stated in their approvals.
1-4. Frequently Asked Questions.
This paragraph contains a list of questions concerning the guidance material in this AC. The responses to these questions are intended to help applicants interpret the guidance contained in this AC.
a. Ground Proximity Warning System/Terrain Awareness and Warning System (GPWS/TAWS) Mode 5 alert.
(1) Question: Is a GPWS or Class A TAWS Mode 5 alert a hard requirement to add localizer performance with vertical guidance (LPV) or GBAS landing system (GLS) capability?
(2) Answer: No. It is not the FAA’s intent to burden manufacturers and operators by changing the GPWS or TAWS functions. The intent is simply to recommend a glidepath alerting function to help prevent controlled flight into terrain during LPV, LNAV/VNAV, and GLS approaches. See paragraphs 15-7.8 and 15-9.13 for clarification and additional guidance.
b. Class B TAWS and LPV or GLS Capability.
(1) Question: Is a low glideslope alerting function for LPV or GLS required with Class B TAWS for compliance with the guidance in paragraphs 15-7.8 and 15-9.13?
(2) Answer: No. It is not the FAA’s intent to burden manufacturers and operators by changing the GPWS or TAWS functions. The intent is to simply recommend a glidepath alerting function to help prevent controlled flight into terrain during LPV, LNAV/VNAV, and GLS approaches.
c. Using the term vertical navigation (VNAV).
(1) Question: Doesn’t RTCA/DO-229D assign a very specific meaning to the term ‘VNAV’ and dictate the term’s specific uses for SBAS-based vertical navigation?
(2) Answer: No. RTCA/DO-229D, section 2.2.1.1.7 provides a recommended usage for the ‘VNAV’ label, but only requires that the label be used in a consistent manner. ‘VNAV’ can be used for an LNAV/VNAV approach procedure generated by GPS/SBAS-based or barometric-based vertical navigation capability (GPS/GBAS does not provide an LNAV/VNAV approach capability). The ‘VNAV’ label can also be used for an advisory vertical navigation function that provides vertical path deviation guidance indications on a
non-essential, not-required basis. Refer to the following AC 20-138D, chapters for additional information:
• Chapter 4, Advisory Vertical Guidance; • Chapter 11, Baro-VNAV; • Chapter 12, section 12-11, General Human Factors Considerations; • Chapter 15, section 15-7.6, GPS/SBAS Equipment Annunciations; and, • Chapter 18, section 18-5, Baro-VNAV integration with GNSS-Provided Vertical Guidance.
d. Tightly-coupled inertial navigation system/global positioning system (INS/GPS).
(1) Question: AC 20-138D, section 6-7 c. includes the following statement: "The FAA assumes that there is a limitation on the use of the GPS/inertial position data output to support enroute through lateral navigation (LNAV) approach only." Can you please explain the basis of this assumption? It appears to exclude the use of tightly coupled INS/GPS for oceanic use. Is this the intent? Or, is the intent to exclude it for use for LPV?
(2) Answer: Paragraph 6-6 addresses loosely-coupled systems and paragraph 6-7 addresses tightly-coupled systems. There is no intent to exclude either loosely-coupled or tightly-coupled INS/GPS from oceanic use. However, un-augmented GPS, even with tightlycoupled INS, is not adequate for vertical approach capability, and hybrid inertial vertical approach capability is not addressed in RTCA/DO-229D, appendix R. As stated in this AC, a GPS-based vertical approach capability requires GPS/SBAS or GPS/GBAS augmentation.
e. Flight management system (FMS) limitations.
(1) Question: AC 20-130A, section 5.d.(2) contained a limitation on FMS use and required an alternate means of navigation for the route flown. AC 20-138D does not include this section or make a mention of this limitation. What was the reasoning behind not including a similar section in AC 20-138D? Is there some higher level guidance that addresses this or is it left up to the safety analysis to address the need for an alternate means of navigation?
(2) Answer: It is important to differentiate between operational limitations and equipment performance limitations. AC 20-138D addresses equipment performance limitations while the 90-series ACs produced by Flight Standards address operational limitations (for example, 90-100, 90-101A, 90-105 for RNAV, RNP AR, and RNP respectively) as well as the Aeronautical Information Manual and operational rules (parts 91, 121, 135).
(a) AC 20-130A was written prior to implementing performance-based navigation concepts and the evolving RNAV/RNP-based National Airspace System. An FMS incorporating multiple navigation sensor inputs by its very nature has multiple sources of navigation, but the individual sensors have performance limitations on their navigation capabilities. Accordingly, the FMS functions will meet different requirements depending upon the sensors involved and the intended navigation capability. This AC addresses the performance limitations of the individual sensors contained in the document. These performance limitations
must be considered for the overall intended function at the aircraft level during the airworthiness approval (i.e., during the type certificate (TC), amended type certificate (ATC), or supplemental type certificate (STC) approval) to determine any limitations on the aircraft.
(b) In summary, operational rules dictate the navigation equipage requirements. It is up to the operator to determine how to comply based on their specific operating rules and mission needs.
f. Satellite Navigation Terminology.
(1) Question: Why are so many different names and acronyms (such as GNSS, WAAS, SBAS, etc.) used for GPS?
(2) Answer: The different names and acronyms used depend upon whether the topic is a generic, international reference to satellite navigation, or a particular State’s specific implementation.
(a) GNSS is used internationally to indicate any satellite-based positioning system or augmentation system. The acronym ‘GNSS’ includes satellite constellations, such as GPS, GLONASS, Galileo, or Beidou, along with augmentation systems such as ‘SBAS’ and ‘GBAS’; all of which provide a satellite-based positioning service.
(b) The acronyms ‘SBAS’ and ‘GBAS’ are the respective international designations for satellite-based and ground-based augmentation systems complying with the International Civil Aviation Organization (ICAO) standards and recommended practices (SARPs). Several countries have implemented their own versions of ‘SBAS’ and ‘GBAS’ that have specific names and acronyms. For example, WAAS is the U.S. implementation of an ‘SBAS’ while EGNOS is the European implementation. Refer to Appendix 9 for definitions of terms and acronyms.
Note: This AC uses the acronyms GPS/SBAS and GPS/GBAS throughout for consistency and clarity to indicate augmentation systems for the GPS constellation.
g. RNAV versus RNP.
(1) Question: Are technical standard order (TSO)-C129(AR) Class A1 GPS and TSO-C146(AR) Class Gamma GPS/SBAS equipment RNAV or RNP systems?
(2) Answer: Both. RNAV systems conform to the ICAO performance-based navigation specification for total system error (TSE). RNAV total system error is the 95% probability that the navigation system accuracy remains within the limits defined for the RNAV operation. For example, during an RNAV-1 operation the TSE remains within one nautical mile of the desired path 95% of the time (see Figure 1 below). RNP systems conform to a performance-based navigation specification based on RNAV capability that also includes requirements for on-board performance monitoring and alerting. For example, during an RNP
1 Nautical Mile 95% of flight time
--T-rack Centerline~
1 Nautical Mile 95% of flight time
1.0 operation, the TSE remains within one nautical mile of the desired path 95% of the time, and on-board performance monitoring provides the pilot with an alert when the probability that TSE exceeds 2xRNP is greater than 10-5 (see Figure 2 below). RNP is an RNAV subset that also includes a requirement to provide on-board navigation system accuracy performance monitoring and alerting which means an RNP system is also an RNAV system. GNSS equipment provides accuracy performance monitoring and alerting which, by definition, makes it both an RNAV and RNP capable system.
Note: TSO-C129(AR) Class B/C, TSO-C145(AR), and TSO-C196(AR) sensors provide both RNAV and RNP capability when interfaced to an appropriate navigation computer (such as TSO-C115d).
(a) By definition, TSO-C129(AR) Class A1 and all TSO-C146(AR) Class Gamma GNSS equipment provides an RNAV capability that includes on-board performance monitoring and alerting. This equipment has the capability to perform RNAV(GPS) approaches to at least the LNAV line of minima.
(b) RNAV(GPS) approaches require GPS, which includes on-board performance monitoring and alerting. Therefore, an RNAV(GPS) approach is an RNP procedure where the initial, intermediate, and missed approach segments are RNP 1.0. The LNAV final approach segment is RNP 0.3.
(c) None of the preceding statements should be confused with RNP AR that requires special aircraft and aircrew approval. Neither TSO-C129(AR) Class A1 GPS nor TSO-C146(AR) Class Gamma GPS/SBAS can qualify for RNP AR operations without additional aircraft and aircrew approvals (see appendix 2). No RNP AR procedures can be included in the navigation databases of equipment that is not approved for RNP AR operations. RNP AR approach procedures are titled RNAV(RNP) and have an “authorization required” designation printed on the charts.
Figure 1. RNAV Depiction
RNP 1 RNP 1 Alert to Pilot
ne
Track Centerline
1 N
ne
1 Nautical Mile 95% of flight time
1 Nautical Mile 95% of flight time
Track Centerline
1 Nautical Mile 99.999% of flight time
1 Nautical Mile 99.999% of flight time
The Key Difference: On-board Performance Monitoring and Alerting
Figure 2. RNP Depiction
h. Incomplete Technical Standard Order (TSO).
(1) Question: Is it possible to receive an incomplete TSOA for a GPS or GPS/SBAS receiver circuit card assembly providing the functional performance of a sensor unit?
(2) Answer: No. The basis for a TSOA is that the applicant has sufficient control over the design and production to assure the system meets the minimum performance standard published by the FAA. However, we do allow for incomplete systems to obtain an authorization, as explained in the latest revision of AC 21-46, Technical Standard Order Program.
(a) The incomplete authorizations are applicable to a complete unit that performs a subset of the required performance or functionality of the TSO (see AC 21-46 (latest revision), paragraph 5-3). A GNSS receiver circuit card assembly is not a complete unit; it is a part that must be incorporated into another box to function properly. AC 20-170 (latest revision) Integrated Modular Avionics Development, Verification, Integration, and Approval Using
RTCA/DO-297 and Technical Standard Order-C153, addresses a somewhat similar situation for integrated modular avionics (IMA). But, navigation and non-navigation avionics equipment that incorporate GNSS receiver circuit card assemblies are not an IMA. Therefore, the IMA guidance is not applicable.
(b) However, the FAA recognizes that GNSS receiver circuit card assemblies are more than “component parts” and fundamentally provide the GNSS sensor functional capability. In essence, the only difference between a complete GNSS sensor unit and a receiver circuit card assembly is the sensor unit includes a power supply and enclosure shielding. But this difference is significant relative to the performance tests in the minimum operational performance standard (MOPS) specified by the GNSS TSOs. The concern is that a bare receiver circuit card assembly could pass the MOPS performance testing in isolation, but not maintain that performance when integrated into another device where it might be exposed to significant radio frequency interference from other circuit card assemblies or devices. The FAA has created three new TSOs to address this concern and provide certification credit for the functional capabilities in GNSS receiver circuit card assemblies. But the GNSS receiver circuit card assembly’s end-user must repeat selected MOPS performance tests with the circuit card assembly installed in the end-use equipment and apply for the applicable GNSS sensor unit TSO (see paragraph 3-5).
i. Incorporating Step-down Fixes in Navigation Databases.
(1) Question: The latest ARINC 424 format has fields for both named and unnamed step-down fixes. Is it acceptable for equipment manufacturers to include approach procedure step-down fixes in the navigation database; particularly when LPV capability is included?
(2) Answer: Yes. But ARINC 424 is not a TSO-specified standard, so there is no “requirement” to include step-down fixes or use all the fields. Having step-down fixes in the navigation database can present challenges for the airworthiness approval when LPV capability is included since step-down fixes are not applicable to LPV and the LPV requirements are designed to mimic an instrument landing system (ILS). The airworthiness applicant must ensure there is no confusing or disparate information presented to flight crews due to the cockpit arrangement. This can be a significant issue in legacy cockpits that have limited display capabilities. See paragraph 12-8 for guidance when including step-down fixes in the navigation database.
j. Using RTCA Inc. document (RTCA)/(DO)-178C Software Considerations in Airborne Systems and Equipment Certification, dated December 13, 2011.
(1) Question: Is it acceptable for equipment manufacturers to use RTCA/DO-178C in lieu of RTCA/DO-178B?
(2) Answer: Yes. In the U.S. it is acceptable for software development to use revision ‘C’ for TSOs that specify revision ‘B’ thru the deviation process. The project ACOs may approve deviation requests to use revision ‘C’ in lieu of revision ‘B’ without Headquarters
coordination. Refer to AC 20-115C for additional guidance on software qualification, including re-using software qualified to previous RTCA/DO-178 revisions.
2-2. TSOA.
Chapter 2. Technical Standard Order Authorization (TSOA) and Airworthiness
Approval Considerations - General.
2-1. Guidance for TSOA/Letter of Design Approval (LODA) and Airworthiness Approvals.
Title 14 CFR part 21; subparts D, E, and O provide the regulatory basis defining changes to TC (major/minor changes to aircraft type design), STC, and TSOAs. The regulations and 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 are available for positioning and navigation-related equipment and components (see appendix 10 of this AC). New TSOs 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) Positioning and navigation equipment has become increasingly more complex and workload intensive with no standardized pilot interface. The human factors evaluation of the equipment can be subjective.
(3) There is no 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 and data process assurance levels. For example: a decision by the positioning and navigation equipment manufacturer to develop system software to RTCA/DO-178B Level C, may limit installation eligibility if that equipment contributes to failure conditions of other systems that perform critical functions to a higher software design assurance level.
Note: AC 20-115C provides guidance on using RTCA/DO-178C including re-using software qualified to previous RTCA/DO-178 revisions.
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
2-4. Type Certificate.
positioning and navigation installation STCs solely to avionics manufacturers.
c. The installation manual and other data approved during the TSOA process can be used as a source of approved data to support an installation airworthiness compliance finding provided the data is applicable to the installation airworthiness requirements (see AC 21-50 (latest revision), Installation of TSOA Articles and LODA Appliances).
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.
3-1. TSO-C196(AR).
Chapter 3. TSO Authorization.
3-1. TSO-C196(AR).
a. TSO-C196(AR), Airborne Supplemental Navigation Sensors for Global Positioning System Equipment Using Aircraft-Based Augmentation, defines an acceptable standard for GPS equipment without ground-based or space-based augmentations. The TSO has been updated to revision ‘b’ for harmonization with TSO-C129a’s cancellation and for TSO-C206 circuit card assemblies. TSO-C196(AR) is intended as the aircraft-based augmentation GPS sensor standard for TSOA/LODA applicants. TSO-C196(AR) equipment has a performance limitation that requires other positioning and navigation systems appropriate to the operation on-board the aircraft.
Note: TSO-C129a has been cancelled, but this does not affect equipment with an existing TSOA/LODA (see paragraph 3-1.c).
b. TSO-C196(AR) defines GPS sensor equipment that incorporates many processing improvements found in the GPS/SBAS equipment 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 (or later revision), Airborne Navigation Sensors Using the Global Positioning System (GPS) Augmented by the Wide Area Augmentation System (WAAS), sensor approved as a TSO-C196b sensor. It is acceptable for TSO-C196b applicants to take certification credit by re-using data developed during a previous revision ‘b’ or later TSO-C145 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(AR) 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 (revision ‘d’ implements RTCA/DO-229D, Change 1). Both RTCA/DO-229D and RTCA/DO-229D, Change 1 meets or exceeds the performance requirements for TSO-C196b. The original RTCA/DO-178B or ‘C’ documentation can be re-used if there are no software changes.
(2) Applicants seeking a TSO-C196b TSOA/LODA based on a previously approved revision ‘b’ or later TSO-C145 sensor must maintain separate part numbers for each unit. It is not acceptable to have both a TSO-C145(AR) and TSO-C196(AR) TSOA/LODA simultaneously on the same article (see paragraph 3-6.b(4)).
Note: Maintaining separate part numbers might only require different software part numbers.
3-2. TSO-C145(AR)/C146(AR).
(3) It is acceptable for TSOA/LODA applicants with revision ‘b’ or later TSO-C145 sensors to simply disable the GPS/SBAS tracking loops in their equipment to apply for a TSO-C196b TSOA/LODA. The applicant will need to supply substantiation that the SBAS tracking loops are permanently disabled along with the data from their revision ‘b’ or later TSO-C145 TSOA/LODA.
(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 all RTCA/DO-316 requirements not addressed in RTCA/DO-229C, and requirements that are more stringent such as enroute/terminal mode accuracy and the broadband external interference noise environment.
c. TSO-C129a was cancelled effective October 21, 2011, but there is no plan to withdraw TSO-C129(AR) authorizations. TSO-C129a cancellation will not affect existing authorizations. Manufacturers can continue production according to their existing TSO-C129(AR) TSOA/LODA. Additionally, the equipment is still eligible for installation according to existing airworthiness approvals and is eligible to receive new airworthiness approvals.
(1) No new TSO-C129a TSOAs/LODAs will be granted.
(2) Major changes to an existing TSO-C129a equipment design will require a new application according to 14 CFR 21.619(b) for either TSO-C145d, TSO-C146d or TSO C196b.
3-2. TSO-C145(AR)/C146(AR).
a. TSO-C145d, Airborne Navigation Sensors Using the Global Positioning System (GPS) Augmented by the Satellite-Based Augmentation System (SBAS) and TSO-C146d, Stand- Alone Airborne Navigation Equipment Using the Global Positioning System (GPS) Augmented by the Satellite Based Augmentation System (SBAS) define an acceptable standard for GPS/SBAS equipment. There is no equipment performance limitation for GPS/SBASequipped aircraft to have other positioning and navigation systems on-board.
Note: Refer to the appropriate operating rules and operational guidance documents for equipage requirements.
b. RTCA/DO-229D referenced by the GPS/SBAS TSOs will remain as the MOPS for single-frequency GPS/SBAS equipment. Future multi-frequency/multi-constellation equipment will have a separate MOPS and TSO.
c. There is no plan to withdraw authorizations to the earlier TSO revisions, so manufacturers of TSO-C145/C146 revision ‘a’ through ‘c’ 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.
3-3. TSO-C161a/C162a.
--
d. 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.
e. The difference between revisions ‘c’ and ‘d’ to the GPS/SBAS TSOs is: recognizing TSO-C204/C205 circuit card assemblies; and using Change 1 to RTCA/DO-229D.
f. 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.
g. Displays or navigation computers (such as FMSs) may receive a TSO-C146d Class 1, 2, or 3 (functional Class Gamma) incomplete TSOA/LODA provided they meet the applicable Class Gamma requirements in RTCA/DO-229D and are linked by part number to compatible TSO-C145(AR) 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.
Note: See paragraph 3-4 for additional information on FMS incomplete TSO-C146c Class Gamma TSOA/LODAs and Class Delta-4 FMS implementations.
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 position/velocity/time (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 a TSO-C145d, TSO-C146d, or TSO-C196b 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
3-4. TSO-C115(AR).
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 15-9.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. TSO-C115(AR).
a. TSO-C115d, Required Navigation Performance (RNP) Equipment Using Multi- Sensor Inputs 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 earlier TSO-C115 revisions. Manufacturers of earlier TSO-C115 revisions can continue production according to their TSOA/LODA; and the equipment is still eligible for installation in accordance with the guidance in this AC. However, integrating GNSS into TSO-C115/C115a multi-sensor navigation equipment is considered a major change and requires an application for a TSO-C115dTSOA/LODA.
(1) TSO-C115b only addressed TSO-C129 Class B and C sensors because it was published prior to TSO-C129a, TSO-C145(AR), TSO-C161(AR), and TSO-C196(AR). It is acceptable to integrate any GNSS sensor with TSO-C115b equipment.
Note: The multi-sensor navigation system or FMS must comply with TSO-C115 revision ‘b’ (or a later revision) when integrating GNSS sensors if TSO-C115 is the approval basis. It is not acceptable to use systems certified to earlier TSO-C115 revisions for GNSS sensor integration (see paragraph 3-6.b(1)).
(2) 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 12-2.a). Equipment manufacturers may design FMSs for either a TSO-C146d Class Gamma-3, or Class Delta-4 architecture when integrating LP/LPV capability.
(a) A TSO-C115b (or later revision) FMS designed as a Class Gamma-3 architecture typically has level B software for the LP/LPV processing functions. It is acceptable to have the GPS/SBAS capability and level B software partitioned from other functions in the FMS. See paragraph 3-4.b for additional information on incomplete TSO-C146c Class Gamma TSOA/LODAs.
(b) TSO-C146d Class Delta-4 provides an ILS look-alike for LP/LPV final approach segment-only capability. A TSO-C115b (or later revision) FMS designed for a Class Delta-4 architecture does not process LP/LPV inputs; does not output LP/LPV deviations, path
construction, alerts, etc.; and, does not require the FMS to have a TSO-C146d TSOA/LODA. The aircraft integration must include a GPS/SBAS sensor that has a TSO-C146d Class Delta-4 TSOA/LODA. See paragraph 3-4.c for additional information on Class Delta-4 implementations.
b. FMS manufacturers may add an incomplete TSO-C146d TSOA/LODA to FMSs certified to TSO-C115b (or later revision). An appropriate operational class incomplete TSO-C146d Class Gamma TSOA/LODA provides an established means for the installed FMS to demonstrate navigation computer compliance as a GPS/SBAS system.
Note 1: FMSs that do not meet the applicable RTCA/DO-229D Class Gamma performance requirements can still receive 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 associated with a TSO-C129(AR) sensor (see paragraphs 5-5.2.b and 5-5.2.c).
Note 2: There is significant overlap in requirements between TSO-C146d Class Gamma implementation of RTCA/DO-229D and TSO-C115d implementation of RTCA/DO-283B Minimum Operational Performance Standards for Required Navigation Performance for Area Navigation requirements. Where requirements overlap exists it is acceptable to re-use compliance information from RTCA/DO-229D as the method of demonstrating RTCA/DO-283B compliance. However, applicants remain responsible to ensure all RTCA/DO-283B requirements are satisfied.
Note 3: TSO-C146d Class Gamma has alert limits for navigation system error (NSE) at 1 x RNP value and assumes a fixed, manual flight technical error (FTE). The TSO-C146d Class Gamma FTE assumption and NSE alert meets the 2 x RNP TSE alerting requirement for RNP operations. TSO-C115d does not assume a fixed FTE value which allows applicants to trade off FTE and NSE when meeting the 2 x RNP TSE alerting requirement.
(1) TSO-C146d will take precedence when adding an incomplete TSO-C146d Class Gamma TSOA/LODA to an FMS with an existing TSO-C115b or later TSOA/LODA if there are any conflicts between the two TSOs.
(2) TSO-C115d requires the FMS meet the minimum performance standard documentation and qualification requirements for Class A or Class B specified in sections 2.1 and 2.2 of RTCA/DO-283B. Class A includes full VNAV and advanced RNP capability while Class B includes only 2-dimensional RNP navigation functions. Class B applicants that wish to
--- ----
include baro-VNAV capability or receive advanced RNP recognition must comply with the appropriate RTCA/DO-283B requirements. See RTCA/DO-283B, Table 2-13 for a complete list of the required Class A and Class B functions. The baro-VNAV guidance in this AC must be used when including baro-VNAV for approach capability. See appendix 3 for guidance on advanced RNP recognition.
(3) FMSs may qualify as TSO-C146d Class Gamma navigation computer systems when receiving inputs from a TSO-C145d Class Beta sensor. An incomplete TSO C146d Class Gamma approval (Gamma-2 or -3 as appropriate) can be added to the TSO-C115b (or later revision) approval, or replace the TSO-C129(AR) approval if one exists, to provide GPS/SBAS-based VNAV approach capability. Class Gamma-1 can be used for FMSs that don’t intend to process GPS/SBAS vertical deviations.
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.b, 16-2.a, and 18-5).
c. For Class Delta-4 architectures, FMSs in typical federated avionics architectures do not need an incomplete TSO-C146d Class Delta-4 TSOA/LODA for LPV capability 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 with Class Delta-4 TSOA/LODA, level B path, and display) will be confirmed at the time of installation. See paragraph 15-2.a regarding displays and path for legacy aircraft retrofit installations previously certified with ILS.
(1) It is acceptable for the Class Delta-4 sensor to reside within the FMS itself provided the LP/LPV outputs are not processed or altered by the FMS (similar to an ILS).
(2) The FMS may provide an interface for pilot control of the Class Delta-4 equipment (such as selecting the approach) and may host the Final Approach Segment (FAS) database 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 interface description to establish FMS compatibility in the installation manual.
(3) At the aircraft level, Class Delta-4 implementations depend upon the entire path for the guidance deviations complying with a severe major/hazardous failure condition in modern aircraft with digital data busses. See paragraph 15-2.a regarding displays and path for legacy aircraft retrofit installations previously certified with ILS.
(4) 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. The applicable modules for these FMSs will need a TSO-C146d Class Delta-4 TSOA/LODA and appropriate software level for the Class Delta-4 performance
3-5. TSO-C204/C205/C206.
requirements listed in RTCA/DO-229D that they provide.
Note: It is also acceptable for applicants with non-federated FMS architectures to consider pursuing incomplete TSO-C146d Class Gamma approval for the navigation computer functions/components.
(5) An FMS that is part of an aircraft-level TSO-C146d Class Delta-4 integration normally provides the RNP 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 also provides the RNP capability for the missed approach segment.
Note: RNP capability for the initial, intermediate, and missed approach segments can be accomplished by the FMS according to its TSO-C115b (or later revision) or other GNSS TSO 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).
d. Multi-sensor systems must also comply with the appropriate TSO requirements for the individual sensors that are integrated. For example, if distance measuring equipment (DME) is integrated, then the system must also comply with 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 U.S. national airspace system.
3-5. TSO-C204/C205/C206.
a. The FAA created three new TSOs to recognize the functional capability of GNSS sensor circuit card assemblies and enable end-use manufacturers to incorporate these devices for navigation and non-navigation uses. The intent is to ease the GNSS sensor TSO burden for end-use equipment manufacturers; particularly for non-navigation equipment such as ADS-B or TAWS. But FMS, multi-mode receiver, or other navigation equipment manufacturers could also benefit from these TSOs.
b. The three circuit card assembly TSOs are matched to the three existing GNSS sensor TSOs as follows:
• TSO-C205 to TSO-C146d Class Delta-4
---
Note: TSO-C205 is not appropriate for TSO-C146d Class Gamma functionality since Class Gamma is a combined sensor/navigation computer/display. However, TSO-C204 can be used for the sensor portion of a Class Gamma unit similar to using TSO-C204 in an FMS or multi-mode receiver.
3-6. Multiple TSO Authorizations.
c. Appendix 1 in TSO-C145d/C146d/C196b contains information on the MOPS performance tests the end-use manufacturer must re-accomplish to receive the appropriate TSOA. The end-use manufacturer must mark their equipment with the appropriate GNSS sensor TSO and assumes full responsibility for the GNSS sensor TSOA per the 14 CFR Part 21 Subpart O regulations.
d. The purpose of the new TSOs is to provide certification credit to the end-use equipment manufacturer for the following items performed by the circuit card assembly manufacturer:
• compliance with the requisite MOPS section 2 requirements, • hardware/software development, • failure condition classification, and; • partial MOPS performance testing.
However, the circuit card assembly TSOs have limitations requiring the end-use manufacturer to apply for the latest revision of TSO-C145, TSO-C146 Class Delta-4, or TSO-C196, consistent with the circuit card assembly TSO.
e. The end-use equipment manufacturer receives credit for the items in paragraph 3-5.d by virtue of the circuit card assembly TSO. To receive a GNSS sensor TSOA the end-use equipment manufacturer data submittal is:
(1) The TSO on the circuit card assembly;
(2) The repeated MOPS performance testing according to the GNSS TSO appendix 1;
(3) All other documentation associated with the GNSS sensor TSO, including environmental testing.
3-6. 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(AR), or TSO-C161a/C162a).
(3) TSO-C129(AR) Class B or Class C with TSO-C145(AR), TSO-C146(AR) or TSO-C196(AR).
(4) TSO-C196(AR) 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-2. Implementations.
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 ILS.
Note 3: We recommend that equipment manufacturers provide a means for pilots to inhibit advisory vertical guidance to support non-precision 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(AR), 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(AR), 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 (see paragraphs 12-8 and 18-2.b).
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 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.
(1) It is possible for GPS/SBAS Operational Class 2 equipment to also provide advisory vertical guidance for LNAV minima on instrument approach procedures that also contain LNAV/VNAV or LPV lines of minima as published, but with the additional considerations listed below. The reason is due to the wide range of displays, cockpit configurations, and potential confusion over “advisory” versus “approved” vertical guidance and which line of minima applies.
(a) LNAV with “advisory” vertical guidance must only be selectable prior to the FAF.
(b) The “advisory” vertical guidance indication must be unambiguous and easily distinguishable from the “approved” vertical guidance indication.
(c) The installation instructions/manual (or equivalent documents) must define the minimum display capability and cockpit configuration.
(d) The equipment must have an installation limitation or method to inhibit the function for non-qualifying installations.
(2) It is not acceptable for GPS/SBAS Operational Class 2 equipment to provide “advisory” vertical guidance in a “fail-down” mode from LNAV/VNAV to LNAV minima during the final approach segment.
Note 1: GPS/SBAS equipment manufacturers should exercise care when implementing “advisory” vertical guidance for LNAV minima collocated with LNAV/VNAV or LPV minima as published. The cockpit configuration and display capability can influence the
ability to provide an unambiguous, easily distinguishable vertical guidance indication during the airworthiness approval.
Note 2: Both the design approval applicant and airworthiness approval applicant have a responsibility to ensure the implementation is properly configured. Airworthiness approval applicants should contact their ACO early for concurrence on the proposed implementation.
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).
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, either GPS/SBAS or baro-VNAV, during approach operations using these lines of minima.
Note 2: Per RTCA/DO-229D it is not appropriate for GPS/SBAS Operational Class 3 equipment to “fail-down” from LP to LNAV.
(1) It is possible for GPS/SBAS Operational Class 3 equipment to also provide advisory vertical guidance for LNAV minima on instrument approach procedures that also contain LNAV/VNAV or LPV lines of minima as published, but with the additional considerations listed below. The reason is due to the wide range of displays, cockpit configurations, and potential confusion over “advisory” versus “approved” vertical guidance and which line of minima applies.
(a) LNAV with “advisory” vertical guidance must only be selectable prior to the FAF.
(b) The “advisory” vertical guidance indication must be unambiguous and easily distinguishable from the “approved” vertical guidance indication.
(c) The installation instructions/manual (or equivalent documents) must define the minimum display capability and cockpit configuration.
(d) The equipment must have an installation limitation or method to inhibit the function for non-qualifying installations.
(2) It is not acceptable for GPS/SBAS Operational Class 3 equipment to provide
4-3. Limitations.
“advisory” vertical guidance in a “fail-down” mode from LPV or LNAV/VNAV to LNAV minima during the final approach segment.
Note 1: GPS/SBAS equipment manufacturers should exercise care when implementing “advisory” vertical guidance for LNAV minima coincident with LNAV/VNAV and display capability can influence the ability to provide an unambiguous, easily distinguishable vertical guidance indication during the airworthiness approval.
Note 2: Both the design approval applicant and airworthiness approval applicant have a responsibility to ensure the implementation is properly configured. Airworthiness approval applicants should contact their ACO early for concurrence on the proposed implementation.
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. Limitations.
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)/rotorcraft flight manual (supplement) (AFM(S)/RFM(S)) 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 GPS/SBAS-provided 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 AFM(S)/RFM(S) 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 AC 23-17, Systems and Equipment Guide for Certification of Part 23 Airplanes, AC 25.1329-1, Approval of Flight Guidance Systems, AC 27-1, Certification of Normal Category Rotorcraft, or AC 29-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.
5-1. Introduction.
Chapter 5. Equipment Performance - GNSS.
5-1. Introduction.
a. There have been questions on whether GNSS is an RNAV or RNP system. The answer is GNSS is both an RNAV and RNP system because RNP is a subset of RNAV that also includes a requirement to provide on-board navigation system accuracy performance monitoring and alerting. Therefore, an RNP system is also capable of RNAV. GNSS equipment provides accuracy performance monitoring and alerting which, by definition, makes it an RNP-capable system. Paragraph 1-4.f contains a frequently asked question and more detailed answer explaining RNAV, RNP and GNSS qualification. Chapters 7 - 10 provide more information about RNP.
b. 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 publication 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(AR)) 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
c. 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.
d. TSO-C145b/c and TSO-C146b/c 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.
Note: RTCA/DO-229D, Change 1 contains the latest noise standards and is implemented by TSO-C145d/C146d. TSO-C196(AR) equipment also incorporates the Table 1 effective noise density.
5-2. GPS (TSO-C129(AR) and TSO-C196(AR) receivers). › 5-2.1 Antennas.
e. 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.
f. 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.
g. Improperly used or installed GNSS re-radiators can present misleading information to GNSS equipment. Equipment manufacturers should consider measures to mitigate against the use of erroneous data for GNSS position and navigation solutions. Possible measures to consider are: implementing or enabling cross-checks of GNSS sensor data against independent position sources and/or other detection monitors using GNSS signal metrics or data.
5-2. GPS (TSO-C129(AR) and TSO-C196(AR) receivers).
a. TSO-C129(AR) and TSO-C196(AR) GPS equipment may be used on RNAV ‘T’ and ‘Q’ routes and for RNAV approaches to LNAV minimums within the contiguous U.S.. AC 90-100 (latest revision) contains specific information on performance requirements for RNAV routes.
Note: TSO-C129a has been cancelled, but this does not affect equipment with an existing TSOA/LODA (see paragraph 3-1.c).
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 provides guidance on flying in Alaska. Alaska Q routes require GNSS (TSO-C129(AR), TSO-C196(AR), TSO-C145(AR) or TSO-C146(AR)) and radar surveillance. Alaska T routes require TSO-C145(AR) or TSO-C146 (AR). 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(AR) 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 as a unit under TSO-C129/C129a will need a new certification if antennas meeting the original TSOA are no longer available. Using a different antenna specification constitutes a major design change that requires a new TSOA/LODA unless the original
5-2. GPS (TSO-C129(AR) and TSO-C196(AR) receivers). › 5-2.2 Sensors.
TSOA/LODA contains part numbers for multiple antennas.
(1) Either passive or active antennas are acceptable for TSO-C129(AR) and TSO-C196(AR) 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, 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(AR) 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 15-6).
Note 1: TSO-C129(AR) Class A equipment is a sensor/navigation computer combination.
Note 2: TSO-C129a has been cancelled, but this does not affect equipment with an existing TSOA/LODA (see paragraph 3-1.c).
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(AR) 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).
5-2. GPS (TSO-C129(AR) and TSO-C196(AR) receivers). › 5-2.3 Prediction Program.
d. The intent for TSO-C196(AR) equipment is to take advantage of signal processing improvements found in RTCA/DO-229D without including the GPS/SBAS requirements. TSO-C196(AR) 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 sensors.
Note 1: Applicants will have to establish sensor/antenna compatibility when replacing TSO-C129(AR) sensors with either TSO-C196(AR) 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, review published aeronautical information, and 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 currently provides availability service through NOTAMs for GPS/SBAS equipment for domestic navigation operations, and plans to provide prediction services through the aeronautical information system. Either the FAA (through NOTAM or aeronautical information system) or the service provider provides these services for GPS/GBAS equipment for domestic navigation operations depending upon the specific ground facility status; Federal or non-Federal. 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(AR) 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(AR) 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 has transitioned to the service availability prediction tool (SAPT) for RAIM predictions which is available at www.sapt.faa.gov. However, SAPT does not provide FDE predictions for oceanic operations.
e. The prediction program can be provided on any processing platform (in the GPS equipment or elsewhere).
f. The prediction program software should be developed in accordance with at least RTCA/DO-178B or ‘C’ 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(AR) 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.0 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). SAPT does not provide FDE predictions for oceanic operations.
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 estimated
---
time of arrival.
5-3. GPS/SBAS (TSO-C145/C146(AR) receivers). › 5-3.2 Sensor and Sensor/Navigation Computer Configuration.
l. Prediction programs supporting ADS-B out should meet the requirements in 14 CFR 91.227(c)(1)(i) and 14 CFR 91.227(c)(1)(iii). 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. antenna.
TSO-C190, that references RTCA/DO-301, defines an acceptable GPS/SBAS
Note: RTCA/DO-229D, paragraph 2.1.1.10 allows receiver manufacturers to designate manufacturer-specified antennas to take advantage of unique antenna performance rather than using the “minimum 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 the latest TSO revision (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-C145d defines an acceptable standard for GPS/SBAS sensors (Class Beta) while TSO-C146d defines two configurations; a complete sensor/navigation computer (Class Gamma) and an “ILS look-alike” (Class Delta). Both TSOs reference RTCA/DO-229D, Change 1 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(GPS) approach to LNAV minimums at the alternate airport rather than a ground-based approach aid (see paragraph 15-7.1). Additionally, GPS/SBAS equipment may be used on RNAV ‘T’ and ‘Q’ routes within the contiguous U.S. 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.
Note: Refer to the appropriate operating rules and operational guidance documents for equipage requirements.
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. Class 3 and Class 4 GPS/SBAS equipment that complies with the TSO revision ‘b’ or later 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 approved vertical guidance deviation indications for operational credit. 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.
e. GPS/SBAS equipment manufacturers need to use caution when implementing LP capability because some LP procedures cannot support a visual descent angle due to obstructions. The FAS datablock glide path angle field coding uses a zero in these instances. Equipment manufacturers need to ensure a zero in the glide path angle field does not cause unintended software issues; for example, a divide by zero problem.
f. Manufacturers that request a deviation from the LP capability requirement in TSO C145d/C146d for their Class 3 or Class 4 GPS/SBAS equipment must provide an appropriate limitation for the installation instructions (or equivalent installation documentation) as part of their TSO application package. The limitation must be included in the AFM(S)/RFM(S).
5-4. GPS/GBAS (TSO-C161a/C162a receivers). › 5-4.1 Antennas.
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, Change 1. 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 since it changes the reference system but not the actual vertical location (reference RTCA/DO-200B, Standards for Processing Aeronautical Information, dated June 18, 2015, paragraph 2.4.2)
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 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 13-1.1.b, 15-8, and 21-2.3 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 GPS/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. GPS/GBAS (TSO-C161a/C162a receivers). › 5-4.3 Sensor/Navigation Computer (TSO-C161a).
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-C196(AR) or TSO-C145/C146(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-C196(AR) or TSO-C145/C146(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-C196(AR) or TSO-C145/C146(AR) receiver outputs (i.e., no GPS/GBAS-provided PVT).
Note 1: The GPS/GBAS positioning service coverage region is defined by Dmax for GPS/GBAS ground stations supporting differential positioning service.
5-5. GNSS Upgrades. › 5-5.2 Replacing GNSS Equipment.
Note 2: These paragraphs are consistent with TSO-C161a. Applicants may use TSO-C129(AR) GPS receivers if the outputs are shown to be equivalent to TSO-C196(AR).
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 15-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(AR) 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 15-6.
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 and 15-6. 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-C146d and the appropriate sections of RTCA/DO-229D, Change 1 as a complete
5-5. GNSS Upgrades. › 5-5.4 GNSS Antenna Re-Use/Replacement.
--
system in the aircraft.
c. Using a TSO-C145(AR) or TSO-C196(AR) 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 retains its original TSO-C129(AR) certification basis. 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 the original TSO-C129(AR) TSOA.
Note: RTCA/DO-229D, Change 1 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 for TSO-C196(AR) equipment or when flying outside of the GPS/SBAS service provider’s coverage area for TSO-C145(AR) equipment.
5-5.3 GPS/SBAS Upgrade.
It is possible to upgrade TSO-C196(AR) equipment to TSO-C145d 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-C145d/C146d compliance. Proposed upgrades for this equipment to TSO-C145d/C146d 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(AR) 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-C145/C146 revision ‘b’ or later 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-C145/C146 revision ‘b’ or later 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
Active
Antenna Type
TSO-C129 TSOA Antenna/Receiver
Combination
X
X
X X
X
X
X
X
X
X
X
X
X
X
See Note See Note See Note
Table 2. Acceptable Standard Antennas
5-6. Navigation Database. › 5-6.2 Database Process.
--- ---
Note: An active TSO-C144 antenna may be acceptable for TSO-C145/C146 revision ‘b’ or later Operational Class 2, 3, and 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(AR) to TSO-C145d 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.
a. For all combined sensor/navigator GNSS equipment, the navigation database is an essential component for the equipment to perform its intended function (see paragraphs 7-1.c and 19-8). Detailed guidance pertaining to the navigation database can be found in AC 20-153 (latest revision).
Continue reading ↓ 120 of 634 passages shown