Radar Vectors
Advisory Circular Cancelled Issued Jul 17, 2006 ANM-110 135 pages Copy saved Nov 18, 2026

AC 25.1329-1B Approval of Flight Guidance Systems

Describes acceptable means for showing compliance with certain requirements of Title 14, CFR, of FAR 25.1329, Flight Guidance System. While Part 25 contains the airworthiness standards applicable to transport category airplanes, the guidance in this AC pertains to the functions of autopilots, as well as any interactions with stability augmentation and trim functions.

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

Official source ↗ Open PDF

US Department of Transportation Logo

Subject: Approval Of Flight Guidance Systems

Date: 10/16/12 Initiated by: ANM-110

AC No: 25.1329-1B Change 1 1. Purpose. This change updates Advisory Circular (AC) 25.1329, “Approval of Flight Guidance Systems,” dated July 16, 2006 to AC 25.1329-1B, Change 1 dated 10/16/12. a. This change removes Appendix 2, “Flight Test Procedures,” because this material has been incorporated in AC 25-7C, “Flight Test Guide for Certification of Transport Category Airplanes.” 2. Applicability. a. The guidance provided in this document is directed to airplane manufacturers, modifiers, and operators of certain transport category airplanes. b. The guidance in this AC is neither mandatory nor regulatory in nature and does not constitute a requirement. You may follow alternate FAA-approved design recommendations. c. While these guidelines are not mandatory, they are derived from extensive FAA and industry experience in determining compliance with the relevant regulations. On the other hand, if we become aware of circumstances that convince us that following this AC would not result in compliance with the applicable regulations, we will not be bound by the terms of this AC, and we may require additional substantiation or design changes as a basis for finding compliance. d. This material does not change, create any additional, authorize changes in, or permit deviations from, regulatory requirements. 2. Principle changes. a. This change removes Appendix 2 from this AC, renumbers the remaining appendices, and changes all references to AC 25-7 from AC 25-7A to AC 25-7C, dated 10/16/12.

10/16/12 AC 25.1329-1B Change 1

b. The change number is shown at the top of each page with the date of the change.

Page control chart

Remove Pages Dated Insert Pages Dated

Cover 7/17/2006 Cover, ii 10/16/2012

ii-v 7/17/2006 ii-v 10/16/2012

11-12 7/17/2006 11-12 10/16/2012

16 7/17/2006 16 10/16/2012

21 7/17/2006 21 10/16/2012

24-25 7/17/2006 24-25 10/16/2012

37 7/17/2006 37 10/16/2012

44 7/17/2006 44 10/16/2012

49 7/17/2006 49 10/16/2012

57 7/17/2006 57 10/16/2012

70 7/17/2006 70 10/16/2012

86-88 7/17/2006 86-88 10/16/2012

92 7/17/2006 92 10/16/2012

98 7/17/2006 98 10/16/2012

100 - 103 7/17/2006 100 - 103 10/16/2012

106 - 107 7/17/2006 106 - 107 10/16/2012

111 7/17/2006 111 10/16/2012

Appendices 2-4 7/17/2006 Appendices 2 - 3 10/16/2012 John Piccola John Piccola Acting Manager, Transport Airplane Directorate Aircraft Certification Service

ii

Federal Aviation Administration

Subject: Approval Of Flight Guidance Systems

Date: 10/16/2012 Initiated by: ANM-110

AC No: 25.1329-1B Change 1 1. Purpose. This advisory circular (AC) describes an acceptable means for showing compliance with certain requirements of Title 14, Code of Federal Regulations (14 CFR) 25.1329, Flight guidance systems. While Part 25 contains the airworthiness standards applicable to transport category airplanes, the guidance in this AC pertains to the functions of autopilots, flight directors (FD), and automatic thrust control as well as any interactions with stability augmentation and trim functions. 2. Cancellation. Advisory Circular 25.1329-1B, dated July 17, 2006, is canceled. 3. Applicability. a. The guidance provided in this document is directed to airplane manufacturers, modifiers, and operators of certain transport category airplanes. b. The guidance in this AC is neither mandatory nor regulatory in nature and does not constitute a requirement. You may follow alternate FAA-approved design recommendations. c. While these guidelines are not mandatory, they are derived from extensive FAA and industry experience in determining compliance with the relevant regulations. On the other hand, if we become aware of circumstances that convince us that following this AC would not result in compliance with the applicable regulations, we will not be bound by the terms of this AC, and we may require additional substantiation or design changes as a basis for finding compliance. d. This material does not change, create any additional, authorize changes in, or permit deviations from, regulatory requirements.

i

Change 1 4. Related regulations, ACs, and industry documents. a. Regulations. The following related documents are provided for information purposes and are not necessarily directly referenced in this AC. The full text of 14 CFR can be downloaded from the Internet at http://ecfr.gpoaccess.gov/cgi/t/text/textidx?c=ecfr&tpl=%2Findex.tpl. A paper copy may be ordered from the Government Printing Office (GPO), Superintendent of Documents, Attn: New Orders, PO Box 371954, Pittsburgh, PA 15250-7954.

Section Title

§ 25.143 Controllability and Maneuverability, General

§ 25.301 Loads

§ 25.671 Control systems, General

§ 25.672 Stability augmentation and automatic and power-operated systems

§ 25.677 Trim systems

§ 25.777 Cockpit controls

§ 25.779 Motion and effect of cockpit controls

§ 25.781 Cockpit control knob shape

§ 25.901 Installation

§ 25.903 Engines

§ 25.1301 Function and installation

§ 25.1303 Flight and navigations instruments

§ 25.1309 Equipment, systems, and installations

§ 25.1322 Warning, caution, and advisory lights

§ 25.1581 Airplane Flight Manual, General

§ 25.1583 Airplane Flight Manual, Operating limitations

§ 25.1585 Airplane Flight Manual, Operating procedures

ii

Change 1 b. ACs. An electronic copy of the following ACs can be downloaded from the internet at http://www.faa.gov/regulations_policies/advisory_circulars/ or our Regulatory and Guidance Library (RGL) at http://rgl.faa.gov/ .

Number Title

AC 20-115B RTCA, Inc., Document RTCA/DO 178B [Radio Technical Commission for Aeronautics]

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

AC 20-152 Design Assurance Guidance for Airborne Electronic Hardware RTCA/DO 254

AC 25-7C Flight Test Guide for Certification of Transport Category Airplanes

AC 25-11A Transport Category Airplane Electronic Display Systems

AC 25-12 Airworthiness Criteria for the Approval of Airborne Windshear Warning Systems in Transport Category Airplanes

AC 25.672-1 Active Flight Controls

AC 25.1309-1A System Design and Analysis

AC 25.1419-1A Certification of Transport Category Airplanes for Flight in Icing Conditions

AC 25.1581-1 Change 1

Airplane Flight Manual

AC 120-28D Criteria for Approval of Category III Weather Minima for Takeoff, Landing, and Rollout

AC 120-29A Criteria for Approving Category 1 and Category II Landing Minima for FAR 121 Operators

AC 120-41 Criteria for Operational Approval of Airborne Windshear Alerting and Flight Guidance Systems

Note: This table represents the latest version of each AC at the time of publication. These individual ACs may be updated in the future, such that this table may reference a specific version of an AC that has been superseded. The latest version of each AC should always be used, even though this document may reference a previous version of an AC.

iii

10/16/12 AC 25.1329-1B Change 1

c. Related Industry Standards. The following documents are available from the Society of Automotive Engineers (SAE). These documents can be obtained from the Society of Automotive Engineers, Inc., 400 Commonwealth Drive, Warrendale, Pennsylvania, 15096 electronically from the SAE International website, http://www.sae.org/.

Number Title

SAE ARP5366 Autopilot, Flight Director and Autothrust Systems

SAE ARP4754 Certification Considerations for Highly Integrated or Complex Aircraft Systems SAE ARP4761 Guidelines and Methods for Conducting the Safety Assessment Process on Civil Airborne Systems and Equipment SAE ARP5288 Transport Category Airplane Head Up Display Systems

SAE AS8055 Minimum Performance Standards for Airborne Head Up Display The following documents are available from the RTCA, Inc. These documents can be purchased by mail from the RTCA Inc., 1150 18th Street NW, Suite 910, Washington, DC 20036; by fax, after completing the Document Order Form and faxing to 202-833- 9434; or electronically from the RTCA online store at: http://www.rtca.org/onlinecart/.

Number Title

RTCA DO-178B/ EUROCAE ED-12B

RTCA DO-178B/ EUROCAE ED-12B

Software Considerations in Airborne Systems and Equipment Certification

RTCA DO-160E/ EUROCAE ED–14D

Environmental Conditions and Test Procedures for Airborne Equipment

RTCA DO-254/ EUROCAE ED-80

Design Assurance Guidance for Airborne Electronic Hardware

RTCA DO-254/ EUROCAE ED-80

iv

10/16/12 AC 25.1329-1B Change 1

d. FAA Documents. An electronic copy of the following FAA document can be downloaded from the Internet at http://www.faa.gov/aircraft/air_cert/design_approvals/csta/publications/ .

Title

Federal Aviation Administration Human Factors Team Report on: The Interfaces Between Flight Crews and Modern Flight Deck Systems – Jun 18, 1996 An electronic copy of the following FAA Order can be downloaded from the Internet at http://rgl.faa.gov/. A paper copy may be ordered from the U.S. Department of Transportation, Subsequent Distribution Office, M-30, Ardmore East Business Center, 3341 Q 75th Avenue, Landover, MD 20795.

Number Title

FAA Order 8260.3 United States Standard for Terminal Instrument Procedures John Piccola Acting Manager, Transport Airplane Directorate Aircraft Certification Service

v

This page left blank.

vi

CONTENTS Paragraph Page

Chapter 1. Background 11. General 13 a. Advisory Circular (AC) 25.1329-1A 13 b. Scope 13 12. Evolution of Flight Guidance Systems (FGS) 13 a. Complexity 13 b. Guidance Considerations 13 13 – 16. [RESERVED] 13

Chapter 2. Overview of Flight Guidance Systems (FGS) 17. Purpose of FGS 15 18. FGS Components 15 a. Included in Definition 15 b. Excluded from Definition 15 19. FGS Functions 15 a. Elements of FGS 15 b. Approach and Landing System 15 c. Flight Management System (FMS) 16 d. Design Philosophy 16 e. Description of FGS Behavior and Operation 16 20. Compliance with § 25.1329 16 a. General 16 b. Relevant Paragraphs 16 Table 2-1 Cross-References § 25.1329 Paragraphs to AC Chapters

17

21 – 26 [RESERVED] 22

21 – 26 [RESERVED] 22

Chapter 3. FGS Engagement, Disengagement,

Indications, and Override 27. Autopilot Engagement, Disengagement, and Indications 23 a. Autopilot Engagement 23 (1) Single Switch Action 23 (2) Engagement Status of Autopilot 23 (3) Multiple Autopilots 23 (4) Acceptable Transients 23

Paragraph Page (5) Flight Director (FD) Not Engaged 23 (6) FD Engaged 24 b. Autopilot Disengagement 24 (1) General 24 (2) Autopilot Disengagement Alerts 25 (3) Quick Disengagement Control 26 (4) Alternative Means of Autopilot Disengagement 26 (5) Flightcrew Pitch Trim Input 27 28. FD Engagement, Disengagement, and Indications 27 a. FD Engagement 27 (1) General 27 (2) Guidance Cue(s) 28 (3) Reactive Windshear Guidance System 28 b. FD Disengagement 29 29. Autothrust Engagement, Disengagement, and Indications 29 a. Autothrust Engagement 29 (1) Indication 29 (2) Accessibility of Controls 29 (3) Inadvertent Engagement/Disengagement 29 (4) Automatic Engagement 29 b. Autothrust Disengagement 30 (1) Indication of Disengagement 30 (2) Inadvertent Disengagement 30 (3) Consequence of Disengagement 30 (4) Autothrust Quick Disengagement Control 30 30. Override of the FGS 31 a. General 31 b. Autopilot Override 31 (1) With Automatic Disengagement 31 (2) Without Automatic Disengagement 31 c. Autothrust Override 32 (1) Force Required 32 (2) Response to Override 32 (3) Engagement Status with Override 32 31. FGS Engagement Mode Compatibility 33 a. FGS Mode Engagement Philosophy 33 b. Engagement Mode Compatibility 33 32 — 41. [RESERVED] 33

Chapter 4. Controls, Indications, and Alerts Paragraph Page 42. General 35 a. Human-Machine Interface 35 b. Design of Controls, Indications, and Alerts 35 c. Evaluation of Information Provided by FGS 35 43. FGS Controls 35 a. General 35 b. Design Considerations 35 (1) Differentiation of Knob Shape and Position 35 (2) Design to Support Correct Selection of Target Values 36 (3) Commonality Across Aircraft Types 36 (4) Positioning of Controls and Related Indications 36 (5) Inadvertent Operation 36 44. FGS Mode Selection, Annunciation, and Indication 36 a. Annunciation of Engagement of the FGS 36 b. Description of FGS Modes 36 c. FGS Mode Annunciations 36 (1) Active and Armed Modes 36 (2) Location 37 (3) Discriminators 37 (4) Color 37 d. Mode Changes 37 (1) Operationally Relevant Mode Changes 37 (2) Attention-Getting Features 37 (3) Use of Alerts 38 e. Failure to Engage or Arm 38 f. FGS Mode Display and Indications 38 45. FGS Alerting, Warning, Caution, Advisory, and Status 38 a. General 38 (1) Alerting Provisions 38 (2) Determination of FGS Capability 38 b. Speed Protection Alerts 38 (1) Alerts to Crew 38 (2) Alert Specifications 39 (3) Consistency 39 (4) Nuisance Alerts 39 c. Loss of Autopilot Approach Mode 39 d. Awareness of Potential Significant Transient Condition (“Bark Before Bite”)

39

(1) General 39 (2) Flightcrew Alert(s) 39 (3) Situations to Consider for an Alert 40

Paragraph Page (4) Automatic Disengagement 40 46. FGS Considerations for Head Up Displays (HUD) 41 a. General 41 b. Characteristics of HUD Guidance 41 (1) Supplemental Use Display System 41 (2) External Visual References 41 (3) Interference and Occlusion 41 (4) Display Criteria 42 (5) Conformal Symbology 42 (6) Low Visibility Approach 42 (7) Clutter 42 c. HUD/Head Down Display (HDD) Compatibility 42 (1) General 42 (2) Consistency and Compatibility 42 d. Alerting Issues 43 (1) Alerts Displayed on HUDs 43 (2) Monochrome HUDs 44 (3) Mulit-Color HUDs 44 (4) Single HUD Installation 44 (5) Dual HUD Installations 44 (6) Ground Proximity Warning System (GPWS)/Traffic Alert and Collision Avoidance System (TCAS) Alerts On HUD

44

e. Upset/Unusual Attitude Recovery Guidance 44 (1) Guidance Cues 44 (2) Orientation Cues 45 47 – 51. [RESERVED] 45

Chapter 5. Performance of Function

Chapter 5. Performance of Function

52. General 47 a. Intended Function 47 b. Effect of System Tolerances 47 53. Normal Performance 47 a. General 47 b. Conditions to Consider 47 Table 5.1 Examples of Normal Conditions 48 c. Level of Performance 49 (1) Significant Characteristics 49 (2) Configuration Changes 49 (3) Compliance Evaluation 49 (4) Prescribed Levels of Performance 49 (5) Equivalence of Performance 49 (6) Autopilot 49

Paragraph Page (7) Flight Director (FD) 49 (8) Autothrust 49 (9) Automatic Trim 49 54. Performance in Rare Normal Conditions 50 a. General 50 (1) Range of Conditions 50 (2) Effect on Performance 50 b. Conditions to Consider 50 Table 5-2 Examples of Rare Normal Conditions 51 c. Level of Performance 52 (1) Performance Standard 52 (2) Autopilot Authority Limit 52 (3) Masking of Potential Hazard 52 55. Icing Considerations in Normal and Rare Normal Conditions 52 a. Effect on Performance 52 b. Alerts 52 c. Effect on Speed Protection 53 56. Performance in Non-Normal Conditions 53 a. General 53 b. Considerations to Consider 53 Table 5-3 Examples of Non-Normal Conditions 54 c. Level of Performance 55 (1) Performance Standard 55 (2) Autopilot Authority Limit 55 (3) Masking of Potential Hazard 55 57. Speed Protection 55 a. General 55 (1) Speed Excursions 55 (2) Compliance with § 25.1329(h) 55 (3) Design Standard 56 b. Low Speed Protection 57 (1) General 57 (2) Factors to Consider 57 (3) Low Speed Protection During Approach Operations 57 (4) Windshear Recovery Guidance 59 c. High Speed Protection 59 (1) General 59 (2) Factors to Consider 59 58 – 61. [RESERVED] 60

Chapter 6. Characteristics of Specific Modes Paragraph Page 62. General 61 63. Lateral Modes 61 a. Heading or Track Hold 61 b. Heading or Track Select 61 c. Lateral Navigation (LNAV) Mode 61 (1) Lateral Flight Path 61 (2) Automatic Mode Transitions 61 (3) Takeoff or Go-Around (TOGA) 62 64. Vertical Modes 62 a. Target Altitude Selection 62 b. Vertical Speed 62 c. Flight Path Angle 62 d. Indicated Airspeed (IAS)/Mach Hold [speed on elevator] 62 e. Indicated Airspeed (IAS)/Mach Select [speed on elevator] 62 f. Flight Level (FL) Change [speed on elevator] 63 g. Altitude Capture 63 (1) Mode Transition 63 (2) Guidelines for Altitude Capture Mode 63 h. Altitude Hold 64 (1) Entering Mode 64 (2) Mode Transition Annunciation 64 (3) Barometric Pressure Adjustment 64 i. VNAV 65 (1) FMS Path 65 (2) Climb or Descent 65 65. Multi-Axis Modes 66 a. Takeoff Mode 66 (1) Vertical Guidance 66 (2) Lateral Guidance 66 (3) Rotation Guidance 66 (4) Autothrust 66 (5) Operation and Performance 66 b. Go-Around Mode 67 (1) Vertical Elements 67 (2) Speed 67 (3) Autothrust 67 (4) Engagement 68 (5) All Engine and Engine Out Capability 68 c. Approach Mode 68 (1) Final Approach Path 68 (2) Mode Annunciations 68

Paragraph Page (3) Sub-Modes 68 (4) Mode Engagement Sequence 68 66. Autothrust Modes 68 a. Thrust Mode 68 b. Speed Mode 68 c. Retard Mode 69 67. Special Considerations for VNAV Approach Operations Related to Selecting a Target Altitude

69

a. Approach Operations 69 b. VNAV Path Operations 69 68. Control Wheel Steering (CWS) [control steering through the autopilot]

69

a. General 69 b. Design 69 (1) Control Forces 69 (2) Bank and Pitch Attitudes 70 (3) Control Behavior 70 (4) Stall and Stall Recovery 70 (5) Adjustments to Trim 70 (6) Takeoff and Landing 70 (7) Automatic Reversion to CWS Mode 70 c. Terminology 71 (1) Touch Control Steering (TCS) 71 (2) Supervisory Override 71 69. Special Considerations for the Integration of Fly-by-Wire Flight Control Systems and FGS

71

a. Speed Protection 71 b. System Degradation 71 70 – 74 [RESERVED] 71

Chapter 7. FGS Integration 75. General 73 76. System Integration Issues 73 a. Common and Cascading Failure Modes 73 b. Risk of Error 73 c. System Safety Analysis 73 77. Functional Interfaces 74 a. Interfacing Sensors 74 b. Potential Inconsistencies Between Systems 74 c. Function and Performance 74 78 – 82 [RESERVED] 74

Chapter 8. Safety Assessment Paragraph Page 83. General 75 a. Basic Safety Requirements 75 b. Safety Assessment 75 c. Validation of Safety Assessment 75 d. Coordination with the FAA 75 84. FGS Failure Conditions 75 a. Functionality 76 b. Effect of Failure Condition 76 85. Type and Severity of Failure Conditions 76 a. Types of Failure Conditions 76 (1) Loss of Function 76 (2) Malfunction 77 b. Cause 77 c. Severity 77 d. Assessment of Failure Conditions 77 (1) Functional Failures 77 (2) Airframe Loads 77 (3) Assessing Total Effect of Failure 78 86. Mitigation of Failure Conditions 78 a. General 78 b. Identification of Methods 78 c. FGS De-Selection 78 87. Validation of Failure Conditions 78 a. General 78 b. Validation Options 79 c. Validation Methodology 79 88. Specific Considerations 79 a. FGS Action During Ground Operations 79 b. FGS Operations in Close Proximity to the Ground 79 (1) Takeoff 80 (2) Approach 81 c. Cruise Operations 82 d. Asymmetric Thrust During Autothrust Operation 82 89. Failure to Disengage the FGS 83 90 – 97 [RESERVED] 83

Chapter 9. Compliance Demonstration Using

Chapter 9. Compliance Demonstration Using

Flight Test and Simulation

Paragraph Page 98. General 85 a. Methods of Compliance Demonstration 85 b. Criteria for Establishing Compliance 85 c. Elements of Certification Flight Test 85 d. Pilot–in–the–Loop Evaluation 85 e. Other Applicable Guidance Material for FGS Takeoff and/or Approach Modes

86

(1) Criteria to Consider 86 (2) Procedures to Show Compliance 86 f. Relation of AC Chapters 86 Figure 9-1, Relationship Between AC Chapters 87 99. Performance Demonstration (Fault Free): § 25.1301 88 a. General 88 (1) Certification Plan 88 (2) Evaluating Performance 88 (3) Evaluating Compatibility of Mode Controls, Indications, and Alerts

88

b. Normal Performance 88 (1) Demonstration 88 (2) Evaluation 88 (3) Expected Errors 89 c. Performance in “Other Than Normal” Conditions 89 (1) Test Program 89 (2) Evaluation of FGS 89 (3) Additional Guidance for Windshear 89 d. Specific Performance Conditions 89 (1) Icing Considerations 89 (2) Low-Speed Protection 90 (3) High-Speed Protection 91 (4) Go-Around 91 (5) Steep Approach [special authorization] 92 (6) Indication Of and Response To an Out Of Trim Condition 93 e. Flight Director (FD) /Head Up Display (HUD 93 (1) General 93 (2) Specific Demonstrations for HUD 94 (3) Simulator Demonstration for HUD 95 f. Flightcrew Override of the FGS 96 (1) Autopilot Override 96 (2) Autothrust Override 97 (3) Pitch Trim System Evaluation During Autopilot Override 97

Paragraph Page 100. Failure Conditions Requiring Validation: § 25.1309 97 a. General 97 (1) Safety Assessment 97 (2) Evaluation of Failure Conditions 97 b. Validation Elements 98 (1) Assessment 98 (2) Failure Condition 98 (3) Pilot Recognition 98 (4) Pilot Reaction Time 100 (5) Pilot Recovery 100 c. Takeoff 101 (1) Worst Case Failure Condition 101 (2) Failures to be Evaluated 101 (3) On Runway Guidance 101 d. Climb, Cruise, Descent, and Holding 101 e. Maneuvering 101 f. Approach 101 (1) Approach With Vertical Path Reference 101 (2) Approach Without Vertical Path Reference 103 (3) Steep Approach 103 g. Specific Conditions 103 (1) Failure Conditions to be Evaluated 103 (2) Failure to Disengage 103 101. Criteria Supporting Operational Use of Autopilot 103 a. Typical Flight Operations 103 b. Operations in Close Proximity to the Ground 104 (1) General 104 (2) Considerations 104 (3) Autopilot Engagement Altitude/Height After Takeoff 104 (4) Autopilot Engagement During Approach 105 (5) Circling Approach 107 c. Climb, Cruise, Descent, and Holding 107 d. Maneuvering 107 102. Automatic Disengagement of the Autopilot 108 103. Assessment of Human Factors 108 a. General 108 b. Flight Evaluations 108 (1) During Certification 108 (2) Prior to Certification 108 (3) Credit to Establish FGS Compliance 109 (4) Simulation Versus Flight Tests 109 c. Structured Subjective Evaluations 109 d. Pilot Training and Experience 110

Change 1 Paragraph Page e. Evaluating New or Unique Design Features 110 f. Certification Planning Documentation 110 104 – 108 [RESERVED] 110

Chapter 10. Airplane Flight Manual 109. General 111 a. AFM Terminology 111 b. Low-Visibility Operations 111 110. Information Supporting Operational Use of Autopilot 111 a. General 111 b. Specifying a Minimum Use Height (MUH) 111 (1) Takeoff 111 (2) Cruise 111 (3) Approach 111 c. Maximum Displacement Deviation 112 111. Limitations 112 112. Non-Normal/Emergency Procedures 112 113. Normal Procedures 112 a. Documentation of Normal Procedures 112 b. Maximum Displacement Deviation 112 c. Procedures for Use of FGS in Icing Conditions 112 d. Aircraft With Published Flightcrew Operation Manuals (FCOM)

112

e. Aircraft Without Published FCOMs 113

Appendices 1 Safety Assessment A1-1 1. General A1-1 2. Identification of Failure Conditions A1-1 3. Considerations When Assessing The Severity of Failure Condition Effects

A1-2

4. Failure Condition Classification A1-3 2 Definitions A2-1 3 Acronyms A3-1

4. Failure Condition Classification A1-3 2 Definitions A2-1 3 Acronyms A3-1

Change 1

Tables Number Page 2-1 Cross-References § 25.1329 Paragraphs to AC Chapters 17 5-1 Examples of Normal Conditions 48 5-2 Examples of Rare Normal Conditions 51 5-3 Examples of Non-Normal Conditions 54

Figures Number Page 9-1 Relationship Between AC Chapters (Chapter 9) 87

7/17/06 AC 25.1329-1B 1 — 10 [Reserved]

Chapter 1 Background 11. General. a. Advisory Circular (AC) 25.1329-1B. This advisory material replaces material previously provided in AC 25.1329-1A for autopilots. The automatic control and guidance systems in current aircraft have evolved to a level that dictates a revision to current advisory material. b. Scope. This advisory material provides information for flight guidance systems (FGS), which include any autopilot functions, flight director (FD) functions, and automatic thrust control functions as well as any interactions with stability augmentation and trim functions. 12. Evolution of FGSs. a. Complexity. There have been dramatic changes in technology and system design, which have resulted in much higher levels of integration, automation, and complexity. These changes have also redefined the allocation of functions and interfaces between systems. Relatively simple, dedicated systems have been replaced with digital multi–function systems with more modes and automatic changes in modes of operation. The introduction of fly–by–wire flight control systems has created new interface considerations for the FGS. b. Guidance Considerations. These new systems are capable of providing better performance, increased safety, and decreased workload. But, if designed without consideration for the criteria in this AC, these systems could also be confusing and not immediately intuitive for the flightcrew. Significant operational experience has been gained on new generation systems, and this guidance material is provided based on that experience. 13 — 16 [Reserved]

7/17/06 AC 25.1329-1B

This page left blank.

Chapter 2 Overview of flight guidance systems (FGS) 17. Purpose of FGS. The FGS is primarily intended to assist the flightcrew in the basic control and tactical guidance of the airplane. The system may also provide workload relief to the pilots and provide a means to fly a flight path more accurately to support specific operational requirements, such as reduced vertical separation minimum (RVSM) or required navigation performance (RNP). 18. FGS Components. a. Included in Definition. For the purpose of this AC, the term “FGS” includes all the equipment necessary to accomplish the FGS function, including the sensors, computers, power supplies, servo–motors/actuators, and associated wiring. It includes any indications and controllers necessary for the pilot to manage and supervise the system. b. Excluded from Definition.

Any equipment or component that remains mechanically connected to the primary flight controls or propulsion controls when the FGS is not in use is regarded as a part of the primary flight controls and propulsion system, and the provisions for such systems are applicable. 19. FGS functions. a. Elements of FGS. (1) Flight guidance and control (for example, autopilot, FD displayed head down or head up). (2) Autothrottle/autothrust systems. The term “autothrust” is generic in nature and includes power control systems for propeller driven airplanes. (3) Interactions with stability augmentation and trim systems. (4) Alerting, status, mode annunciation, and situation information associated with flight guidance and control functions. b. Approach and Landing System. The FGS includes those functions necessary to provide guidance and control in conjunction with an approach and landing system, such as the following: (1) Instrument landing system (ILS) (2) Microwave landing system (MLS)

Change 1 (3) Ground-Based Augmentation System (GBAS) Landing System (GLS.) c. Flight Management System (FMS). The FGS also includes those functions necessary to provide guidance and control in conjunction with a FMS. The FGS does not include the flight planning and the generation of flight path and speed profiles tied to waypoints and other flight planning aspects of the FMS. However, it does include the interface between the FMS and FGS necessary for the execution of flight path and speed commands. d. Design Philosophy. The applicant should establish, document, and follow a design philosophy that supports the intended operational use regarding FGS behavior, modes of operation, the pilot interface with controls, indications, alerts, and mode functionality. e. Description of FGS Behavior and Operation. A description of the FGS behavior and operation should be addressed from flightcrew and maintenance perspectives in appropriate documentation and training material. 20. Compliance with § 25.1329. a. General. Subsequent chapters of this advisory material provide acceptable means of compliance with § 25.1329 and the applicability of other part 25 rules to FGS (e.g., §§ 25.1301 and 25.1309). The demonstrated means of compliance may include a combination of analysis, laboratory testing, flight testing, and simulator testing. The applicant should coordinate with the FAA early in the certification program via a certification plan to reach agreement on the methods to be used to demonstrate compliance.

Note 1: This AC uses the terminology “should” and “should not” when discussing compliance to the AC itself, as the AC represents one, but not the only, method of complying with § 25.1329. Note 2: This AC uses the terminology “must” and “may not” when discussing compliance to § 25.1329 and other specific rules, as compliance to a rule is not optional. In these cases, the AC text supplies a reference to the specific rule being discussed. b. Relevant Paragraphs. The following table (Table 2-1) lists the relevant paragraphs of § 25.1329 and indicates where acceptable means of compliance with each paragraph can be found within this AC.

Table 2-1 Cross-References § 25.1329 Paragraphs to AC Chapters

Section/Paragraph AC Chapter Reference/Paragraph

§ 25.1329(a) Quick disengagement controls for the autopilot and autothrust functions must be provided for each pilot. The autopilot quick disengagement controls must be located on both control wheels (or equivalent). The autothrust quick disengagement controls must be located on the thrust control levers. Quick disengagement controls must be readily accessible to each pilot while operating the control wheel (or equivalent) and thrust control levers.

Chapter 3 FGS Engagement, Disengagement, Indications, and Override

Chapter 3 FGS Engagement, Disengagement, Indications, and Override

Paragraph 27, Autopilot Engagement, Disengagement, and Indications Paragraph 29, Autothrust Engagement, Disengagement, Indications § 25.1329(b) The effects of a failure of the system to disengage the autopilot or autothrust functions when manually commanded by the pilot must be assessed in accordance with the requirements of § 25.1309.

Chapter 3 FGS Engagement, Disengagement, Indications, and Override

Paragraph 27, Autopilot Engagement, Disengagement, Indications Paragraph 29, Autothrust Engagement, Disengagement, and Indications Paragraph 30, Override of the FGS Chapter 8 Safety Assessment

Paragraph 89, Failure to Disengage the FGS § 25.1329(c) Engagement or switching of the flight guidance system, a mode, or a sensor may not cause a transient response of the airplane’s flight path any greater than a minor transient, as defined in paragraph (n)(1) of this section.

Chapter 3 FGS Engagement, Disengagement, Indications, and Override Chapter 8 Safety Assessment

Chapter 3 FGS Engagement, Disengagement, Indications, and Override Chapter 8 Safety Assessment

Section/Paragraph AC Chapter Reference/Paragraph

§ 25.1329(d) Under normal conditions, the disengagement of any automatic control function of a flight guidance system may not cause a transient response of the airplane’s flight path any greater than a minor transient.

Chapter 3 FGS Engagement, Disengagement, Indications, and Override Chapter 4 Controls, Indications, and Alerts

Paragraph 45, FGS Alerting, Warning, Caution, Advisory, and Status Chapter 8 Safety Assessment

§ 25.1329(e) Under rare normal and non-normal conditions, disengagement of any automatic control function of a flight guidance system may not result in a transient any greater than a significant transient, as defined in paragraph (n)(2) of this section.

Chapter 3 FGS Engagement, Disengagement, Indications, and Override Chapter 4 Controls, Indications, and Alerts

Paragraph 45, FGS Alerting, Warning, Caution, Advisory, and Status Chapter 8 Safety Assessment

§ 25.1329(f) The function and direction of motion of each command reference control, such as heading select or vertical speed, must be plainly indicated on, or adjacent to, each control if necessary to prevent inappropriate use or confusion.

Chapter 4 Controls, Indications and Alerts

Chapter 4 Controls, Indications and Alerts

Paragraph 43, FGS Controls

Section/Paragraph AC Chapter Reference/Paragraph

§ 25.1329(g) Under any condition of flight appropriate to its use, the flight guidance system may not produce hazardous loads on the airplane, nor create hazardous deviations in the flight path. This applies to both fault-free operation and in the event of a malfunction, and assumes that the pilot begins corrective action within a reasonable period of time.

Chapter 4 Controls, Indications and Alerts

Paragraph 45, FGS Alerting, Warning, Caution, Advisory, and Status Chapter 5 Performance of Function Chapter 8 Safety Assessment Chapter 9 Compliance Demonstration Using Flight Test and Simulation

§ 25.1329(h) When the flight guidance system is in use, a means must be provided to avoid excursions beyond an acceptable margin from the speed range of the normal flight envelope. If the airplane experiences an excursion outside this range, a means must be provided to prevent the flight guidance system from providing guidance or control to an unsafe speed.

Chapter 5 Performance of Function

Chapter 5 Performance of Function

Paragraph 57, Speed Protection

§ 25.1329(i) The flight guidance system functions, controls, indications, and alerts must be designed to minimize flightcrew errors and confusion concerning the behavior and operation of the flight guidance system. Means must be provided to indicate the current mode of operation, including any armed modes, transitions, and reversions. Selector switch position is not an acceptable means of indication. The controls and indications must be grouped and presented in a logical and consistent manner. The indications must be visible to each pilot under all expected lighting conditions.

Chapter 4 Controls, Indications, and Alerts

Chapter 4 Controls, Indications, and Alerts

Section/Paragraph AC Chapter Reference/Paragraph

§ 25.1329(j) Following disengagement of the autopilot, a warning (visual and auditory) must be provided to each pilot and be timely and distinct from all other cockpit warnings.

Chapter 3 FGS Engagement, Disengagement, Indications, and Override

Chapter 3 FGS Engagement, Disengagement, Indications, and Override

Paragraph 27, Autopilot Engagement, Disengagement, and Indications, Chapter 8 Safety Assessment

§ 25.1329(k) Following disengagement of the autothrust function, a caution must be provided to each pilot.

Chapter 3 FGS Engagement, Disengagement, Indications, and Override

Paragraph 27, Autopilot Engagement, Disengagement, and Indications Chapter 8 Safety Assessment

§ 25.1329(l) The autopilot may not create a potential hazard when the flightcrew applies an override force to the flight controls.

Chapter 3 FGS Engagement, Disengagement, Indications, and Override

Paragraph 30, Override of the FGS Chapter 4 Controls, Indications, and Alerts

Paragraph 45, FGS Alerting, Warning, Caution, Advisory, and Status Chapter 8 Safety Assessment

10/16/12 AC 25.1329-1B Change 1

Section/Paragraph AC Chapter Reference/Paragraph

§ 25.1329(m) During autothrust operation, it must be possible for the flightcrew to move the thrust levers without requiring excessive force. The autothrust may not create a potential hazard when the flightcrew applies an override force to the thrust levers.

Chapter 3 FGS Engagement, Disengagement, Indications, and Override paragraph 30, Override of the FGS Chapter 8 Safety Assessment

§ 25.1329(n) For purposes of this section, a transient is a disturbance in the control or flight path of the airplane that is not consistent with response to flightcrew inputs or environmental conditions. (1) A minor transient would not significantly reduce safety margins and would involve flightcrew actions that are well within their capabilities. A minor transient may involve a slight increase in flightcrew workload or some physical discomfort to passengers or cabin crew. (2) A significant transient may lead to a significant reduction in safety margins, an increase in flightcrew workload, discomfort to the flightcrew, or physical distress to the passengers or cabin crew, possibly including non-fatal injuries. Significant transients do not require, in order to remain within or recover to the normal flight envelope, any of the following: (i) Exceptional piloting skill, alertness, or strength. (ii) Forces applied by the pilot which are greater than those specified in § 25.143(d). (iii) Accelerations or attitudes in the airplane that might result in further hazard to secured or non-secured occupants.

Appendix 3 - Definitions

Appendix 3 - Definitions

Note: The text for each paragraph in § 25.1329 is included in this AC for reference only. Please refer to the actual text in 14 CFR part 25. 21 — 26 [Reserved]

Chapter 3 FGS engagement, disengagement,

indications, and override 27. Autopilot engagement, disengagement, and indications. Autopilot engagement and disengagement should be accomplished in a manner consistent with other flightcrew procedures and tasks and should not require undue attention. a. Autopilot Engagement. (1) Single Switch Action. Each pilot should be able to select the autopilot function of the FGS with a single switch action. The single switch action should engage both the pitch and roll axes. (2) Engagement Status of Autopilot. The autopilot system should provide positive indication to the flightcrew that the system has been engaged. The selector switch position is not acceptable as a means of indication. [See § 25.1329(i)] Regardless of the method used, the engagement status (and changes in status) of the autopilot(s) should be clearly indicated and should not require undue attention or recall.

Note: If an operational need is identified for split–axis engagement, then annunciation or indication should be provided for each axis. (3) Multiple Autopilots. If a single autopilot within a multiple autopilot installation can be individually selected by the flightcrew, the engagement annunciation should reflect the flightcrew selection. It should not be possible for multiple autopilots to be engaged in different modes. For modes that use multiple autopilots, the additional autopilots may engage automatically at selection of the mode or after arming the mode. A means should be provided to determine that adequate autopilot capability exists to support the intended operation (for example, "Land 2" and "Land 3" are used in some aircraft). (4) Acceptable Transients. The engagement of the autopilot should be free of perceptible transients. Under dynamic conditions, including maneuvering flight, minor transients are acceptable. However, with normal operating conditions, significant transients may not occur. [See § 25.1329(d)] (5) Flight Director (FD) Not Engaged. Without a FD engaged, the initial lateral and vertical modes should be consistent with minimal disturbance from the flight path. For example, the lateral mode at engagement may roll the airplane to wings level and then hold the airplane heading/track or maintain the existing bank angle (if in a normal range). A heading/track pre–select at engagement function may be provided, if precautions are taken to ensure that selection reflects the current intent of the flightcrew. The modes at engagement should be annunciated and any associated selected target values should be displayed.

10/16/12 AC 25.1329-1B Change 1

(6) FD Engaged. With a FD engaged, the autopilot should engage in a mode consistent with (that is, the same as, or if that is not possible, then compatible with) the active FD mode of operation. Consideration should be given to the mode in which the autopilot will engage when large commands are present on either or both FDs. The following examples list some of these considerations: (a) Should the autopilot retain the active FD mode or should it engage in the basic default mode? (b) Are there any implications for current flight path references and targets? (c) Is there any potential for flightcrew confusion and unintended changes in flight path or modes?

Note: The design should consider the possibility that the pilot may attempt to engage the autopilot outside of the normal flight envelope. It is not required that the autopilot compensate for unusual attitudes or other situations outside the normal flight envelope, unless that is part of the autopilot’s intended function. b. Autopilot Disengagement. (1) General. (a) Normal Conditions. Under normal conditions, automatic or manual disengagement of the autopilot should be free of perceptible transients or out–of–trim forces that are not consistent with the maneuvers being conducted by the airplane at the time of disengagement. A disengagement in normal conditions may not result in a transient any greater than a minor transient. If multiple autopilots are engaged, any disengagement of an individual autopilot may not result in a transient any greater than a minor transient. [See § 25.1329(d)] The disengagement of an individual autopilot should not adversely affect the operation of the remaining engaged autopilot(s). (b) Other Than Normal Conditions. Under other than normal conditions (that is, non-normal or rare normal conditions), disengagement of the autopilot may not result in a transient any greater than a significant transient. [See § 25.1329(e)] (See Chapter 5, Performance of Function, paragraphs 54 and 56 of this AC for a discussion of non-normal and rare normal conditions). The flightcrew should be able to respond to a significant transient without using any of the following: 1 exceptional piloting skill, alertness, or strength, 2 forces greater than those given in § 25.143(d), or

10/16/12 AC 25.1329-1B Change 1

3 accelerations or attitudes in the airplane that might result in a hazard to secured or non–secured occupants. (c) Potential for Significant Transient. The flightcrew should be made aware (via a suitable alerting or other indication) of conditions or situations (for example, continued out–of–trim) that could result in a significant transient at disengagement. [See Chapter 4, Controls, Indications, and Alerts, paragraph 45d, Awareness of Potential Significant Transient Condition (“Bark before Bite”).]

Note: See Appendix 2 for definitions of significant transient and minor transient. See Chapter 5, Performance of Function, paragraphs 53, 54, and 56 for a discussion of normal conditions, rare normal conditions, and non-normal conditions. (2) Autopilot Disengagement Alerts. (a) Alert Type. Since it is necessary for a pilot to immediately assume manual control following disengagement (manual or automatic) of the autopilot, a warning (both visual and aural) must be given. [See § 25.1329(j)] (b) Aural Warning Specifications. A timely aural warning must be provided and must be distinct from all other cockpit warnings. [See § 25.1329(j)] It should sound long enough to ensure that it is heard and recognized by the pilot and other flight crewmembers, but not so long that it adversely affects communication between crewmembers or is a distraction. The aural warning should continue until silenced by one of the following means: 1 Activation of the autopilot quick disengagement control. 2 Re–engagement of the autopilot. 3 Another acceptable means. (c) Multiple Autopilot System. 1 Disengagement of an autopilot channel within a multiple-channel autopilot system, downgraded system capability, or a reduction in the level of system redundancy which requires immediate flightcrew awareness and possible timely action should cause a caution level alert to be issued to the flightcrew. 2 Disengagement of an autopilot channel within a multiple-channel autopilot system which requires only flightcrew awareness should cause a suitable advisory level alert to be issued to the flightcrew.

(3) Quick Disengagement Control. (a) Purpose. The purpose of the quick disengagement control is to ensure the capability for each pilot to manually disengage the autopilot quickly with a minimum of pilot hand/limb movement. (b) Location. The quick disengagement control must be located on each control wheel or equivalent. [See § 25.1329(a)] It should be within easy reach of one or more fingers/thumb of the pilot’s hand when the hand is in a position for normal use on the control wheel or equivalent. (c) Criteria. The quick disengagement control: 1 Must be operable with one hand on the control wheel or equivalent and the other hand on the thrust levers. [See § 25.1329(a)] 2 Should be accessible and operable from a normal hands–on position without requiring a shift in hand position or grip on the control wheel or equivalent. 3 Should be easily locatable by the pilot without having to first locate the control visually. 4 Should be designed so that any action to operate the quick disengagement control should not cause an unintended input to the control wheel (or equivalent). 5 Should be designed to minimize inadvertent operation and interference from other nearby control wheel (or equivalent) switches/ devices, such as radio control or trim.

Note: When establishing location of the quick disengagement control, consideration should be given to its accessibility with large displacements of or forces on the control wheel (or equivalent) and the possible need to operate the quick disengagement control with the other hand. (4) Alternative Means of Autopilot Disengagement. (a) Factors to Consider. When a § 25.1309 assessment shows a need for an alternative means of disengagement, the following factors should be addressed: 1 Independence from primary quick disengagement control. 2 Whether alternative means are readily accessible to each pilot.

3 Reliability and the possibility of latent failure of those alternative means. (b) Acceptable Means. The following means of providing an alternative disengagement have been found to be acceptable: 1 Selecting the engagement control to the “off” position. 2 Disengaging the bar on mode select panel (MSP). 3 Activating the trim switch on the yoke.

Note: Use of circuit breakers as a means of disengagement is not considered acceptable. (5) Flightcrew Pitch Trim Input. If the autopilot is engaged and the pilot applies manual pitch trim input, and the autopilot is designed to disengage because of that flight crew action, the autopilot must disengage with no more than a minor transient. [See § 25.1329(c)] Alternatively, pitch trim changes may be inhibited, such that the potential for a transient is removed. 28. FD engagement, disengagement, and indications. Engagement and disengagement of the FD should be accomplished consistent with other flightcrew procedures and tasks and should not require undue attention. a. FD Engagement. (1) General. (a) Selection. A means may be provided for each pilot to select (that is, turn on) and de-select (that is, turn off) the FD for display on his or her primary flight display (PFD). (b) Engagement. A FD is considered “engaged” if it is selected and displaying guidance cues.

Note: The distinction is made between “engaged” and “selected,” because the FD might be selected but not displaying guidance cue(s) (for example, the cue(s) are biased out of view). (c) Engagement Status of FD. The selection status of the FD and the source of FD guidance should be clear and unambiguous. Failure of a selected FD should be clearly annunciated.

(d) Multiple FDs. If there are multiple FDs and if necessary for crew awareness, indications should be provided to denote which FD is engaged (for example, FD1, FD2, HUD (head up display)). For airplanes with multiple FDs installed, all engaged FDs should always be in the same armed and active FGS modes. The selection status of each FD should be clear and unambiguous for each pilot. In addition, indications should be provided to denote loss of FD independence (for example, first officer selection of captain’s FD). (e) Autopilot Engaged. A FD should engage into the current modes and targets of an already engaged autopilot or FD, if any. With no autopilot engaged, the basic modes at engagement of the FD functions should be established consistent with typical flight operations.

Note: The engagement of the pitch axis in Vertical Speed or Flight Path Angle and engagement of the lateral axis in Heading Hold, Heading Select, or Bank Angle Hold have been found to be acceptable. (f) HUD. Since the HUD can display flight guidance, the HUD guidance mode should be indicated to both pilots and should be compatible with the active head down FD mode. (g) Maneuvering Flight. Engagement during maneuvering flight should be considered.

Note: The design should consider the safety consequences if it is possible for the FD to engage outside of the normal flight envelope. It is not required that the FD should compensate for unusual attitudes or other situations outside the normal flight envelope, unless that is part of the FD’s intended function. (2) Guidance Cue(s). (a) Display. The FD command guidance cue(s) will typically be displayed under the following conditions: 1 When the FD is selected and valid command guidance is available, or 2 When the FD is automatically providing guidance (See paragraph (3), below). (b) Engagement Indication. The display of guidance cue(s) (for example, FD bars) is sufficient indication that the FD is engaged. (c) Invalid Guidance. The FD guidance cue(s) should be removed when guidance is determined to be invalid.

(3) Reactive Windshear Guidance System. For airplanes equipped with a FD windshear guidance system, FD engagement should be provided consistent with the criteria in AC 25–12, Airworthiness Criteria for the Approval of Airborne Windshear Warning Systems in Transport Category Airplanes; and AC 120–41, Criteria for Operational Approval of Airborne Windshear Alerting and Flight Guidance. b. FD Disengagement. There should be a means for each pilot to readily de-select his or her on–side FD function. Flightcrew awareness of disengagement and de-selection is important. Removal of guidance cue(s) alone is not sufficient indication of deselection, because the guidance cue(s) may be removed from view for a number of reasons, including invalid guidance or autopilot engagement. Therefore, the FD function should provide clear and unambiguous indication to the flightcrew that the function has been deselected. 29. Autothrust engagement, disengagement, and indications.

Engagement and disengagement should be accomplished in a manner consistent with other flightcrew procedures and tasks and should not require undue attention. a. Autothrust Engagement. (1) Indication. The autothrust function must provide the flightcrew positive indication that the system has been engaged. (See § 25.1329(i)) (2) Accessibility of Controls. The autothrust engagement controls should be accessible to each pilot. (3) Inadvertent Engagement/Disengagement. The autothrust function should normally be designed to prevent inadvertent engagement and inadvertent application of thrust for both on–ground and in–air operations. For example, separate arm and engage functions may be provided. (4) Automatic Engagement. Intended automatic engagement, such as a “wake up” mode to protect for unsafe speeds, may be acceptable. (See Chapter 5, paragraph 57b, Low Speed Protection. If such automatic engagement occurs, it should be clear to the flightcrew that automatic engagement has occurred. The automatic engagement may not cause a transient larger than a minor transient.

[See § 25.1329(c)] The transition to the engaged state should be smooth, and should not cause large, unexpected changes in pitch attitudes or pitching moments. The reason for automatic engagement should be clear and obvious to the flightcrew.

Note: The design should consider the possibility that the pilot may attempt to engage the autothrust function outside of the normal flight envelope or at excessive or too low engine thrust. It is not expected that the autothrust feature should compensate for situations outside the normal

flight envelope or normal engine operation range, unless that is part of the intended function of the autothrust system. b. Autothrust Disengagement. (1) Indication of Disengagement. Positive indication of disengagement of the autothrust function must result in a caution level alert to the flightcrew. [See § 25.1329(k)] The autothrust “engage” status annunciations should be deleted. (a) Visual Indication. 1 Following automatic disengagement: Visual indication of disengagement should persist until canceled by flightcrew action. 2 Following manual disengagement: If an aural alert is provided, visual indication of disengagement should persist for some minimum period. If an aural alert is not provided, visual indication of disengagement should persist until canceled by flightcrew action. (b) Aural alert. If provided, the aural disengagement alert should be of sufficient duration and volume to assure that the flightcrew has been alerted that disengagement has occurred.

However, an extended cycle of an aural alert is not acceptable following disengagement, if such an alert can significantly interfere with flightcrew coordination or radio communication. (2) Inadvertent Disengagement. The autothrust normally should be designed to preclude inadvertent disengagement during activation of autothrust modes of operation. (3) Consequence of Disengagement. Under normal conditions, autothrust disengagement may not cause a transient any greater than a minor transient. [See § 25.1329(d)] The transition to the disengaged state should be smooth and not cause unexpected changes in pitch attitude or pitching moment or a significant thrust transient. The disengagement should not preclude, inhibit, or interfere with timely thrust changes for go-around, landing, or other maneuvers requiring manual thrust changes. (4) Autothrust Quick Disengagement Control. Autothrust quick disengagement controls must be provided for each pilot on the respective thrust control (thrust lever or equivalent).

A single–action, quick disengagement switch must be incorporated on the thrust control, so that switch activation can be executed when the pilot’s other hand is on the control wheel (or equivalent). [See § 25.1329(a)] The disengagement control should be positioned such that inadvertent disengagement of the autothrust function is unlikely. Positioning the control on the outboard side has been shown to be acceptable for multi– engine aircraft. Thrust lever knob, end-mounted disengagement controls available on both sides to facilitate use by either pilot have been shown to be preferable to those positioned to be accessible by the pilot’s palm.

30. Override of the FGS. a. General. An override of an engaged FGS function is defined as an action taken by the flightcrew intended to prevent, oppose, or alter an operation being conducted by the FGS function without first disengaging that function. b. Autopilot Override. (1) With Automatic Disengagement. (a) Override Force. The autopilot should disengage when the flightcrew applies a significant override force to the controls. The applicant should interpret “significant” as a force that is consistent with an intention to overpower the autopilot by either or both pilots. The autopilot should not disengage by minor application of force to the controls, such as a pilot gently bumping the control column while entering or exiting a pilot seat during cruise.

Note: Twenty-five pounds (25 lbs) of force at the control column or wheel has been determined to be a significant override force level for other than approach operations on some aircraft types. To reduce nuisance disengagement, higher forces have been found acceptable for certain approach, landing, and go-around operations on some aircraft. The force to disengage an autopilot is not necessarily the force required at the column to oppose autopilot control, that is, to cause elevator movement. The corresponding forces for a sidestick controller may be different. (b) Transients Resulting from Override. In normal operating conditions, a transient larger than a minor transient may not result from autopilot disengagement when the flightcrew applies an override force to the controls. [See § 25.1329(d)] Mitigation may be accomplished through provision of an appropriate alert and flightcrew procedure. (c) Sustained Override Force Below Level Required for Automatic Disconnect. Sustained application of force below the disengagement threshold may not result in a potential hazard.

[See § 25.1329(l)] For example, the automatic trim should not run to oppose the override of the autopilot by the flightcrew that would result in unacceptable airplane motion, if the autopilot were to automatically disengage or be manually disengaged. (2) Without Automatic Disengagement. (a) Potential Hazard. If the FGS is not designed to disengage in response to any override force, then the response to an override may not result in a potential hazard. Sustained application of an override force may not result in a potential hazard, such as when the flightcrew abruptly releases the force on the controls. [See § 25.1329(l)] Mitigation may be accomplished through provision of an appropriate alert and flightcrew procedure.

Note: The term “sustained application of override force” is intended to describe a force that is applied to the controls which may be small, slow, and sustained for some period of time. This may be due to an inadvertent crew action or may be an intentional crew action meant to “assist” the autopilot in a particular maneuver. (See Chapter 9, Compliance Demonstration Using Flight Test and Simulation, paragraph 99f, Flightcrew Override of the FGS, for more information.) (b) Transients Resulting from Override. In normal operating conditions, a transient larger than a minor transient may not result from manual autopilot disengagement after the flightcrew has applied an override force to the controls. [See § 25.1329(d)] Mitigation may be accomplished through provision of an appropriate alert and flightcrew procedure.

Note 1: The term “override force” is intended to describe a pilot action that is intended to prevent, oppose or alter an operation being conducted by a flight guidance function without first disengaging that function. One possible reason for this action could be an avoidance maneuver, such as responding to a traffic alert and collision avoidance system (TCAS) resolution advisory that requires immediate action by the flightcrew and would typically involve a rapid and forceful input from the flightcrew.

Note 2: For control wheel steering considerations, see Chapter 6, Characteristics of Specific Modes, paragraph 68, Control Wheel Steering (CWS) [control steering through the autopilot]. c. Autothrust Override. (1) Force Required. It should be possible for the pilot to readily override the autothrust function and set thrust by moving the thrust levers (or equivalent) with one hand. (2) Response To Override. The autothrust response to a flightcrew override may not create a potential hazard. [See § 25.1329(m)] The autothrust response to the flightcrew override should not result in an abrupt change of pitch attitude, an abrupt pitching moment, or an uncontrolled change of thrust. (3) Engagement Status With Override. Autothrust functions may be designed to safely remain engaged during pilot override. Alternatively, autothrust functions may disengage as a result of pilot override, provided that the design prevents unintentional autothrust disengagement and adequately alerts the flightcrew to ensure pilot awareness.

31. FGS Engagmenet mode compatibility. a. FGS Mode Engagement Philosophy. A description of the philosophy used for the mode at engagement of the autopilot, FD, and autothrust functions should be provided in flightcrew training material. b. Engagement Mode Compatibility. It should not be possible to select incompatible FGS command or guidance functions, such as commanding speed through elevator and autothrust at the same time. 32 — 41 [Reserved]

This page left blank.

Chapter 4 Controls, Indications, and Alerts 42. General. a. Human-Machine Interface. The human-machine interface with the FGS is crucial to ensuring safe, effective, and consistent FGS operation. The manner in which FGS information is depicted to the flightcrew is vital to flightcrew awareness and, therefore, to safe operation of the FGS. b. Design of Controls, Indications, and Alerts. These features must be designed to minimize flightcrew errors and confusion. [See § 25.1329(i)] Indications and alerts should be presented in a manner compatible with the procedures and assigned tasks of the flightcrew and provide the necessary information to perform those tasks. The indications must be grouped and presented in a logical and consistent manner and must be visible from each pilot’s station under all expected lighting conditions. [See § 25.1329(i)] The choice of colors, fonts, font size, location, orientation, movement, graphical layout, and other characteristics—such as steady or flashing—should all contribute to the effectiveness of the system.

Controls, indications, and alerts should be implemented in a consistent manner. c. Evaluation of Information Provided by FGS. It is recommended that the applicant evaluate the adequacy and effectiveness of the information provided by the FGS interface, that is the controls, indications, alerts, and displays, to ensure flightcrew awareness of FGS behavior and operation. See Chapter 9, Compliance Demonstration Using Flight Test and Simulation, for more discussion of appropriate analyses which may include, for example, cognitive task analysis as a basis for evaluation. 43. FGS Controls. a. General. The FGS controls must be designed and located to prevent crew errors, confusion, and inadvertent operation. [See § 25.1329(i)] They should be designed to provide convenience of operation to each crewmember. The function and direction of motion of each control must be readily apparent or plainly indicated on or adjacent to each control, if needed to prevent inappropriate use or confusion.

[See § 25.1329(f)] Sections 25.777(b) and 25.779(a) provide requirements regarding direction of motion of flight deck controls. These requirements apply for FGS command reference controls which select target values, such as heading select or vertical speed. Section 25.781 also provides requirements for the shapes of the knobs. b. Design Considerations. The design of the FGS should address the following specific considerations: (1) Differentiation of Knob Shape and Position. Errors by the flightcrew have included confusing speed and heading knobs on the MSP.

(2) Design to Support Correct Selection of Target Values. Use of a single control, such as concentric controls, for selecting multiple command reference targets has resulted in erroneous target value selection. (3) Commonality Across Aircraft Types. Use of uniform control design in different aircraft prevents negative transfer of learning with respect to operation of the controls. Using knowledge about the operation of the controls on one type of airplane has resulted in activation of the incorrect control when pilots move from that type of airplane to another type of airplane. An example of this is confusion between the takeoff/go-around button and the autothrust disengagement button when transitioning between aircraft types with differing designs and locations for these controls. (4) Positioning of Controls and Related Indications. Individual FGS controls, flight mode annunciator (FMA), and related PFD information should be positioned so that, as much as reasonably practical, items of related function have similarly related positions.

Misinterpretation and confusion have occurred due to the inconsistent arrangement of FGS controls with the annunciations on the FMA. (5) Inadvertent Operation. The FGS controls must be located to discourage or avoid inadvertent operation, such as inadvertent engagement or disengagement. [See § 25.777(a)] Further design aspects of the FGS controls, other than location of the controls, should also be used discourage or avoid inadvertent operation. Examples include the shape of the control and the force required for operation. 44. FGS Mode selection, annunciation, and indication. a. Annunciation of Engagement of the FGS. Engagement of the FGS functions must be suitably annunciated to each pilot. [See § 25.1329(i)] Guidance is provided in Chapter 3, FGS Engagement, Disengagement, Indications, and Override. b. Description of FGS Modes. The operator should be provided with appropriate descriptions of the FGS modes and their behaviors. c. FGS Mode Annunciations. Mode annunciation must indicate the state of the system.

[See § 25.1329(i)] Mode annunciation should be presented in a manner compatible with flightcrew procedures/tasks and be consistent with the mode annunciation design for the specific aircraft type. That is, the mode annunciation should be compatible with other flight deck systems mode annunciations. Mode selector switch position or status is not acceptable as the sole means of mode annunciation. [See § 25.1329(i)] Modes and mode changes should be depicted in a manner that achieves flightcrew attention and awareness. (1) Active and Armed Modes. The FGS mode annunciations must effectively and unambiguously indicate the active and armed modes of operation. [See § 25.1329(i)]

Change 1 The mode annunciation should convey explicitly, and as simply as possible, what the FGS is doing (for active modes), what it will be doing (for armed modes), and target information (such as selected speed, heading, and altitude) for satisfactory flightcrew awareness. (2) Location. Mode annunciations should be located in the forward field of view. For example, a suitable location is on the PFD. Engaged modes should be annunciated at different locations than armed modes to assist in mode recognition. (3) Discriminators. Color, font type, font size, location, highlighting, and symbol flashing have historical precedent as good discriminators, when implemented appropriately. The fonts and font size should be chosen so that annunciation of FGS mode and status information is readable and understandable without eyestrain when viewed by the pilot seated at the design eye position. The use of graphical or symbolic (that is, non-textual) indications is acceptable.

Implementation of such discriminators should follow accepted guidelines, as described in applicable international standards (such as AC 25-11A, Transport Category Airplane Electronic Display Systems), and should be evaluated for their consistency with and integration with the flight deck design. (4) Color. Color should be used in a consistent manner and assure compatibility with the overall use of color on the flight deck. Specific colors should be used such that the FGS displays are consistent with other flight deck systems, such as a flight management system (FMS). The use of monochrome displays is not precluded, provided that the aspects of flightcrew attention and awareness are satisfied. Engaged modes should be annunciated with different colors than armed modes to assist in mode recognition. d. Mode Changes. (1) Operationally Relevant Mode Changes. Mode changes that are operationally relevant—especially mode reversions and sustained speed protection— should be clearly and positively annunciated to ensure flightcrew awareness.

Altitude Capture is an example of an operationally relevant mode that should be annunciated, because pilot actions during that brief time the mode is operational may have different effects on the airplane. Annunciation of sustained speed protection should be clear and distinct to ensure flightcrew awareness. The FGS sub–modes that are not operationally relevant (for example, sub-modes as the FGS transitions from instrument landing system Localizer (LOC) Capture to Localizer Track) need not be annunciated. (2) Attention-Getting Features. The transition from an armed mode to an engaged mode should provide an additional attention–getting feature, such as boxing and flashing on an electronic display (see AC 25-11A) for a suitable, but brief, period (for example, ten seconds) to assist in flightcrew awareness. Aural notification of mode changes should be limited to special considerations.

(3) Use Of Alerts. In–service experience has shown that mode annunciation alone may be insufficient—unclear or not compelling enough—to communicate mode changes to the flightcrew, especially in high workload situations. Therefore, the safety consequences of the flightcrew not recognizing mode changes should be considered. If necessary, an appropriate alert should be used. e. Failure to Engage or Arm. The failure of a mode to engage or arm when selected by the pilot should be apparent. f. FGS Mode Display and Indications. Mode information provided to the flightcrew should be sufficiently detailed, so that the consequences of the interaction between the FGS and the flightcrew can be determined unambiguously. The FGS interface should provide timely and positive indication when the FGS deviates from the pilot's direct commands (for example, a target altitude or speed setting) or from the pilot's pre-programmed set of commands (for example, waypoint crossing). The interface should also provide clear indication when there is a difference or conflict between pilot-initiated commands.

An example would be when a pilot engages positive vertical speed and then selects an altitude that is lower than the aircraft altitude. The default action taken by the FGS should be made apparent. 45. FGS Alerting, warning, caution, advisory, and status. a. General. (1) Alerting Provisions. Alerting information must follow the provisions of § 25.1322. The advisory material associated with § 25.1322 should be consulted. Alerts for FGS engagement and disengagement are described in Chapter 3, FGS Engagement, Disengagement, Indications, and Override. (2) Determination of FGS Capability. There should be some method for the flightcrew to determine and monitor the availability or capability of the FGS (for example, prior to dispatch), where the intended operation is predicated on the use of the FGS. The method of monitoring provided should take account of the hazard resulting from the loss of the autopilot function for the intended operation. b. Speed Protection Alerts. (1) Alerts to Crew.

To assure crew awareness, an alert should be provided when a sustained speed protection condition is detected. This is in addition to any annunciations associated with mode reversions that occur as a consequence of invoking speed protection (See Chapter 5, Performance of Function, paragraph 57, Speed Protection).

(2) Alert Specifications. (a) Low Speed Protection. Low speed protection alerts should include both an aural and a visual component. (b) High Speed Protection. High-speed protection alerts need include only a visual alert component because of existing high–speed aural alert requirements. However, giving an alert prior to that required aural alert is not precluded. [Refer to § 25.1303(c)(1) for overspeed alerting regulations. (3) Consistency. Alerts for speed protection should be consistent with the protection provided and with the other alerts in the flight deck. (4) Nuisance Alerts. Care should be taken to set appropriate values for indicating speed protection that would not be considered a nuisance for the flightcrew. c. Loss of Autopilot Approach Mode. The loss of the Approach mode requires immediate flightcrew awareness. This may be accomplished through autopilot disengagement described in AC 120-28D, Criteria for Approval of Category III Weather Minima for Takeoff, Landing, and Rollout.

If the autopilot remains engaged and reverts to a non-approach mode, an appropriate aural warning and/or visual alert should be provided. d. Awareness of Potential Significant Transient Condition (“Bark Before Bite”). (1) General. There have been situations where an autopilot was engaged, operating normally and controlling up to the limit of its authority for an extended period of time, and the flightcrew was unaware of the potential hazard. This service experience has shown that, without timely flightcrew awareness and action, such a situation can progress to a loss of control after autopilot disengagement, particularly in rare normal or non-normal conditions. However, with adequate flightcrew awareness and pilot action, loss of control may be prevented. (2) Flightcrew Alert(s).

To help ensure flightcrew awareness and timely action, appropriate alert(s)—normally a caution or warning—should be provided to the flightcrew for conditions that could require exceptional piloting skill or alertness for manual control following autopilot disengagement (for example, significantly out of trim conditions). The number and type of alerts required should be determined by the unique situations that are being detected and by the crew procedures required to address those situations. Any alert should be clear and unambiguous and should be consistent and compatible with other flight deck alerts. Care should be taken to set appropriate thresholds for these alerts so that they are not considered a nuisance for the flightcrew.

(3) Situations to Consider for an Alert. (a) Sustained Lateral Control Command. If the autopilot is holding a sustained lateral control command, it could be indicative of an unusual operating condition for which the autopilot is compensating. Examples of such unusual operating conditions are asymmetric lift and/or drag due to asymmetric icing, fuel imbalance, or asymmetric thrust. In the worst case, the autopilot may be operating at or near its full authority in one direction. If the autopilot were to disengage while holding this lateral trim, the result would be that the airplane could undergo a rolling moment that could possibly take the pilot by surprise. Therefore, a timely alert should be considered to permit the crew to manually disengage the autopilot and take control prior to any automatic disengagement that might result from the condition. (b) Sustained Pitch Command. If the autopilot is holding sustained pitch command, it could be indicative of an unusual operating condition (for example, inoperative automatic horizontal trim) for which the autopilot is compensating.

If the autopilot were to disengage while holding this pitch command, the result would be that the airplane could undergo an abrupt change in pitch that could possibly take the pilot by surprise. Therefore, a timely alert should be considered to permit the crew to manually disengage the autopilot and take control prior to any automatic disengagement that might result from the condition. (c) Bank and Pitch Angles. Most autopilots are designed with operational limits in both the pitch and roll axes, such that those predetermined limits will not be purposely exceeded. If the airplane exceeds those limits, it could be indicative of a situation that requires the pilot to intervene. Such a situation may not be covered by paragraphs (a) or (b) above. Therefore, a timely alert should bring this condition to the attention of the flightcrew and permit the crew to manually disengage the autopilot and take control prior to any automatic disengagement which might result. (4) Automatic Disengagement. It is preferable that the autopilot remains engaged during out–of–trim conditions.

However, if there is an automatic disengagement feature due to excessive out–of–trim, an alert should be generated and should precede any automatic disengagement with sufficient margin to permit timely flightcrew recognition and manual disengagement. See also Chapter 3, FGS Engagement, Disengagement, Indications, and Override, paragraph 30, Override of the FGS, for related material.

Note 1: This paragraph is not intended to require alerting for all instances of automatic autopilot disengagement. It is intended only for conditions that would, if not addressed, lead to disengagement that could result in a significant transient (or greater) for which the pilot may be unprepared. The intent is to provide crew awareness that would allow the flightcrew to be prepared with hands on controls and take appropriate corrective action before the condition results in a potentially hazardous airplane configuration or state.

Note 2: This paragraph describes alerting requirements for conditions resulting in unintended out–of–trim operation. There are FGS functions that can intentionally produce out-of-trim conditions. Examples would be parallel rudder operation in align or engine failure compensation modes, pitch trim operation during the approach/landing to provide trim up/flare spring bias, and pitch trim operation for certain types of speed/Mach trim systems. It is not the intent of this paragraph to require alerts for functions producing intentional out–of–trim conditions. Other system indications (for example, mode and status annunciations) should be provided to make the crew aware of the operation of these functions, where appropriate. 46. FGS Considerations for head up displays (HUD). a. General. HUDs have unique characteristics compared to flight displays installed on the instrument panel. Most of these HUD differences are addressed during HUD certification whether or not the HUD provides flight guidance functions.

The intent of this chapter is to address how such HUD differences may affect FGS functions. (See SAE ARP5288, Transport Category Airplane Head Up Display Systems, for further information on this subject. An address for obtaining SAE ARP documents is provided in paragraph 4 of this AC.) b. Characteristics of HUD Guidance. (1) Supplemental Use Display System. If the HUD is designed as a supplemental use display system, it does not replace the requirement for standard head down display (HDD) of flight instrument data. The HUD is intended for use during takeoff, climb, cruise, descent, approach, and landing under day, night, visual meteorological conditions (VMC), and instrument meteorological conditions (IMC) conditions. When it can be reasonably expected that the pilot will operate primarily by reference to the HUD, it should be shown that the HUD is satisfactory for manually controlling the airplane and for monitoring the performance of the FGS. (2) External Visual References.

During takeoff and landing in certain light and visibility conditions, HUD symbology can be extremely dominant in comparison to external visual references. When visual references are relatively dim, extremely active symbology dynamics and guidance cue gains can lead the pilot to make excessively strong corrections. It should be shown that—if HUD guidance cues are followed regardless of the appearance of external visual references—they do not cause the pilot to take unsafe actions. (3) Interference and Occlusion. It should be shown that there is no interference between the indications of primary flight information and the flight guidance cues. In takeoff, approach, and landing FGS modes, the flight guidance symbology should have occlusion priority. That is, the flight guidance symbology should not be obscured or covered by the primary flight information. The HUD guidance symbology should not

excessively interfere with pilots’ forward view, ability to visually maneuver the airplane, acquire opposing traffic, and see the runway environment. (4) Display Criteria. Generally, the criteria for the mechanization of guidance displayed on the HUD should be no different than for guidance displayed on the HDD. See Chapter 5, Performance of Function, for FD performance criteria. (5) Conformal Symbology. Unlike HDDs, HUDs are capable of displaying certain symbology conformal to the outside scene, including guidance cues. Consequently, the range of motion of this conformal symbology, including the guidance cues, can present certain challenges in rapidly changing and high crosswind conditions. In certain cases, the motion of the guidance and the primary reference cue may be limited by the field of view. It should be shown that, in such cases, the guidance remains usable and that there is a positive indication that it is no longer conformal with the outside scene. (6) Low Visibility Approach.

The HUD guidance is often used in cases, like the low visibility approach, where the pilot will need to reference both the information displayed on the HUD and outside references. Consequently, it should be shown that the location and presentation of the HUD information does not distract the pilot or obscure the pilot’s outside view. For example, it would be necessary for the pilot to track the guidance to the runway without having the view of runway references or hazards along the flight path obscured by the HUD symbology. (7) Clutter. The HUD display should present flight guidance information in a clear and unambiguous manner. Display clutter should be minimized. Some flight guidance data elements are essential or critical and should not be removed by any declutter function. c. HUD/Head Down Display (HDD) Compatibility. (1) General. The HUD FGS symbology should be compatible and consistent with symbology on other FGS displays such as head down electronic flight instruments.

The FGS-related display parameters should be consistent to avoid misinterpretation of similar information, but the display presentations need not be identical. The HUD and head down PFD formats and data sources need to be compatible to ensure that the same FGS-related information presented on both displays have the same intended meaning. (2) Consistency and Compatibility. While not all information displayed on the HUD is directly related to the FGS, the pilot is likely to use most of the displayed information while using the HUD-displayed guidance and FGS annunciations. Therefore, when applicable, the guidelines below for the presentation of FGS-related display information should be followed as much as possible. Certain deviations from these guidelines may be appropriate due to conflict with other information display characteristics or requirements unique to HUDs. These may include minimization of display clutter, minimization of excessive symbol flashing, and the presentation of certain information conformal to the outside scene.

(a) Symbology. Symbols should be the same format. For example, a triangle-shaped pointer head down should appear as a triangle pointer head up. However, some differences in HUD symbology, such as the FD “circle” versus head down FD “bars” or “wedge,” have been found acceptable. (b) Location. Information (symbols) should appear in the same general location relative to other information. (c) Alphanumeric Data. Alphanumeric readouts should have the same resolution, units, and labeling. For example, the command reference indication for “vertical speed” should be displayed in the same foot-per-minute increments and be labeled with the same characters as the HDDs. (d) Analog Scales. Analog scales or dials should have the same range and dynamic operation. For example, a glideslope deviation scale displayed head up should have the same displayed range as the glideslope deviation scale displayed head down, and the direction of movement should be consistent. (e) Display of FGS Modes.

The FGS modes and status state transitions should be displayed on the HUD using consistent methods, except for the use of color. That is, the method used head down to indicate a FD mode transitioning from armed to captured should also be used head up. (f) Information Sources. Information sources should be consistent between the HUDs and the HDDs used by the same pilot. (g) Display of FGS Command Information. When FGS command information (for example, a FD command) is displayed on the HUD in addition to the HDDs, the HUD depiction and guidance cue deviation “scaling” needs to be consistent with that used on the HDDs. This is intended to provide comparable pilot performance and workload when using either HUDs or HDDs. (h) Display for Pilot Not Flying. The same information concerning current HUD system mode, reference data, status state transitions, and alert information that is displayed to the pilot flying on the HUD should also be displayed to the pilot not flying on the HDDs. Consistent nomenclature should be used to ensure unambiguous awareness of the HUD operation. d.

Alerting Issues. (1) Alerts Displayed on HUDs. Although HUDs are typically not intended to be classified as integrated caution and warning systems, they may display cautions, warnings, and advisories as part of their FGS function. In this regard, HUDs should provide the equivalent alerting functionality as the head down PFD(s). Warnings that require continued flightcrew attention on the PFD also should be presented on the HUD

Change 1 (for example, TCAS, windshear, and ground proximity warning (GPWS) annunciations). If master alerting indications are not provided within the peripheral field of view of the pilot while using the HUD, the HUD should provide annunciations that inform the pilot of caution and/or warning conditions. (2) Monochrome HUDs. For monochrome HUDs, appropriate use of attentiongetting properties, such as flashing, outline boxes, brightness, size, and/or location are necessary to adequately compensate for the lack of color normally assigned to distinguish and call attention to cautions and warnings. (3) Multi–Color HUDs. For multi-color HUDs, the use of red, amber, or yellow for symbols not related to caution and warning functions should be avoided, so that the effectiveness of distinguishing characteristics of true cautions and warnings is not reduced. (4) Single HUD Installation. Single HUD installations rely on the fact that the pilot not flying (PNF) will monitor the head down instruments and alerting systems for failures of systems, modes, and functions not associated with PFDs.

(5) Dual HUD Installations. Dual HUD installations require special consideration for alerting systems. It should be assumed that both pilots will be head up simultaneously (full or part-time), especially when the HUD is being used as the primary flight reference or when the HUD is required equipment for the operation being conducted. If master alerting indications are not provided within the peripheral field of view of each pilot while using the HUD, then each HUD should provide annunciations that direct the pilot’s attention to head down alerting displays. The types of information that should trigger the HUD master alerting display are any cautions or warnings not already duplicated on the HUD from head down primary display as well as any caution level or warning level engine indications or system alerts.

Note: The objective is to avoid redirecting attention of the pilot flying (PF) to another display when an immediate maneuver is required (for example, TCAS resolution advisory, windshear). (6) Ground Proximity Warning System (GPWS)/Traffic Alert and Collision Avoidance System (TCAS) on HUD. If a GPWS, wind shear detection system, wind shear escape guidance system, or a TCAS is installed, then the guidance, warnings and annunciations required to be a part of these systems and normally required to be in the pilot’s primary field of view should be displayed on the HUD. e. Upset/Unusual Attitude Recovery Guidance. (1) Guidance Cues. Upsets due to wake turbulence or other environmental conditions may result in near instantaneous excursions in pitch and bank angles and a subsequent unusual attitude. If the HUD is designed to provide guidance for recovery from upsets or unusual attitudes, recovery steering guidance commands should be distinct

from and not confused with orientation symbology such as horizon “pointers.” For example, a cue for left control wheel/stick input should not be confused with a cue indicating direction to the nearest horizon. Guidance should be removed if cues become invalid at extreme attitudes, such as zenith, nadir, overbanked (for example, greater than 90 degrees bank angle), or inverted. For extreme attitudes, it is acceptable for the pilot to transition to the HDD, provided that the cues to transition from the HUD are clear and unambiguous. (2) Orientation Cues. If the HUD is designed to provide only orientation during upsets or unusual attitudes (that is, no guidance cues are provided), those orientation cues should be designed to prevent them from being mistaken as flight control input commands. 47 — 51 [Reserved]

This page left blank.

Chapter 5 Performance of Function 52. General.. a. Intended Function. The FGS should provide guidance or control, as appropriate, for the intended function of the active mode(s) in a safe and predictable manner within the airplane’s normal flight envelope. There are special considerations when the FGS is operating at the limits of its performance capabilities or under significant environmental conditions. The following paragraphs provide criteria for acceptable means of compliance and interpretive material pertaining to these considerations. b. Effect of System Tolerances. Where system tolerances have a significant effect on autopilot authority limits, consideration should be given to the effect on autopilot performance. Factors to be considered include, but are not limited to, tolerances of servo authority, servo clutch setting, “cam-out” settings, control friction, and sensor tolerances. 53. Nornal performance. a. General.

The FGS should be designed to provide guidance or control, as appropriate, for the intended function of the active mode(s) in a safe and predictable manner within the airplane’s normal flight envelope. b. Conditions to Consider. The design of the FGS should consider the normal conditions listed in the following table. This table does not fully define every condition that may be encountered during an airplane’s life and unequivocally categorize what can be considered to be a “normal condition. Rather, the table is intended to give examples to be used during system development and testing. By the very nature of the phenomena involved, there will always be some subjectivity to these categorizations. Also, the same conditions may affect different airplane models in very different ways. These differences should be considered in determining how to characterize the severity of the conditions discussed in the table.

Table 5-1 Examples of Normal Conditions

No failure conditions All airplane systems that are associated with airplane performance are fully operational. Failures of those systems could impair the flight guidance system's (FGS) ability to perform its functions.

Light to moderate winds

Constant wind in a specific direction that may cause a slight deviation in intended flight path or a small difference between airspeed and groundspeed.

Light to moderate wind gradients

Variation in wind velocity—as a function of altitude, position, or time—which may cause slight erratic or unpredictable changes in intended flight path.

Light to moderate gusts

Non–repetitive momentary changes in wind velocity that can cause changes in altitude and/or attitude to occur, but the aircraft remains in positive control at all times.

Light turbulence Turbulence that momentarily causes slight, erratic changes in altitude and/or attitude (pitch, roll, or yaw).

Moderate turbulence Similar to light turbulence but of greater intensity. Changes in altitude and/or attitude occur, but the aircraft remains in positive control at all times.

Light chop Turbulence that causes slight, rapid, and somewhat rhythmic bumpiness without appreciable changes in altitude or attitude.

Moderate chop Similar to light chop but of greater intensity. It causes rapid bumps or jolts without appreciable changes in aircraft altitude or attitude.

Icing All icing conditions covered by 14 CFR Part 25, Appendix C with the exception of “asymmetric icing” discussed under “Rare Normal Conditions” in Table 5-2.

Note: Representative levels of the environmental effects should be established consistent with the airplane’s intended operation.

10/16/12 AC 25.1329-1B Change 1

c. Level of Performance. (1) Significant Characteristics. Any performance characteristics that are operationally significant or operationally limiting must be identified with an appropriate statement or limitation in the airplane flight manual (AFM). [See § 25.1581] (2) Configuration Changes. The FGS should perform its intended function during routine airplane configuration or power changes, including the operation of secondary flight controls and landing gear. (3) Compliance Evaluation. Evaluation of FGS performance for compliance should be based on the minimum level of performance needed for its intended functions. Subjective judgment may be applied to account for experience acquired from similar equipment and levels that have been established as operationally acceptable by the end-user. (4) Prescribed Levels of Performance. There are certain operations that dictate a prescribed level of performance.

When the FGS is intended for operations that require specific levels of performance, the use of FGS should be shown to meet those specific levels of performance (for example, low visibility operations – Category II and III operations, reduced vertical separation minimums (RVSM), required navigation performance (RNP)). (5) Equivalence of Performance. The FGS performance of intended functions should at least be equivalent to that expected of a pilot for a similar task. AC 25-7C, Flight Test Guide for Certification of Transport Category Airplanes, and the SAE ARP5366, Autopilot, Flight Director and Autothrust Systems, may prove useful for establishing the general behavior of the FGS. When integrated with navigation (NAV) sensors or the FMS, the FGS should satisfy the flight technical error tolerances expected for the use of those systems in performing their intended functions. (6) Autopilot. The autopilot should provide smooth and accurate control without divergent or perceptible sustained nuisance oscillation. (7) Flight Director (FD).

The FD, in each available display presentation (for example, single cue, cross–pointer, flight path director) should provide smooth and accurate guidance and be appropriately damped, to achieve satisfactory control task performance without pilot compensation or excessive workload. (8) Autothrust. The autothrust function should provide smooth and accurate control of thrust without significant or sustained oscillatory power changes or excessive overshoot of the required power setting. (9) Automatic Trim. The automatic pitch trim function should operate at a rate sufficient to mitigate excessive control surface deflections or limitations of control

authority without introducing adverse interactions with automatic control of the aircraft. Automatic roll and yaw trim functions, if installed, should operate without introducing adverse interactions with automatic control of the aircraft. 54. Performance in rare normal conditions. a. General. (1) Range of Conditions. The FGS will encounter a wide range of conditions in normal operations, some of which may be infrequent but levy a greater than average demand on the FGS capabilities. Certain environmental conditions, as discussed in paragraph b, below, are prime examples. The FGS performance during such rare normal conditions should be assessed. (2) Effect on Performance. Rare normal conditions may degrade the performance of the FGS but should be safe for operation of the FGS. The relative infrequency of such conditions may also be a factor in the flightcrew’s ability to detect and mitigate in a timely manner any limited capability of the FGS to cope with them. b. Conditions to Consider. The design of the FGS should consider the rare normal conditions listed in the following table.

This table does not fully define every condition that may be encountered during an airplane’s life and unequivocally categorize what can be considered to be a “rare normal condition. Rather, the table is intended to give examples to be used during system development and testing. By the very nature of the phenomena involved, there will always be some subjectivity to these categorizations. Also, the same conditions may affect different airplane models in very different ways. These differences should be considered in determining how to characterize the severity of the conditions discussed in the table.

Table 5-2 Examples of Rare Normal Conditions Significant winds Constant wind in a specific direction that may cause a large change in intended flight path or groundspeed or cause a large difference between airspeed and groundspeed. Significant wind gradients

Variation in wind velocity—as a function of altitude, position, or time—which may cause large changes in intended flight path. Windshear/microburst A wind gradient of such magnitude that it may cause damage to the aircraft. Large gusts Non-repetitive momentary changes in wind velocity that can cause large changes in altitude and/or attitude to occur. Aircraft may be momentarily out of control. Severe turbulence Turbulence that causes large, abrupt changes in altitude or attitude. It usually causes large variations in indicated airspeed. Aircraft may be momentarily out of control. Asymmetric icing Icing conditions that result in ice accumulations that causes the FGS, if engaged, to counter the aerodynamic effect of the icing conditions with a sustained pitch, roll, or yaw command that approaches its maximum authority.

Note: Airplanes intended to meet § 121.358 for windshear warning and guidance need FD windshear guidance. The FGS may also provide suitable autopilot control during windshear. Refer to AC 25-12 and AC 120-41 for wind shear guidance system requirements.

c. Level of Performance. (1) Performance Standard. For rare normal conditions, the FGS should be designed to provide guidance or control, as appropriate, for the intended function of the active mode(s) in a safe and predictable manner, both within the normal flight envelope and for momentary excursions outside the normal flight envelope. If a determination is made that there are environmental conditions in which the FGS cannot be safely operated, appropriate operational limitations should be placed in the AFM. (2) Autopilot Authority Limit. Operations in rare normal conditions may result in automatic or pilot-initiated autopilot disengagement close to the limit of autopilot authority.

Autopilot disengagement in rare normal conditions should meet the safety criteria for autopilot disengagement found in Chapter 3, FGS Engagement, Disengagement, Indications, and Override, paragraph 27b, Autopilot Disengagement, and the criteria for flight guidance alerting in Chapter 4, Controls, Indications, and Alerts, paragraph 45d, Awareness of Potential Significant Transient Condition (“Bark Before Bite”). (3) Masking of Potential Hazard. It is not necessary that the FGS always be disengaged when rare normal conditions that may degrade its performance or capability are encountered. The FGS may significantly help the flightcrew during such conditions. However, the design should address the potential for the FGS to mask a condition from the flightcrew or otherwise delay appropriate flightcrew action. See Chapter 4, paragraph 45, FGS Alerting, Warning, Caution, Advisory, and Status, for discussion of alerting under such conditions. 55. Icing coniseration in normal and rare normal conditions. a. Effect on Performance.

The FGS typically will be designed to provide acceptable performance in all standard airplane configurations. Operating an airplane in icing conditions can have significant implications on the aerodynamic characteristics of the airplane (for example, ice accretion on wings, tail, and engines) and, consequently, on FGS performance. Ice accretion may be slow, rapid, symmetric, or asymmetric. During autopilot operation, the flightcrew may not be aware of the gradual onset of icing conditions or the effect that the accumulation of ice is having on the handling qualities of the airplane. b. Alerts. Means should be provided to alert the flightcrew when icing conditions begin to have an effect upon FGS performance, as described in Chapter 4, paragraph 45.

c. Effect On Speed Protection. The implication of icing conditions on speed protection should be assessed. If the threshold of the stall warning system is adjusted due to icing conditions, appropriate adjustments should also be made to the FGS low speed protection threshold, which is discussed in paragraph 57b, Low Speed Protection, of this chapter. 56. Performance in non-normal conditions. a. General. The FGS will occasionally be operating when the airplane transitions outside of its normal flight envelope, due to failures or non-standard ferry configurations. Under such circumstances, the FGS characteristics and flightcrew interaction with the FGS should be shown to be safe. b. Conditions to Consider. The following table shows examples of non–normal conditions. The table does not fully define every condition that may be encountered during an airplane’s life and unequivocally categorize what can be considered to be a “non–normal condition.” Rather, the table is intended to give examples to be used during system development and testing. By the very nature of the phenomena involved, there will always be some subjectivity to these categorizations. Also, the same conditions may affect different airplane models in very different ways. These differences should be considered in determining how to characterize the severity of the conditions discussed in the following table.

Table 5-3 Examples of Non-Normal Conditions Significant fuel imbalance

Large variation of the amount of fuel between the two wing tanks (and center and tail tanks, if so equipped) that causes the FGS, if engaged, to counter the aerodynamic effect of the fuel imbalance with a pitch, roll, or yaw command that is approaching maximum system authority. Non-standard ferry flight configurations

Possible aerodynamic drag (both symmetrical and unsymmetrical) caused by non-standard airplane ferry flight conditions such as locked high lift devices, landing gear locked in the deployed position, or an extra engine carried underneath one wing in an inoperative position. Inoperative engine(s) Loss of one or more engines that causes the FGS, if engaged, to counter the aerodynamic effect of the difference in thrust with a pitch, roll, or yaw command that is approaching maximum system authority. Loss of one or more hydraulic systems

Loss of one or more hydraulic systems down to the minimum amount of remaining operational systems which the FGS is certified to operate. Inoperative Ice Detection/ Protection System

Loss of ice detection/protection system on an airplane so equipped where the FGS is certified for operation in icing conditions with that failure present.

c. Level of Performance. (1) Performance Standard. For non- normal conditions, the FGS should be designed to provide guidance or control, as appropriate, for the intended function of the active mode(s) in a safe and predictable manner, both within the normal flight envelope and for momentary excursions outside the normal flight envelope. If a determination is made that there are non-normal conditions in which the FGS cannot be safely operated, appropriate operational limitations should be placed in the AFM. (2) Autopilot Authority Limit. Operations in non-normal conditions may result in automatic or pilot-initiated autopilot disengagement close to the limit of autopilot authority.

Autopilot disengagement in non-normal conditions should meet the safety criteria for autopilot disengagement found in Chapter 3, FGS Engagement, Disengagement, Indications, and Override, paragraph 27b, Autopilot Disengagement, and the criteria for flight guidance alerting in Chapter 4, Controls, Indications, and Alerts, paragraph 45d, Awareness of Potential Significant Transient Condition (“Bark Before Bite”). (3) Masking of Potential Hazard. It is not necessary that the FGS always be disengaged when non-normal conditions that may degrade its performance or capability are encountered. The FGS may significantly help the flightcrew during such conditions. However, the design should address the potential for the FGS to mask a condition from the flightcrew or otherwise delay appropriate flightcrew action. See Chapter 4, paragraph 45, FGS Alerting, Warning, Caution, Advisory, and Status, for discussion of alerting under such conditions. 57. Speed protection. a. General. (1) Speed Excursions.

The requirement for speed protection is based on the premise that reliance on flightcrew attentiveness to airspeed indications alone during FGS operation is not adequate to avoid unacceptable speed excursions outside the speed range of the normal flight envelope. Many existing FGS systems have no provisions to avoid speed excursions outside the normal flight envelope. Some FGSs will remain engaged until the aircraft slows to stall conditions and also to speeds well above maximum operating limit speed/maximum operating limit Mach (VMO/MMO). (2) Compliance with § 25.1329(h). Standard stall warning and high-speed alerts are not always timely enough for the flightcrew to intervene to prevent unacceptable speed excursions during FGS operation. The intent of § 25.1329(h) is for the FGS to provide a speed protection function for all operating modes, so that the airspeed can be safely maintained within an acceptable margin of the speed range of the normal flight envelope. The FGS design may use any of the following ways or a combination of ways to provide acceptable speed protection:

(a) The FGS Provides Speed Protection. In this case, the following are acceptable means to comply with this rule: 1 The FGS may detect the speed protection condition, alert the flightcrew, and provide speed protection control or guidance. 2 The FGS may detect the speed protection condition, alert the flightcrew, and then disengage the FGS. 3 The FGS may detect the speed protection condition, alert the flightcrew, and remain engaged in the active mode without providing speed protection control or guidance. (b) Other Systems Provide Speed Protection. Other systems, such as the primary flight control system or the FMS (when in a vertical navigation (VNAV) mode) may be used to provide equivalent speed protection.

Note: If compliance with this requirement is based on use of alerting alone, the alerts should be shown to be appropriate and timely to ensure flightcrew awareness and enable the pilot to keep the airplane within an acceptable margin from the speed range of the normal flight envelope. See Chapter 4, Controls, Indications, and Alerts, paragraph 45b, Speed Protection Alerts, for additional discussion of speed protection alerting. (3) Design Standard. (a) Interaction of FGS Elements. The design should consider how and when the speed protection is provided for combinations of autopilot, FDs, and autothrust operation. Care should be taken to set appropriate values for transitioning into and out of speed protection such that the flightcrew does not consider the transitions a nuisance. (b) Integration of Pitch and Thrust Control. The speed protection function should integrate pitch and thrust control. Consideration should be given to automatically activating the autothrust function when speed protection is invoked. If an autothrust function is either not provided or is unavailable, speed protection should be provided through pitch control alone. (c) Interaction of Systems. The role and interaction of autothrust with elements of the FMS, the primary flight control system, and the propulsion system, as applicable, should be accounted for in the design for speed protection. (d) Engine Inoperative. Consideration should be given to the effects of an engine inoperative condition on the performance of speed protection.

10/16/12 AC 25.1329-1B Change 1

b. Low Speed Protection. (1) General. When the FGS is engaged in any modes (with the possible exception of Approach, as discussed in paragraph (3) below) for which the available thrust is insufficient to maintain a safe operating speed, the low speed protection function should be invoked to avoid unsafe speed excursions. (2) Factors to Consider. Activation of speed protection should take into account such factors as the phase of flight, turbulence and gusty wind conditions, and compatibility with the speed schedules. The low speed protection function should activate at a suitable margin to stall warning that will not result in nuisance alerts. Consider the operational speeds, as specified in the AFM, for all-engine and engine-inoperative cases during the following phases of flight: (a) Takeoff. (b) Departure, climb, cruise, descent, and terminal area operations. During these flight phases, airplanes are normally operated at or above the minimum maneuvering speed for the given flap configuration.

Note: For high altitude operations, it may be desirable to incorporate low speed protection at the appropriate engine out drift–down speed schedule, if the FGS (or other integrated sensors/systems) can determine that the thrust deficiency is due to an engine failure. (c) Approach. (d) Transition from approach to go–around and go–around climb.

Note: A low speed alert and a transition to the Speed Protection mode at approximately 1.13 VSR (reference stall speed) for the landing flap configuration has been found to be acceptable. (3) Low Speed Protection During Approach Operations. (a) Non–Interference. Speed protection should not interfere with the approach and landing phases of flight. (b) Autothrust Operation. It is assumed that with autothrust operating normally, the combination of thrust control and pitch control during the approach will be sufficient to maintain speed and desired vertical flight path. In cases where it is not sufficient, an alert should be provided in time for the flightcrew to take appropriate corrective action. (c) Defined Vertical Path. For approach operations with a defined vertical path (for example, ILS, microwave landing system (MLS), GBAS landing system (GLS),

Lateral Navigation (LNAV) mode, VNAV mode), if the thrust is insufficient to maintain both the desired flight path and the desired approach speed, there are several ways to meet the intent of low speed protection: 1 The FGS may maintain the defined vertical path as the airplane decelerates below the desired approach speed until the airspeed reaches the low speed protection value. At that time, the FGS would provide guidance to maintain the low speed protection value as the airplane departs the defined vertical path. The FGS mode reversion and low speed alert should be activated to ensure pilot awareness.

Note: The pilot is expected to take corrective action to add thrust and return the airplane to the defined vertical path or go–around, as necessary. 2 The FGS may maintain the defined vertical path as the airplane decelerates below the desired approach speed to the low speed protection value. The FGS will then provide a low speed alert while remaining in the existing FGS approach mode.

Continue reading ↓ 120 of 272 passages shown