AC 29-2C, Chg 2 4/25/06 (F) Automatic switching back to the original mode of operation after the caution or warning ceases should not be allowed unless it is part of the aircraft design philosophy.
(iii) Pop-Up Inhibit Feature. For dual displays, pop-up functionality may be inhibited if the terrain and obstacle map is on at least one display when a terrain alert occurs. However, if the terrain and obstacle map is not on a display when a terrain alert occurs, the terrain and obstacle map, with the alerts, should be automatically displayed on at least one display.
(4) Auto-Range Switching Mode.
(i) An auto-ranging function during alerts should be provided. If provided, an auto-ranging display should be designed so that range is evident to the flight crew. The range selected for auto-ranging should provide a usable depiction of the threat on the display. Switching back to manually selected range should require minimal effort. If auto range is not provided, RFM or RFMS limitation should require the selection of a range of 3 miles or less when low altitude mode is selected.
(ii) For displays that do not support a range of 3 miles or less, an evaluation of adequacy for operation in Low Altitude Mode should be performed.
k. Alerts.
(1) In addition to meeting the color requirements of § 29.1322, as applicable, the HTAWS alerts should be clear, concise, and unambiguous.
(2) The certification plan should inclu de tests and analyses to assure that the visual and aural alerts are consistent with the alerting philosophy of the aircraft flight deck in which the HTAWS equipment is installed. This is particularly important with retrofit installations, which may use previously-installed alerting annunciations. The plan should consider that the visual alerts are:
• Located in the pilots field of view,
• Consistent with their associated voice, or aural call out, and
• Consistent with the colors specified in § 29.1322 and TSO C-113, both in the discrete and textual display formats.
l. Alert Prioritization.
(1) Installations of HTAWS on aircraft also equipped with Traffic Collision Avoidance System (TCAS) should include an alert prioritization scheme such that:
(i) Only one alert is given at any one time, and Page MG 18 - 14
(ii) Alerts for situations requiring immediate action by the flight crew have priority in situations where conditions for multiple alerts may occur.
NOTE: In older aircraft, the system architecture may preclude the prioritization of alerts for multiple alerting systems. If that is the case, a prioritization scheme is not required.
However, if simultaneous alerts can be given, then the aural words should be understandable and the associated visual alerts should not be confusing to the flight crew.
(2) Implementing this prioritizati on scheme within the HTAWS equipment is acceptable. Figure AC 29.MG 18-1, below, displays an example of the recommended alert prioritization.
(3) Installation of HTAWS on helicopters with central or integrated Master Aural Warning system should show compatibility to a master aural warning scheme that is consistent with the overall cockpit design.
Page MG 18 - 15
AC 29-2C, Chg 2 4/25/06
Recommended Alert Prioritization between the HTAWS and TCAS TA
Priority Description Highest Class (A) Pull-Up Warning (Excessive Rates of Descent) Class (A) Terrain Terrain (Excessive Closure Rates) Class (A) Terrain Closure Pull-Up Warning (Excessive Closure Rates) Class (A)/(B) Terrain Awareness Warning (FLTA) Class (A) Warning Obstacle (Look ahead obstacle warning) Class (A) Minimums (Voice Callouts) Class (A)/B Terrain Awareness Caution (FLTA) Class (A)/(B) Caution Obstacle (look ahead obstacle caution) Class (A) Too Low Terrain (Flight Into Terrain When Not in Landing Configuration) Class (A) Altitude Callouts (Voice callouts) Class (A) Too Low Gear (Flight Into Terrain When Not in Landing Configuration) Class (A) Sink Rate (Excessive Rates of Descent) Class (A)/(B) Don’t Sink (Excessive Altitude Loss After Take-off) Class (A) Glide slope (Excessive Downward Deviation From an ILS Glide slope) Class (A)/B TCAS TA (“Traffic Traffic”) (*) Class (A) Bank Angle (Voice Callouts) Class (A) Tail Strike (Voice Callouts) Class (A)/(B) Terrain INOP Status (Be Alert Terrain INOP) Lowest TCAS TA (“Traffic Traffic”) (*) (*) TCAS TA Priority can be either priority 15 or 19.
(Note: The alert described above only accounts for HTAWS/TCAS aural priorities.
Other aircraft system aural alerts may be present and the resulting prioritization would then need to be established on an installation basis.)
FIGURE AC 29.MG 18-1 Page MG 18 - 16
m. System Inhibit.
(1) A means for the flight crew to i nhibit the following HTAWS functions should be provided:
FLTA and Basic GPWS audio for a period of time not to exceed 5 minutes or FLTA cautions and warnings. (momentary switch with 5-minute reset) --OR-- FLTA Cautions and Warnings
Basic GPWS – Excessive downward deviation from the ILS glide slope
Basic GPWS for extreme low-level operation and FLTA. Note: This option should have specific coverage in the RFM/RFMS for its use and operational constraints.
(2) Appropriate annunciation of the inhibi ted functions should be provided to the flight crew. Flight crew procedures for disabling various HTAWS functions should be identified in the Flight Manual (or Supplement). For Class (A) equipment, inhibiting the FLTA functionality, if provided, should not affect the Basic GPWS functions.
n. Flight Data Recorder. For those applications that require crash-survivable flight data recording in accordance with the requirements of § 29.1459(e) (flight recorders), consideration should be given to provide a means to record the FLTA alerts. (It is not necessary to distinguish between Basic GPWS and the new FLTA alerts.) If this provision is implemented, a means also should be provided to record an FLTA inhibit.
o. Ground Test Considerations.
(1) A ground test should be conducted fo r each HTAWS installation. The level of testing required will be determined by the scope of the installation (First of a Model vs. Follow-on). Some items to consider for ground test should include:
Location of HTAWS controls, displays, and annunciators;
Evaluation of identified failure modes;
Evaluation of all HTAWS interfaces; and,
Electromagnetic interference (EMI)/electromagnetic compatibility (EMC) testing, and VHF harmonic tests for HTAWS with internal GPS receivers.
(2) Considerations should be made (to the maximum extent possible) for evaluating display characteristics and interface if it can be shown that all of the performance aspects of the display that are available during flight can be evaluated on the ground.
Page MG 18 - 17
AC 29-2C, Chg 2 4/25/06
p. Flight Test Considerations.
(1) The level of flight test required to validate a particular HTAWS installation will be based on the aircraft system architecture, and credit given for previously certified installations, simulations, and ground tests. The requirement for a flight test needs to be evaluated for each installation. First time installations and new sensor inputs will require flight tests. STC follow-on installations that introduce changes in flight deck configurations may require flight tests if they cannot be evaluated as specified in paragraph o of this document. The evaluation of new sensor models or aircraft models may require flight tests, unless it can be shown through a sensitivity analysis that the new sensor’s dynamic characteristics and the model aircraft during flight are compatible with the current sensor parameters, and will not effect the performance of the HTAWS.
The following examples are intended to assist in determining the flight test guidelines for some potential or likely HTAWS configurations. Figure AC 29.MG 18-2, (which follows the five examples), provides a summary of these examples.
(i) Example 1. This is the first time the vendor’s equipment has been installed in any aircraft for the purpose of receiving a first time FAA/AUTHORITY approval. A complete and thorough Ground and Flight Test program should be conducted to verify the adequacy of the installation. If the HTAWS has been approved on another helicopter model, the scope of the testing should be reduced to assure functionality of each mode, and proper interface with other aircraft systems and displays.
(ii) Example 2. This involves a follow-on installation of a previously approved HTAWS in which a required sensor input has not been previously approved for the specific vendor’s equipment. For example, if the sensor that provides barometric altitude rate (or equivalent) to the HTAWS equipment has not been previously approved, the flight test evaluation should focus on the HTAWS functions affected by barometric altitude rate such as excessive rates of descent.
(iii) Example 3. This involves a follow-on installation of a previously approved HTAWS in which the Terrain and Obstacle Display has not been previously approved. In this case, the focus of the flight test evaluation should be on display related issues and tests specified in paragraph t(4) (Terrain and Obstacle Display Flight Test Considerations) of this AC.
(iv) Example 4. This involves a follow-on installation of a previously approved HTAWS in which the horizontal and vertical position source sensor input has not been previously approved for the specific vendor’s equipment. The focus of the flight test evaluation should be on the adequacy of the horizontal position source and the terrain and obstacle display as determined by that horizontal position source. In addition, since the navigation system provides track and ground speed information to HTAWS, which affect the alerting logic, an FLTA functional flight test evaluation test is warranted. Some basic GPWS installations use the horizontal position information to Page MG 18 - 18
desensitize some of the basic GPWS modes. Verification of the function and proper interface installation may require additional flight-testing for the basic GPWS.
( v ) Example 5. This involves a follow-on installation of a previously approved HTAWS in which the radar altimeter to the HTAWS equipment has not been previously approved. In this case, the focus of the flight test evaluation should be on the HTAWS functions affected by radar altitude such as one of the Basic GPWS. Only one mode test is required to assure that the radar altimeter input is properly installed to the HTAWS. This example does not apply to Class (B) HTAWS.
( v i ) Example 6. This involves an initial installation of a vendor’s HTAWS in a model aircraft that was previously approved with Basic GPWS equipment from the same vendor. Same basic GPWS algorithms, and the same sensors that are used for the GPWS installation are used for the HTAWS installation. Generally, the Basic GPWS testing is not required to be accomplished for the HTAWS installation. However, there are exceptions such as the following:
Exception: A basic GPWS is installed in an aircraft; subsequently, the HTAWS is to be installed. The sensors used for the basic GPWS and those used for the HTAWS are the same, except that some of the algorithms were changed and some features were added. Ultimately, an evaluation should be made to check the differences between the basic GPWS algorithms that were certified and the basic GPWS algorithms used for the HTAWS to determine if any flight-testing is necessary.
Flight Test Matrix WS
HTAWS TEST Examples FLTA Basic GPWS* Terrain Display Horizontal & Vertical Position Source Example 1 X X X X Example 2 X Example 3 X Example 4 X If desensitized X X Example 5 X Example 6 X X X * Class (A) equipment only
FIGURE AC 29.MG 18-2 Page MG 18 - 19
AC 29-2C, Chg 2 4/25/06
(2) FLTA Flight Test Considerations.
(i) Flight-testing to verify the proper operation of the FLTA function can be conducted in an area where the terrain or obstacle elevation for the test runs is known to be within approximately 25 feet.
(ii) Test runs are recommended to be level flight at approximately the peak elevation of the Terrain or Obstacle. After caution and warning messages, the flight path should be adjusted to pass 50 to 100 feet above the terrain or obstacle of interest. The test runs should verify that:
(A) All alerts (caution and warni ngs) are given at an appropriate point in the run.
(B) All pop-up, auto-range, or other display features are working correctly.
(C) The display depicts the terrain or obstacle accurately.
(D) Low Altitude (if installed) al erts (cautions and warnings) are given at an appropriate point in the test run.
(E) Inhibit functions operate properly.
(3) Basic GPWS Flight Test Considerations. Flight-testing to verify the proper operation of Basic GPWS functions can be conducted in any area where the terrain elevation is known to the flight crew. The following information is intended to provide guidance for conducting flight tests to exercise and verify the proper operation of each GPWS function. The need to conduct flight-testing for follow-on HTAWS installations will depend upon the nature of the new or modified sensors and their impact on that particular GPWS function.
(i) Excessive Rates of Descent (Optional). This test should be conducted over level terrain or water. For Class (A) equipment, this test verifies the proper installation of barometric altitude (and the corresponding computation of barometric altitude rate) and radar altitude. Only one test run is required to determine proper installation.
(ii) Excessive Closure Rate to Terrain. This test should be conducted in an area of known rising terrain. It is recommended that one level test run at an altitude 200 feet above the terrain peak elevation be conducted. For Class (A) equipment only, this test will verify the proper installation of the radar altimeter.
(iii) Excessive Altitude Loss after Takeoff. This test is conducted after a normal takeoff profile has been established but before reaching pattern altitude. For Page MG 18 - 20
Class (A) equipment, this test verifies the proper installation of barometric altitude, barometric altitude rate, and radar altitude.
(iv) Flight into Terrain when Not in Landing Configuration. This test should be conducted while on a visual approach to a runway or over level terrain or water. For Class (A) equipment only, this test verifies the proper installation airspeed and radar altitude as well as the gear sensor inputs to HTAWS.
( v ) Excessive Downward Deviation from an ILS Glide slope. This test should be conducted during an ILS approach. For Class (A) equipment only, this test will verify the proper installation of the ILS Glide slope input to HTAWS. For aircraft equipped with dual ILS system, both systems should be demonstrated.
(4) Terrain and Obstacle Displ ay Flight Test Considerations.
(i) Flight-testing to verify the proper operation of the Terrain and Obstacle Display should be conducted while verifying all the other required HTAWS functions.
(ii) Emphasis should be placed on verifying compliance with the provisions specified in paragraph j(1) (Terrain and Obstacle Display) of this document, during normal aircraft maneuvering during all phases of flight. Pop-up and auto-ranging features should be evaluated, if applicable.
(iii) The applicant should perform sustained standard rate turns to evaluate:
• Symbol stability
• Flicker
• Jitter
• Display update rate
• Color cohesiveness
• Readability
• The use of color to depict relative elevation data
• Caution and warning alert area depictions
• Map masking
• Overall suitability of the display Page MG 18 - 21
AC 29-2C, Chg 2 4/25/06
(5) Added Features Flight Test Considerations . Flight-testing should be used to verify the proper operation of additional implemented features (i.e. functions not defined by TSO C151b) such as:
Autorotation detection,
Tail Strike,
Bank angle,
Altitude call outs “Approaching Minimums,” or
Other features not listed here.
(6) Corrected Pressure Altitude Variations in Cold Weather. The HTAWS may be designed to account for the effects of cold weather on barometric altitude, while determining vertical position. Flight-testing may be required, unless a suitable verification procedure can be conducted. This will depend on the design of the cold weather compensation. This test is not required for systems that do not use corrected pressure altitude for cold weather compensation.
q. Rotorcraft Flight Manual (RFM) or Rotorcraft Flight Manual Supplement (RFMS).
The applicant should make an evaluation to determine if there are any limitations of the system and, if so, how they will affect aircraft operations. Any limitations affecting operations should be included in the RFM or RFMS. As a minimum, the applicant should provide instructions in the Limitations Section of the RFM or RFMS that include the following as appropriate (i.e., for systems approved on a no operational credit basis):
(1) Limitations. The following instructi ons should be included in the Limitations section of all RFMs or RFMSs:
(i) Navigation must not be predicated upon the use of the HTAWS information.
NOTE: The Terrain and Obstacle Display is intended to serve as a terrain and obstacle awareness tool only. The Display and database may not provide the accuracy or fidelity on which to base routine navigation decisions and plan routes to avoid terrain or obstacles.
(ii) The status of t he inclusion of Power Lines in the Obstacle Database must be stated.
Page MG 18 - 22
(iii) Low Altitude Mode must not be selected when operating under IMC conditions except as required when performing offshore platform IMC Approach Procedures or other Special Procedures.
(iv) The operator must select a range below 3 miles or an alternate range that has been demonstrated by the applicant to be appropriate when low altitude mode is activated on displays that do not auto-range.
(2) Operational Considerations for Normal and Abnormal Procedures. In addition to the GPWS operational procedures, consider the following:
(i) Terrain or Obstacle Awareness Caution. When a terrain or obstacle awareness CAUTION occurs, verify the aircraft flight path and correct it, if required.
(ii) Terrain or Obstacle Awareness Warning. When a terrain or obstacle awareness WARNING occurs, immediately initiate a maneuver that will provide maximum terrain or obstacle clearance, until all alerts cease.
(iii) Audio Inhibit. For those insta llations that include the ability to inhibit all or some of the HTAWS audio alerts, the Flight Manual (or Supplement) should state:
•When the audio inhibit function should be used.
•What alerts are inhibited.
•How long the alerts are inhibited.
•How to re-establish the alerts.
For Example: “For operations in day VFR conditions where terrain clearance may be assured visually and HTAWS audio alerts will hamper aircrew performance, the AUDIO INHIBIT button may be pushed to inhibit all HTAWS audio alerts. The audio alerts will resume five minutes after inhibit is selected or when the AUDIO INHIBIT button is pressed again.”
(iv) Altitude Reference. The Flight Manual (or Supplement) should explain how different altitude sources are blended to create the altitude used by the HTAWS. If the blended altitude is displayed to the pilot, a caution should state that ATC assigned or posted altitudes will be flown according to standard barometric altimeters with a correct altimeter setting. Blended altitudes may not provide adequate traffic separation. If the use of QFE altimeter settings adversely affects the performance of the HTAWS, procedures for QFE operations should be presented in the Flight Manual (or Supplement).
( v ) Environmental Requirements. For operations in cold weather, either the system should be able to account for variations in cold weather at temperatures at Page MG 18 - 23
AC 29-2C, Chg 2 4/25/06 or below zero degrees Celsuis, or additional flight crew procedures should be considered to address pressure altitude limits for vertical position determination.
Limitations may be needed to address insufficient determination of the aircraft’s vertical position in cold weather temperatures.
r. Instructions for Continued Airworthiness. Instructions for Continued Airworthiness are required by § 29.1529 as appropriate and in accordance with FAR/JAR 29 Appendix A. In addition to Appendix A requirements, the applicant should indicate when and how the terrain and obstacle databases need to be updated.
s. Additional Considerations to TSO C-151b Requirements for Helicopter Installation. Suggested consideration to TSO C-151b is provided below for helicopters installations. Items that are commentary only are italicized.
Class A
Additional Considerations to DO-161 Requirements
Mode 1
An Excessive Descent Rate warning function is not required but may be included optionally.
Mode 2
A Helicopter Class A TAWS should provide an Excessive Closure Rate to Terrain warning within a minimum of 8 seconds of impact with terrain. The system should provide a reduced nuisance free warning when in a landing flight profile. Provision should be made to prevent nuisance warnings during day VFR Low Altitude flying.
Mode 3
A Helicopter Class A TAWS should provide a warning of Excessive Altitude Loss during Takeoff. A warning should be generated if the aircraft losses more than 40% of its terrain clearance during takeoff. Takeoff is defined as at least the first 60 seconds of flights when greater than 50 knots and above 100 feet AGL.
Mode 4
A Helicopter Class A TAWS should provide a warning of Insufficient Terrain Clearance when not in a landing configuration (Gear Up) by 150 feet AGL for retractable gear aircraft. For fixed gear aircraft, a warning of Insufficient Terrain Clearance when not at landing speeds should be provided by 100 feet AGL. During an autorotation, improper landing gear configuration warnings should be provided in sufficient time to extend the gear before landing, based on specific helicopter autorotation performance, i.e. rate of descent and time to extend gear.
Page MG 18 - 24
Mode 5 No change is necessary for Mode 5.
Additional or Modified Requirements to TSO C-151b for Helicopter Installation Required Obstacle Clearance (ROC) and Required Terrain Clearance (RTC) By Phase of Flight
Alternate Figure AC 29.MG 18-2.1 is shown below.
TAWS REQUIRED TERRAIN CLEARANCE (RTC) BY PHASE OF FLIGHT Phase of Flight TERPS (ROC) TAWS (RTC) Level Flight
TAWS (RTC) Descending En route 1000 Feet 150 Feet 100 Feet Terminal (Intermediate Segment) 500 Feet 150 Feet 100 Feet Approach 250 Feet 150 Feet 100 Feet Departure (See Note 1) 48 Feet/NM 100 Feet 100 Feet
Note 1: During the Departure Phase of Flight, the FLTA function of Class A and B equipment should alert if the aircraft is projected to be within 100 feet vertically of terrain. However Class A and Class B equipment should not alert if the aircraft is projected to be more than 150 feet above the terrain.
Alternate FIGURE AC 29. MG 18-2.1 Page MG 18 - 25