AC 29-2C

Change 2Historical

Advisory circular · Certification of Transport Category Rotorcraft

A newer version is currentThis is a historical version. AC 29-2C CHG 9 is the version in force, approved June 23, 2023.
Approved
April 25, 2006
Last reviewed
December 4, 2008
Family
AC 29-2 · 13 versions
Revision
C, change 2
14 CFR parts
29

Guidance, not mandatory unless a rule or AD requires it. DRS record last changed November 22, 2025.

Show pages 1010–1021
Page 1022Open in PDF

AC 29-2C, Chg 2 4/25/06 HTAWS that are discussed throughout this document: equipment qualification, installation, credit validation, testing considerations, and Instructions for Continued Airworthiness (ICA).

c. Related Regulations and Documents

(1) Regulations. FAR/JAR:

§ 29.1301 Function and installation § 29.1303 Flight and navigation instruments § 29.1309 Equipment, systems, and installations § 29.1321 Arrangement and visibility § 29.1322 Warning, caution, and advisory lights § 29.1351 Electrical systems and equipment—General § 29.1357 Circuit protective devices § 29.1381 Instrument lights § 29.1459 Flight recorders § 29.1529 Instructions for Continued Airworthiness § 29.1541 Markings and placards—General § 29.1581 Flight manual—General § 29.1585 Operating procedures

(2) Advisory Circulars (AC), Orders, and Technical Standard Orders TSO/JTSO TSO-C92c, Ground Proximity Warning/Glide slope Deviation Alerting Equipment:

Technical Standards Authorization, Part 37.201 TSO C-151b, Terrain Awareness and Warning System

(3) Industry documents. The Radi o Technical Commission for Aeronautics (RTCA) documents listed below are available from RTCA, Inc., 1140 Connecticut Avenue N.W., Suite 1020, Washington, D.C. 20036-4001; DO-160D, Environmental Conditions and Test Procedures for Airborne Equipment.

DO-161A, Minimum Performance Standards - Airborne Ground Proximity Warning Equipment.

DO-200A, Standards for Processing Aeronautical Data.

Society of Automotive Engineers (SAE) Aerospace Recommended Practice (ARP) 4754, Certification Considerations for Highly Integrated or Complex Aircraft Systems.

d. Definitions

(1) Alerts: A visual or aural stimulus presented either to attract attention or to convey information regarding system status or condition, or both.

HTAWS Alerts:

Page MG 18 - 2

Page 1023Open in PDF

Aural Alert: A discrete sound, tone, or verbal statement used to annunciate a condition, situation, or event.

Visual Alert: The use of projected or displayed information to present a condition, situation, or event to the flight crew.

Caution Alert: An alert requiring flight crew awareness. Subsequent corrective action will normally be necessary.

Warning Alert: An alert for a detected terrain or obstacle threat that requires immediate flight crew attention and decision.

(2) Class (A) HTAWS Equipment: This class of equipment provides Ground Proximity Warning System (GPWS), Forward Looking Terrain Avoidance (FLTA), and a display capability, as defined in paragraphs e and j.

(3) Class (B) HTAWS Equipment: This class of equipment provides FLTA, as defined in paragraph e and j.

(4) Controlled Flight Into Terrain (CFIT): An accident or incident in which the aircraft, under the flight crew's control, is inadvertently flown into terrain, obstacles, or water.

(5) Failure: The inability of the equipment or any subpart of that equipment to perform its intended function within previously specified limits.

(6) False Alert: A warning or caution that occurs when the design terrain or obstacle warning or caution threshold of the system is not exceeded.

(7) Forward-Looking Terrain Avoidance (FLTA): An HTAWS functional requirement to provide look-ahead terrain and obstacle protection along and below the aircraft’s lateral and vertical flight path.

(8) Hazard: A state or set of conditions that, together with other conditions in the environment, could result in an adverse safety impact.

(9) Hazardously Misleading Information (HMI): An incorrect depiction of the terrain or obstacle threat relative to the aircraft during an alert condition (excluding source data).

(10) Integrity: Attribute or reliability of a system or a component that can be relied upon to function as required by the criticality determined by the Functional Hazard Assessment (FHA).

Page MG 18 - 3

Page 1024Open in PDF

AC 29-2C, Chg 2 4/25/06

(11) Low Altitude Mode: A reduced warning algorithm state that allows operation at less than en route altitudes with minimal alerts.

(12) Maneuver: An appropriate change in the flight path of the aircraft initiated by the flight crew in response to an HTAWS alert to include climbs, descents (inappropriate for most situations), and turning procedures.

(13) Nuisance Alert: An alert that occurs when there is no threat or is unnecessary for the intended operation.

(14) Obstacle: A human-made structure that is in the flight path of the aircraft.

( 15) Operational Credit: To give approv al for an HTAWS installation that adds to, replaces, or intervenes in the aircraft’s operating requirements or operational procedures based on the installation and operation of the HTAWS system.

(16) QFE : Corrected Barometric Altitude relative to field elevation.

(17) QNH: Corrected Barometric Altitude relative to sea level.

(18) Required Terrain Clearance (RTC): The minimum requirements for obstacle or terrain clearance as defined by United States Standard for Terminal Instrument Procedures (TERPS) FAA Order 8260.3B and the Aeronautical Information Manual (AIM).

(19) Helicopter Terrain Awareness and Warning System (HTAWS): A generic term used to describe an alerting system that provides the flight crew with sufficient information and time to detect potentially hazardous terrain or obstacle.

(20) Terrain Awareness Display (TAD): A display of the surrounding terrain and obstacle(s) relative to the aircraft.

(21) Terrain Database: Terrain and obstacle information stored within an HTAWS.

(22) Time-shared Display: A disp lay that shows terrain and obstacle information, plus additional information from other systems [e.g., an Electric Flight Instrument System/Navigation Display/Multi-Function Display (EFIS/ND/MFD)].

e. SYSTEM DESCRIPTION

HTAWS is intended to provide flight crews with aural and visual alert aids aimed at preventing a CFIT accident by providing increased terrain and obstacle awareness.

Like airplane TAWS, as described in TSO-151b, HTAWS equipment may be divided into two classes of complexity which, in general, may relate to aircraft size or complexity.

Page MG 18 - 4

Page 1025Open in PDF

(1) Class (A) HTAWS equipment.

(i) Class (A) HTAWS equipment provides two principal alerting functions.

These are:

(A) Forward-Looking Terrain-Avoi dance (FLTA) function, which includes:

• Reduced required terrain clearance.

• Imminent terrain or obstacle impact.

(B) Basic Ground Proximity Warning System (GPWS) functions, which includes:

• Excessive rates of descent. (Optional)

• Excessive closure rate to terrain.

• Excessive altitude loss after takeoff.

• Flight into terrain when not in landing configuration.

• Excessive downward deviation from ILS glidepath.

(ii) Although the installation of a HTAWS is not currently required by operational rules for helicopters, to be consistent with TSO151b requirements the Class (A) HTAWS should include a display that meets the requirements of paragraph j. The terrain and obstacle display and threat alerting are made possible by the HTAWS’ acceptance of a variety of input parameters. These parameters are used in conjunction with a terrain, obstacle and airport database(s) that reside within the HTAWS computer.

The Class (A) HTAWS places an aircraft position symbol on a terrain and obstacle map and applies terrain display algorithms. Terrain and obstacle mapping information may be provided on either a weather radar (WX) display, Electronic Flight Instrument System (EFIS) display, or other compatible display screens. The display of HTAWS information on an MFD that also serves other purposes should be displayed in a heading up or track up orientation, not in a North up orientation to avoid confusion. See paragraph l for prioritization of alerts.

(iii) Aircraft position information should be provided by a Global Positioning System (GPS or GPS-based equivalent) that meets the provisions specified in paragraph h (Position Source).

(iv) Class (A) HTAWS equipment may provide automatic autorotation detection when Excessive Descent Rate warning functions are included. A detected autorotation state should inhibit Excessive Rate Warnings and other warnings that may Page MG 18 - 5

Page 1026Open in PDF

AC 29-2C, Chg 2 4/25/06 distract a flight crew during an emergency procedure. Altitude advisories and gear (not extended) warning may be added during this autorotation state if desired. The altitude for the optional gear warning should be based on the specific helicopter autorotation rate of descent and gear extension time to insure gear down prior to the landing.

(v) Class (A) HTAWS equipment should provide a Low Altitude Mode to allow VFR operations at less than en route altitudes with minimal nuisance alerts.

(2) Class (B) HTAWS equipment.

(i) Class (B) HTAWS equipment provides two principal alerting functions.

These are:

• Imminent terrain or obstacle impact

• Excessive altitude loss after takeoff

(ii) Class (B) HTAWS does not require a display. If a display is installed with a Class (B) HTAWS, it should meet the provisions of paragraph j (Display Presentation).

(iii) Class (B) HTAWS equipment is required to interface with an approved GPS (or GPS-based equivalent) for horizontal position information that meets the provisions specified in paragraph h (Position Source).

(iv) Class (B) HTAWS does not require an interface to a radar altimeter.

(v) Class (B) HTAWS equipment should provide a Low Altitude Mode to allow VFR operations at less than en route altitudes with minimal alerts.

f. Airworthiness Considerations

(1) The scope of the applicant’s program should be directed toward airworthiness approval through the Type Certification (TC), Amended Type Certification (ATC), or Supplemental Type Certification (STC) processes. The significant differences between the airplane (TAWS) and helicopter (HTAWS) systems and the lack of specific TSO requirements for the helicopter system necessitate greater engineering and flight test involvement than normally provided during the field approval process. The applicant must identify if the changes made to the helicopter during installation of the HTAWS constitute a significant (engineering) change. However, the installation of the HTAWS alone should not require application of the Changed Product Rule, § 21.101.

(2) The remainder of this document de scribes in detail specific airworthiness considerations that applicants should consider as part of the certification process.

g. Certification Requirements:

Page MG 18 - 6

Page 1027Open in PDF

(1) General. For first time approvals, the manufacturer or applicant should provide detailed systems description and design features that can be verified by certification engineers and project pilots. Flight-testing should concentrate on the adequacy of the interface, basic functionality of the system, location and visibility of the display, adequacy of the visual and aural alerts, day and night lighting, ease of use, understanding of the terrain and obstacle display, and potential interference with other installed equipment. In general, each mode of operation of the system should be evaluated in flight.

(2) System Safety Assessment. The applicant should perform a Functional Hazard Assessment (FHA) and System Safety Assessment (SSA) to establish the HTAWS criticality and hazards associated with the proposed installation. The reliability level of the system must be commensurate with the assessed criticality, and compliance with this criticality level must be demonstrated during certification. These assessments should consider the probability of such failures as: unannunciated failures, false caution or warning alerts due to undetected (or latent) failures, failure of the system to provide the required alerting functions due to undetected (or latent) failures, effects of HTAWS failures on other aircraft systems, nuisance alerts, etc.

(3) Software Qualification. The so ftware for the HTAWS should be developed in accordance with RTCA DO-178B, Software Considerations in Airborne Systems and Equipment Certification, or an FAA/AUTHORITY-accepted equivalent. The most significant aspects of the enhanced features are the terrain and obstacle database stored in the HTAWS computer and the algorithms used by the HTAWS computer.

Coupled with this are the evasive maneuvers that will be employed to avoid terrain and obstacle. Regardless of the findings of the above System Safety Assessment, software for the HTAWS should be developed as a minimum to DO-178B level C. The software level will be commensurate with the failure condition category determined during the safety assessment process. This analysis should include unannunciated failure or malfunction (false warning) of the HTAWS aural or visual warnings.

(4) Environmental Qualification. Sinc e the TSO is not an installation approval, the HTAWS installation should be shown to be suitable to its airborne environment. A desirable way to qualify the system component is to obtain approval to the appropriate TSO; however, if the TSO environmental considerations do not adequately represent the actual installation environment, the differences must be considered and evaluated.

If the equipment is not TSO-approved, it should be shown through testing that it complies with the requirements of SAE Document AS-8034, for the display and latest revision of RTCA Document DO-160, and other appropriate standards at the time of qualification of the equipment. This will include testing in accordance with the appropriate categories of the latest revision of RTCA Document DO-160, JEDEC Publication No. 64D (Protection from Ionizing Radiation).

(5) System Performance Validation. The applicant should demonstrate that the performance of the HTAWS, with regards to the position of the aircraft relative to the Page MG 18 - 7

Page 1028Open in PDF

AC 29-2C, Chg 2 4/25/06 terrain or obstacle, is adequate to preclude creation of a hazardously misleading situation. The integrity of the navigation source has a significant effect on acceptable performance of the system. The applicant should demonstrate that the performance of the HTAWS navigation source is suitable for each phase of flight (en route, terminal, approach, and low altitude mode) for which approval is sought. The HTAWS navigation source may be the same as the primary navigation system for the aircraft.

(6) Database Considerations. Since 6 arc-second terrain data currently are not available for all regions of the world, it may be years before a complete database is developed. It may be impossible to perform 100 percent verification of the accuracy of the terrain database. There currently are no specific FAA/AUTHORITY certification standards for airborne terrain and obstacle databases; therefore, the completeness and integrity of those available databases may vary significantly. To ensure no erroneous data could result in misleading information, the HTAWS system operating software should be developed in accordance with RTCA DO-178B, or an FAA/AUTHORITY accepted equivalent. The applicant should present and verify the process by which the database is developed and the methodology used to validate the database. The applicant should demonstrate that the accuracy and resolution of the database is suitable for the intended operation. The DO-200A, Standard for Processing Aeronautical Data or equivalent must be used as a guideline.

(7) Alerts. Alerts should be clear, concise, and unambiguous. If there is a failure mode where the display may be inoperative but the HTAWS is operative or vice versa, some type of annunciation of the failure mode should be provided to the flight crew; e.g. “HTAWS display inop”, “HTAWS inop”, etc. This annunciation should be clear, unambiguous, and distinguishable from other failures. The alerting system should be consistent with the basic alerting philosophy of the GPWS.

(8) Displays. The current state of th e art of HTAWS may make use of existing aircraft display systems such as the weather radar, or Multiple Function Display (MFD);

therefore, implementation of the HTAWS presentation requires the integration with existing display systems. The use of the HTAWS display must not unacceptably detract from the usability of existing functions. Refer to paragraph j for Display Presentation Considerations.

h. Position Source. HTAWS uses the estimated position, based on GPS, of the aircraft with reference to the terrain or obstacle to determine when an alert should be annunciated. The applicant should provide evidence that the HTAWS position source (horizontal and vertical) is suitable for each phase of flight (i.e., en route, terminal, low alt mode, and approach, for which approval is sought).

(1) Horizontal and Vertical Position Source.

(i) HTAWS that interface with previously approved navigation systems:

Page MG 18 - 8

Page 1029Open in PDF

(A) Class (A) equipment may use approved Area Navigation (RNAV), which should include GPS which complies with (D) below.

(B) Class (B) equipment is required to interface with an approved GPS for horizontal and vertical position, which complies with (D) below.

(C) Previously approved RNA V and GPS systems that are used for navigation are considered suitable for HTAWS horizontal and vertical position inputs, if they comply with (D) below.

(D) GPS equipment must meet the requirements of TSO-C129a and provide 95% horizontal and vertical position accuracy figure of merit (FOM or DOP) estimates, in accordance with ARINC-743A.

( E ) If a Wide Area Augmentation System (WAAS) is used as a position source, it should meet TSO C-145a and comply with the FOM requirements of (D) above.

(F) HTAWS functions that require a navigation source for operations should be automatically disabled when the source has degraded to a point where its accuracy can no longer support the HTAWS functions. An aural and visual annunciation of this loss of function is required except for specific failures where a visual annunciation has been demonstrated to be acceptable.

(ii) HTAWS equipment with internal GPS position source: Class (A) and Class (B) equipment that uses a GPS internal to the HTAWS for horizontal and vertical position information, must use a GPS that complies with (i)(D) above.

(iii) The HTAWS should be capable of detecting a positional error that exceeds 0.25 NM, which is considered unsuitable for the HTAWS, and the functions that require GPS for operations should be automatically disabled and an aural and visual annunciation provided. An exception to this requirement will be made for specific failures where visual annunciations have been demonstrated to be acceptable. The applicant should be able to demonstrate that the HTAWS, as installed on the helicopter, provides the required position information accuracy (latitude/longitude and altitude) for the HTAWS functions.

(2) Vertical Position Aiding. The following sources are considered suitable for use in aiding vertical position. They may be used in combination, if the appropriate accuracy is demonstrated. The applicant should be able to demonstrate that the HTAWS, as installed on the aircraft, provides the appropriate vertical information for the HTAWS functions. Where operations are reliant on the use of QFE, an adequate means of determining the altitude should be provided. Geometric altitude should be enabled if the system has the capability.

Page MG 18 - 9

Page 1030Open in PDF

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

Page 1031Open in PDF

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

Page 1032Open in PDF

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

Page 1033Open in PDF

(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