AC 29-2C, Chg 2 4/25/06
(i) Barometric Altitude. Vertical position information provided by a barometric altitude source that meets the requirements of TSO-C10b, or later versions, is considered acceptable as a source of vertical position information.
(ii) Radar Altimeter. Vertical position information provided by a radar altimeter that meets the accuracy specified in TSO-C67 or later version, is considered acceptable as a source of vertical position information. Class (B) equipment does not require a radar altitude input.
(iii) Air Data Computers. Vertical position information provided by an air data computer is considered acceptable as a source of vertical position information if it meets the accuracy requirements of TSO-C106, or later versions.
(iv) GPS. Vertical position information provided by GPS may be used in combination with other sources of vertical position. If GPS is used as the only means for the determination of vertical position, then it must meet the requirements of TSO- C145, C129a, C115b, C146a, or later versions and paragraph (1)(i)(D) above.
( v ) IRS. Vertical position information provided by an Inertial Reference System (IRS) may be used in combination with other sources of vertical position. If an IRS is used as the only means for the determination of vertical position, then it must meet the requirements of TSO-C115b, or later versions and (1)(i)(D) above.
i. Terrain Database. The terrain database for HTAWS should be validated via the TSO-C151b authorization process, or similar process. If the TSO or equivalent process is not used to validate the database, the installer should demonstrate that the integrity is acceptable for the installation. There are three additional areas of concern that should be addressed during the installation process:
(1) Updates. The installed system should be capable of accepting updated terrain database and obstacle database (if applicable). The HTAWS manufacturers must have a procedure in place whereby the manufacturer can inform the aircraft owner or operator about database updates. The procedure should contain sufficient information to enable the owner or operator to make a logical safety decision as to whether it is appropriate to purchase and install the update. A means should be provided for identifying the local terrain and obstacle resolution for inclusion in the Pilot’s Guide and Flight Manual (or Supplement).
(2) Valid Regional Data. The Pilot’s Guide and Flight Manual (or Supplement) should identify the procedures for determining the status of the terrain and obstacle database. Operators should use this information to determine if updates include significant changes to the terrain and obstacle databases for the area of intended operation.
j. Display Presentation. For Class (A) HTAWS installed without an operational requirement, the terrain and obstacle display is optional; however, the flight crew’s Page MG 18 - 10
ability to identify potential vertical and horizontal flight path conflicts and correct these conflicts before an alert occurs is greatly enhanced by displaying this information.
Additionally, a visual display of the hazard will help support the appropriate recovery when an alert occurs. Therefore, it is recommended with any HTAWS installation that a means of displaying Terrain information be included when ever practical.
(1) Terrain and Obstacle Display.
(i) When a display is installed, the HTAWS equipment must be capable of providing terrain and obstacle alerting data to a cockpit display. The display hardware may be stand alone or interfaced with existing equipment, such as a weather radar (WXR), navigation displays, or other compatible display systems. The actual display presentation format will depend on the onboard display hardware, the options made available by the HTAWS manufacturer, and the features desired by the customer or user. Regardless of what format is used, the display presentation should enhance the flight crew's awareness of terrain and obstacle hazards.
(ii) The terrain and obstacle disp lay system is an output from the HTAWS; therefore, the possibility of misleading information on the display due to undetected or latent failures should be commensurate with the failure condition category.
(iii) During the development of the HTAWS display, the applicant should use a representative sample of pilots to participate in the design and evaluation process for the proposed presentation format if a novel presentation is considered.
(iv) The applicant may consider selecting a display where multiple functions are presented. In these cases, a means to select or de-select the display of terrain and obstacle information should be provided. However, care should be exercised in selecting such a multifunction implementation, to ensure that the display sharing is appropriate for the specific functions. The use of the HTAWS display should not unacceptably detract from the usability of existing functions. Since the HTAWS display is not to be used for navigation, the use of the display should not impair the ability of the pilot to perform required navigation functions. An example of such an impairment would be an installation that forces the pilot to choose between the HTAWS display and the needed navigation information in situations where both could be effectively used simultaneously and continuously (e.g., instrument approach in the vicinity of hazardous terrain and obstacles). If the timesharing of the display between HTAWS and other functions is deemed acceptable, the design should facilitate simple switching between the functions, with minimal time delays, so both functions are sufficiently accessible in realistic flight scenarios.
(v) The terrain and obstacle display should be installed in a location that provides monitoring by the pilot(s) for identification of potential flight path conflicts. In general, the terrain and obstacle display should be in a location similar to other multifunction displays, such as electronic maps and weather radar.
Page MG 18 - 11
AC 29-2C, Chg 2 4/25/06
(2) Terrain and Obstacle Display Presentation. HTAWS equipment should be designed to interface with a color terrain and obstacle display. If there are multiple terrain and obstacle views available, at least one terrain and obstacle display should be capable of providing all of the following terrain-related information:
(i) The terrain and obstacle should be depicted relative to the aircraft’s position so that the pilot may estimate the relative bearing to the terrain and obstacle of interest.
(ii) The terrain and obstacle depi cted should be oriented to either the heading or track of the aircraft. Since track information may be confusing during hover and low speed flight (other than forward), heading is the appropriate orientation for these flight regimes. Additionally, a north-up orientation may be included as a selectable format but should be limited to pre-flight planning.
(iii) Variations in terrain and obsta cle elevation depicted relative to the aircraft’s elevation (above and below) should be visually distinct. Terrain or an obstacle that is more than 1,500 feet below the aircraft’s elevation need not be depicted.
(iv) Terrain or obstacles that generate alerts should be displayed in a manner to distinguish it from non-hazardous terrain or obstacles, and be consistent with the caution and warning alert level.
(v) The terrain and obstacle display presentation should be clear, unambiguous, and readily usable by the flight crew during day and night operations, under all ambient lighting conditions expected in service.
(vi) The terrain and obstacle display should be viewable in direct sunlight.
(vii) An inhibited, failed, or i noperative HTAWS should be indicated to the flight crew in a manner consistent with the flight deck design philosophy.
(viii) The terrain and obstacle display presentation should complement and be compatible with the terrain alerting function of the HTAWS.
(ix) Terrain and obstacle mapping should allow the flight crew to determine relative terrain elevation.
(x) The terrain and obstacle display should be designed so the flight crew can readily determine if the terrain or an obstacle is a threat to the aircraft.
(xi) The colors and textures used fo r threat terrain and obstacle should be consistent with other FAA and RTCA guidance (such as DO-257) as well as intuitive and indicative of the immediacy of the threat.
Page MG 18 - 12
(xii) If the terrain or obstacle data is presented on a shared display, the terrain and obstacle mode and terrain and obstacle information should be easily distinguishable from weather and other features.
(xiii) For color displays, the sele cted colors should complement the discrete visual and aural alerts that are presented to the flight crew. Accordingly, any colors that are used for the threat terrain and obstacle display should match the colors used for discrete visual alerts.
(xiv) If additional terrain and obstacl e views are provided, they should not present information that is inconsistent or incompatible with the features described above. Each view should be consistent with the other as far as color, scale, and textural information. When transitioning between views, the range scale should remain the same for each view. Each view will be carefully evaluated to ensure that it does not interfere with or reduce the effectiveness of the HTAWS. Since such displays may include functions that go beyond the scope of this guidance, they should be evaluated as appropriate.
(3) Pop-Up Mode-Switching Functionality.
(i) An automatic pop-up feature s hould be incorporated. If the display does not provide a pop-up feature, a flight manual limitation should require the Terrain and Obstacle Display be selected when engaged in Low Altitude Mode operations.
( i i ) General Considerations. If implemented, an automatic pop-up feature should incorporate the following considerations in its design:
(A) The pop-up functionality should automatically display HTAWS-related information when an HTAWS caution alert occurs.
(B) The terrain and obstacle display mode should be annunciated on the display. If this is not feasible, a mode annunciation light should be installed near the terrain and obstacle display.
(C) The pop-up functionality should be implemented consistently for weather, predictive wind shear, and traffic alerts, including any overlay design philosophies. The pop-up must not impair the pilot’s use of essential flight or navigational information.
(D) The display should be designed so that it is very evident that an automatic pop-up has occurred.
(E) Manually switching back to t he original mode of operation should require minimal effort.
Page MG 18 - 13
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