Radar Vectors
Advisory Circular Cancelled Issued Dec 6, 2016 AIR-130 104 pages Copy saved Nov 17, 2026

AC 20-167A Airworthiness Approval of Enhanced Vision System, Synthetic Vision System, Combined Vision System, and Enhanced Flight Vision System Equipment

This advisory circular (AC) provides guidance for gaining airworthiness approval for enhanced and synthetic vision systems in aircraft. Specifically, it provides one acceptable means for complying with Title 14 of the Code of Federal Regulations (14 CFR) part 23, 25, 27, or 29 airworthiness regulations when installing a synthetic vision system (SVS), enhanced vision system (EVS), combined vision system (CVS), or enhanced flight vision system (EFVS) in an airplane or rotorcraft. Since the release of Draft AC 20-167A for public comment, the FAA revised the standard format for Advisory Circulars. AC 20-167A is formatted in compliance with the new standard format, meaning the numbering of paragraphs changed from the draft that was presented for public comment. The preamble accompanying the 2016 EFVS rule specifically references paragraphs 4-5, 4-5.c.4, 4-5.c.4.(h).(iv), and 6-2.f.4. These referenced paragraphs equate to paragraphs 4.5, 4.5.3.4, 4.5.3.4.8.4, 6.2.6.4, respectively.

This document is cancelled. Cancelled by 20-167B. Check the official source before relying on it.

Official source ↗ Open PDF

U.S. Department of Transportation Federal Aviation Administration

Advisory Circular

Subject: Airworthiness Approval of Enhanced Vision System, Synthetic Vision System, Combined Vision System, and Enhanced Flight Vision System Equipment

Date: 12/6/16 Initiated by: AIR-130

AC No: 20-167A

This advisory circular (AC) provides guidance for gaining airworthiness approval for enhanced and synthetic vision systems in aircraft. Specifically, it provides one acceptable means for complying with Title 14 of the Code of Federal Regulations (14 CFR) part 23, 25, 27, or 29 airworthiness regulations when installing a synthetic vision system (SVS), enhanced vision system (EVS), combined vision system (CVS), or enhanced flight vision system (EFVS) in an airplane or rotorcraft.

Since the release of Draft AC 20-167A for public comment, the FAA revised the standard format for Advisory Circulars. AC 20-167A is formatted in compliance with the new standard format, meaning the numbering of paragraphs changed from the draft that was presented for public comment. The preamble accompanying the 2016 EFVS rule specifically references paragraphs 4-5, 4-5.c.4, 4-5.c.4.(h).(iv), and 6-2.f.4. These referenced paragraphs equate to paragraphs 4.5, 4.5.3.4, 4.5.3.4.8.4, 6.2.6.4, respectively.

If you have suggestions for improving this AC, you may use the Advisory Circular Feedback form at the end of this AC.

Richard E. Jennings Acting Manager, Design, Manufacturing, & Airworthiness Division Aircraft Certification Service

ii

Table of Contents Paragraph Page

Chapter 1. Introduction … 1-1

1.1 Purpose … 1-1

1.2 Audience … 1-1

1.3 Applicability … 1-1

1.4 How to Use This Document … 1-2

1.5 Definitions and acronyms are in Appendix I … 1-2

1.6 Cancellation … 1-2

Chapter 2. Vision Systems Overview … 2-1

2.1 Enhanced Vision Systems … 2-1

2.2 Synthetic Vision Systems … 2-2

2.3 Combined Vision Systems … 2-5

2.4 Enhanced Flight Vision Systems … 2-6

Chapter 3. Airworthiness Package Contents … 3-1

3.1 Airworthiness Package … 3-1

3.2 Intended Function … 3-1

Chapter 4. System Criteria … 4-1

4.1 EVS or SVS (or CVS when EVS and SVS combined) – General … 4-1

4.2 EVS Specific Criteria … 4-4

4.3 SVS Specific Criteria … 4-6

4.4 CVS Specific Criteria … 4-10

4.5 EFVS – General and Specific Criteria … 4-11

Chapter 5. Systems Installation Considerations … 5-1

5.1 EVS/SVS/CVS Installations Considerations … 5-1

5.2 EFVS Display (HUD or Equivalent) Installation Considerations … 5-3

5.3 HIRF Considerations for All Installations (EVS, SVS, CVS, and EFVS) … 5-9

Chapter 6. Performance Evaluation … 6-1

6.1 EVS/SVS/EFVS Performance Demonstration … 6-1

6.2 Performance Demonstration of EFVS Landing System … 6-2

6.3 Environmental Qualification and Design Assurance … 6-4

iii

Appendix A. FAA EFVS 14 CFR Compliance (Partial List) … A-1

A.1 Airworthiness Standards … A-1

A.2 EFVS Compliance … A-1

Appendix B. EFVS Approach System and EFVS Landing System Systems Safety GuidanceB-1

B.1 General … B-1

B.2 Required Level of Safety … B-1

B.3 Demonstration … B-2

B.4 State Data … B-2

Appendix C. EFVS Approach System and II Safety Standards … C-1

C.1 Safety factors for EFVS described in this AC … C-1

C.2 Features … C-1

C.3 Demonstration … C-2

C.4 In addition to the sensor imagery, at least the following specific aircraft flight

information must be displayed: … C-4

C.5 Head-Up Display … C-4

Appendix D. Sample EFVS Approach System Flight Test Considerations … D-1

D.1 General Flight Test Considerations … D-1

D.2 Minimum Flight Test Conditions Observed … D-1

D.3 Test Points … D-2

D.4 Evaluation During Taxi … D-3

D.5 Take off Evaluation … D-3

D.6 Climb and Descent and Lateral Modes Evaluation … D-3

D.7 Instrument Approaches … D-3

D.8 Flare Landing and Go Around … D-4

D.9 Copilot Monitor … D-4

D.10 Failure Cases … D-4

D.11 Ice Protection System Evaluation … D-4

D.12 Evaluation Matrix … D-5

Appendix E. Sample Flight Test Considerations for EFVS Landing System … E-1

E.1 General Flight Test Considerations … E-1

E.2 Minimum Flight Test Conditions Observed … E-1

E.3 Test Points … E-3

iv

E.4 Evaluation During Taxi … E-4

E.5 Take off Evaluation … E-4

E.6 Climb and Descent and Lateral Modes Evaluation … E-5

E.7 Instrument Approaches to the DA(H) … E-5

E.8 Final Approach from the DA/DH, Flare, Landing and Rollout to Safe Taxi Speed … E-5

E.9 Rejected Landing … E-5

E.10 Pilot Monitoring (PM) Display … E-5

E.11 Failure Cases … E-6

E.12 Ice Protection System Evaluation … E-6

E.13 Evaluation Matrix … E-6

Appendix F. Sample Airplane Flight Manual (AFM) Supplement … F-1

Appendix G. Installation of Enhanced Vision System and or/Synthetic Vision System on

Rotorcraft … G-1

G.1 General … G-1

G.2 Applicability … G-1

G.3 Airworthiness Approval … G-1

G.4 Design Considerations … G-1

Appendix H. Additional Part 23 Considerations for Enhanced Vision System/or Synthetic

Vision System for Situation Awareness Only … H-1

H.1 Introduction … H-1

H.2 Terrain Alerting … H-1

H.3 Moving Map Display that Corresponds to and Complements Synthetic Vision PFD

Display … H-2

H.4 Minimums Audio Callout Capability … H-2

H.5 Digital Evaluation Model (DEM) Resolution … H-2

H.6 Aircraft Flight Manual Supplement (AFMS) … H-3

H.7 SVS Unusual Attitude Recovery … H-3

H.8 Pilot Evaluation … H-4

Appendix I. Definitions and Acronyms … I-1

I.1 Definitions … I-1

I.2 Acronyms … I-5

Appendix J. Related Publications … J-1

v

J.1 Related Publications … J-1

J.2 How to Get Publications … J-3

Appendix K. Advisory Circular Feedback Information … K-1

List of Figures

Figure Page

Figure 1. Enhanced Vision Diagram … 2-1

Figure 2. Synthetic Vision Diagram … 2-3

Figure 3. Minimum Detection Range … 4-14

Figure 4. Field of View … I-3

List of Tables

Table Page

Table 1. EFVS Visibility and Visual Reference Requirements … 4-13

Table 2. System Operating Phases for Considerations … 5-2

Table 3. EFVS Acceptable Methods of Compliance … A-1

Table 4. Required Level of Safety, 14 CFR part 25 Aircraft … B-2

Table 5. Example EFVS/HUD Functional Hazard Assessment, 14 CFR part 25 Aircraft, ILS Approaches to 100 ft Height Above Touchdown, RVR 1200 ft … B-3

Table 6. EFVS Approach System Evaluation Matrix … D-5

Table 7. EFVS Landing System Evaluation Matrix … E-6

1.3 Applicability › 1.3.2 This AC does not address operational aspects of vision systems or…

CHAPTER 1. INTRODUCTION

1.1 Purpose

1.1.1 In this advisory circular (AC), the Federal Aviation Administration (FAA) provides guidance on airworthiness approvals of enhanced vision system (EVS), synthetic vision system (SVS), combined vision system (CVS), and enhanced flight vision system (EFVS) equipment installation. The FAA has attempted to use regulatory language that is performance based and not limited to a specific sensor technology. The FAA believes this action will accommodate future growth in sensor technologies used in vision systems.

1.1.2 Existing ACs address flight guidance symbology, head-up displays (HUD) and visual display characteristics (for example, AC 25-11B, Electronic Flight Deck Displays, AC 25.1329-1B, Approval of Flight Guidance Systems and AC 23.1311-1C Installation of Electronic Display in Part 23 Airplanes). For a complete listing of related regulations and guidance, refer to Appendix A and Appendix J. This AC complements existing guidance.

1.1.3 This AC is not mandatory and does not constitute a regulation. This AC describes an acceptable means, but not the only means, to install and obtain airworthiness approval for enhanced and synthetic vision technologies. However, if you use the means described in this AC, you must follow it in all aspects.

1.2 Audience

This AC is for airplane and rotorcraft manufacturers, modifiers, and type certification engineers seeking certification or installation guidance for their visual display system. Sections 23.773, 25.773, 27.773 and 29.773 address vision systems using a transparent display surface located in the pilot’s outside view, such as a head-up-display, headmounted display, or other equivalent display. Such “vision systems” could include any EVS, EFVS, SVS, or CVS.

1.3 Applicability

1.3.1 This AC applies to all applicants for a new type certificate (TC), an amended type certificate (ATC), or a supplemental type certificate (STC), to install enhanced and/or synthetic vision systems and equipment. The method of compliance described in this AC can be used to obtain a TC, STC, or ATC for an airplane or rotorcraft equipped with SVS, EVS, CVS, or EFVS equipment.

1.3.2 This AC does not address operational aspects of vision systems or any changes in aircraft operational capability that may result from installation of vision systems. Guidance material for the operational aspects of EFVS described in this AC can be found in AC 90-106A, Enhanced Flight Vision Systems.

Chapter 1. Introduction › 1.6 Cancellation

1.4 How to Use This Document

1.4.1 This AC provides methods, procedures, and practices acceptable to the FAA for complying with regulations. EFVS compliance references are listed in Appendix A.

1.4.2 This material does not alter regulatory requirements.

1.4.3 This AC describes system performance.

1.4.4 EFVS safety standards and sample flight test considerations for EFVS conducted to 100 feet height above runway touchdown zone elevation (EFVS Approach System) and for EFVS operations conducted to touchdown and rollout (EFVS Landing System) are in Appendices B, C, D, and E.

1.4.5 A sample flight manual supplement is outlined in Appendix F.

1.4.6 Appendix G addresses specific installation guidance for EVS and/or SVS on rotorcraft. Appendix H addresses additional part 23 considerations for situation awareness only.

1.5 Definitions and acronyms are in Appendix I.

1.5.1 Certain material within this AC is from RTCA/DO-315A, Minimum Aviation System Performance Standards (MASPS) for Enhanced Vision Systems, Synthetic Vision Systems, Combined Vision Systems, and Enhanced Flight Vision Systems. RTCA/DO- 315A is copyrighted by RTCA, Inc. and used with permission. Purchase information is in Appendix J.

1.6 Cancellation

AC 20-167, Airworthiness Approval of Enhanced Vision System, Synthetic Vision System, Combined Vision System, and Enhanced Flight Vision System Equipment, dated June 22, 2010, is canceled.

2.1 Enhanced Vision Systems › 2.1.1 An EVS is an electronic means to provide a display of the forward…

CHAPTER 2. VISION SYSTEMS OVERVIEW

2.1 Enhanced Vision Systems

2.1.1 An EVS is an electronic means to provide a display of the forward external scene topography through the use of imaging sensors, such as forward looking infrared (FLIR), millimeter wave (MMW) radiometry, MMW radar, and/or low-light-level image intensifying. EVS need not provide the additional flight information/symbology required in 14 CFR 91.176 on a Head Up Display (HUD) or equivalent display. While Enhanced Vision Systems share a similarity with EFVS technology, an EVS does not have to be integrated with a flight guidance system. Furthermore, while an EVS may provide additional situation awareness without the additional capabilities provided by an EFVS, it provides no credit towards operations conducted under 14 CFR 91.176 (a) and (b). The elements of an installed EVS are listed below, with the EVS diagram shown in Figure 1:

 EVS sensor system.

 Display processor.

 EVS display.

 Pilot controls/interface.

 Mounting.

Visible

External Scene Energy

Atmosphere

Sensor

Sensor Conversion

Sensor System

Display Processor

Pilot's Eye

Enhanced Flight Vision

System

Aircraft State

Data

Head-up Display

Processing

Head-up

Display

Enhanced

Vision System

EVS Display

Pilot Controls

Figure 1. Enhanced Vision Diagram (Dashed lines and shading represent individual system boundaries for EVS and EFVS)

2.2 Synthetic Vision Systems › 2.2.1 Synthetic vision is a computer-generated image of the external…

Note 1: While an EFVS contains all the elements of an EVS, for the purposes of this AC any discussion of an EVS excludes an EFVS.

Note 2: For the purposes of this AC, any guidance that applies to Head Up Display (HUD) also applies to displays equivalent to HUD.

2.1.2 The categories of current EVS sensors are passive or active sensors.

2.1.2.1 Passive Sensors: Scene contrast detected by passive infrared sensors can be much different than that detected by natural pilot vision. On a dark night, thermal differences of objects, not detectable by the naked eye, will be easily detected by many imaging infrared systems. However, contrasting colors in visual wavelengths distinguished by the naked eye may not be visible using an imaging infrared system. Sufficient thermal scene contrast allows shapes and patterns of certain visual references to be recognized in the infrared image by the pilot. However, depending on conditions, they can also appear different to a pilot in the infrared image than they would with normal vision.

2.1.2.2 Active Sensors: Scene contrast by active systems depends on several parameters such as: whether the transmitter is centered on the aircraft velocity vector, display updates rates, latency, range resolution, sensitivity, dynamic range, and azimuth and elevation resolution. For an active infrared thermal imaging sensor, the infrared illuminator has the potential to illuminate more weather obscurations, which can compete with scene contrast and interpretation. One advantage of millimeter wave radar systems is their general immunity to weather obscurations.

2.1.2.3 Unlike the pilot's external view, the enhanced vision image can be a monochrome, two-dimensional display. Some, but not all, of the depth cues found in the natural view are also found in the imagery. The quality of the enhanced vision image and the level of enhanced vision sensor performance depend on the atmospheric and external visible and nonvisible energy source conditions. Gain settings of the sensor, and brightness or contrast settings of the display, can significantly affect image quality. Certain system characteristics could create distracting and confusing display artifacts.

2.2 Synthetic Vision Systems

2.2.1 Synthetic vision is a computer-generated image of the external scene topography relative to the aircraft that is derived from aircraft attitude, high-precision navigation solution, and database of terrain, obstacles, and relevant cultural features. A synthetic vision system is an electronic means to display a synthetic vision image of the external scene topography to the flight crew. Synthetic vision creates an image relative to terrain and airport within the limits of the navigation source capabilities (position, altitude, heading, track, and the database limitations). SVS provides situation

awareness but cannot be used in lieu of natural vision. The application of synthetic vision systems is through a primary flight display from the perspective of the flight deck (egocentric), or through a secondary flight display from the perspective correlating to outside the aircraft (exocentric, like a “bird’s eye” view of a moving map display). This AC addresses both perspectives. The elements of an installed SVS are listed below, with the SVS diagram shown in Figure 2.

 Display (includes interface and installation).

 System interface.

 Database of terrain and obstacles.

 Sources providing the aircraft altitude, attitude, and position.

Visible

External Scene Energy

Atmosphere

Aircraft Altitude, Attitude, Position

Database

Synthetic

Vision

Display Processing

Pilot's Eye

Display

Figure 2. Synthetic Vision Diagram (Dashed lines represent individual system boundaries. External scene visible image is

not affected by SVS.)

2.2.3 With the exception of terrain and database processing (addressed… › 2.2.3.4 Terrain and cultural features, such as:

2.2.2 Synthetic vision coordinate referenced databases are usually referenced to digital terrain elevation data (DTED). Digital terrain data can help produce a digital elevation model (DEM), a terrain database used to draw the terrain image on a synthetic vision display.

Note: For information purposes, there are three DTED levels with the following terrain spacing:

 DTED Level 0 uses 30 arc second spacing (nominally one kilometer).

 DTED Level 1 uses 3 arc second spacing (approximately 100 meters).

 DTED Level 2 uses one arc second spacing (approximately 30 meters).

2.2.3 With the exception of terrain and database processing (addressed in chapter 4, paragraph 4.3.7), synthetic vision characteristics may include:

2.2.3.1 Display factors, such as:

 Conformality.

 Refresh rate.

 Field of regard (FOR).

 Field of view (FOV).

2.2.3.2 Display placement factors, such as:

 Pilot’s primary FOV versus pilot’s secondary FOV. See figure A3-1

in AC 25-11B.

 Head down display (HDD) versus Head up display (HUD).

2.2.3.3 Terrain presentation factors, such as:

 Depiction (such as monochromatic, photo-realistic, elevation

coloring).

 Gridding (presence versus absence, spacing).

 Color, shading, shadowing, and texturing. (This AC does not establish

criteria for these items.)

 Resolution. DEM resolution and DTED level.

 Range indication (e.g., terrain based range marks, color scheme).

2.2.3.4 Terrain and cultural features, such as:

 Rivers, valleys, and mountains.

 Major landmarks, highways, and buildings within close proximity to

airport.

 Hue and contrast between terrain and sky.

2.3 Combined Vision Systems › 2.3.2 For combined vision systems applicants are expected to meet…

 Man-made obstacles (e.g., radio towers, bridges, tall buildings) and

airport depiction.

 Airport depiction, including markings (e.g., extended runway

centerline and numbers, taxiway markings, approach lighting system).

 Range marks or indications.

2.2.3.5 Functions, such as:

 Alerting (terrain, obstacles, traffic, and airspace).

 Declutter.

 Mode reversion.

 Image control (FOV, brightness, contrast, registration).

2.2.3.6 Integration of guidance symbology (if incorporated), such as:

 Guidance cues (flight path vector, flight path angle reference cue,

velocity vector, command guidance cues, deviation indicators, and trend indicators).

 Aircraft reference relative to terrain (indication of relationship between

zero pitch line and terrain).

 Pathway markings (“breadcrumbs,” rectangles) and boundaries, to

indicate past or intended future aircraft track.

 Navigation information (course lines, fixes, icons, special-use

airspace).

 Unusual attitude recovery.

 Crosswind indication (and image display based on cross-track).

2.3 Combined Vision Systems

2.3.1 The CVS concept involves a combination of SVS and EVS or EFVS. Some examples of a CVS include database-driven synthetic vision images combined with real-time sensor images superimposed and correlated on the same display. This includes selective blending of the two technologies based on the intended function of the vision system for which approval is sought. For example, on an approach, most of the arrival would utilize the SVS picture. As the aircraft nears the runway, the picture gradually and smoothly transitions from synthetic to enhanced vision, either for SVS picture validation or displaying the runway environment.

2.3.2 For combined vision systems applicants are expected to meet applicable performance criteria for each incorporated system.

2.4.3 Depending on the intended operational function of the EFVS,… › 2.4.3.2 EFVS Landing System – The installed EFVS has been demonstrated…

2.4 Enhanced Flight Vision Systems

2.4.1 An EFVS, as defined in 14 CFR § 1.1, is “an installed aircraft system which uses an electronic means to provide a display of the forward external scene topography (the natural or manmade features of a place or region especially in a way to show their relative positions and elevation) through the use of imaging sensors, including but not limited to forward-looking infrared, millimeter wave radiometry, millimeter wave radar, or low-light level image intensification. An EFVS includes the display element, sensors, computers and power supplies, indications, and controls.” The EFVS must present EFVS sensor imagery, aircraft flight information, and flight symbology on a head up display, or an equivalent display, so that the imagery, information and symbology are clearly visible to the pilot flying in his or her normal position with the line of vision looking forward along the flight path (ref 14 CFR § 91.176(a)(1)(i)(B)). During an instrument approach, the enhanced vision image is intended to enhance the pilot's ability to detect and identify the visual references required by the regulations.

2.4.2 An EFVS requires a real-time imaging sensor providing demonstrated vision performance in low visibility conditions and a level of safety suitable for the proposed operational procedure. This allows the required visual references to become visible in the image before they are visible naturally out-the-window. Depending on atmospheric conditions and the strength of energy emitted and/or reflected from the scene, the pilot can use the imagery produced by an EFVS to see these visual references on the display better than the pilot can see them through the window without enhanced vision. Currently approved enhanced flight vision systems use passive infrared sensor technology. However, an active or passive sensor, as described in chapter 2, paragraph 2.1.2, could be used provided it meets the performance criteria in this AC.

2.4.3 Depending on the intended operational function of the EFVS, airworthiness approval will be designated as an EFVS Approach System or EFVS Landing System as described below. Depending on the airworthiness approval being sought by the applicant, additional basic equipage may be required by § 91.176. Those additional requirements are discussed in paragraph 4.5 of this AC.

2.4.3.1 EFVS Approach System – The installed EFVS has been demonstrated to meet the criteria for AC 20-167A for an EFVS Approach System to be used for instrument approach operations from DA/DH or MDA to 100 TDZE while all system components are working, but may have failure modes that result in the loss of EFVS capability. Above 100 feet above the TDZE, the pilot is expected to conduct a go-around if the EFVS fails. Descent below 100 feet above the TDZE through touchdown and rollout is conducted using natural vision, so any failure of the EFVS should not prevent the pilot from completing the approach and landing.

2.4.3.2 EFVS Landing System – The installed EFVS has been demonstrated to meet the criteria for AC 20-167A for EFVS Landing System to be used for instrument approach and landing operations that rely on sufficient visibility conditions to enable unaided rollout and to mitigate for loss of

2.4.4 The basic elements of an installed EFVS are required by 14 CFR §… › 2.4.4.3 The EFVS includes the display element, sensors, computers and…

EFVS function. An EFVS that meets the certification criteria for EFVS Landing System also meets the certification criteria for an EFVS Approach System.

2.4.4 The basic elements of an installed EFVS are required by 14 CFR § 91.176(a)(1)(i), and are listed below, with the EFVS diagram in Figure 1. Specific system criteria for EFVS systems can be found in Chapter 4 of this AC.

2.4.4.1 The EFVS must have an electronic means to provide a display of the forward external scene topography (the applicable natural or manmade features of a place or region especially in a way to show their relative positions and elevation) through the use of imaging sensors, including but not limited to forward-looking infrared, millimeter wave radiometry, millimeter wave radar, and low-light level image intensification;

2.4.4.2 Present EFVS sensor imagery, aircraft flight information, and flight symbology on a head up display, or an equivalent display, so that the imagery, information and symbology are clearly visible to the pilot flying in his or her normal position with the line of vision looking forward along the flight path. Aircraft flight information and flight symbology must consist of at least airspeed, vertical speed, aircraft attitude, heading, altitude, height above ground level such as that provided by a radio altimeter or other device capable of providing equivalent performance, command guidance as appropriate for the approach to be flown, path deviation indications, flight path vector, and flight path angle reference cue. Additionally, for aircraft other than rotorcraft, the EFVS must display flare prompt or flare guidance. The display should include:

2.4.4.2.1 The EFVS must present the displayed EFVS sensor imagery, attitude symbology, flight path vector, and flight path angle reference cue (FPARC), and other cues, which are referenced to the EFVS sensor imagery and external scene topography, so that they are aligned with and scaled to the external view;

2.4.4.2.2 The EFVS must display the flight path angle reference cue (FPARC) with a pitch scale. The FPARC must be selectable by the pilot to the desired descent angle for the approach and be sufficient to monitor the vertical flight path of the aircraft. The descent angle may also be automatically set to a value found in an onboard database.

2.4.4.2.3 The displayed sensor imagery, aircraft flight information, and flight symbology do not adversely obscure the pilot's outside view or field of view through the cockpit window.

2.4.4.3 The EFVS includes the display element, sensors, computers and power supplies, indications, and controls. It may receive inputs from an airborne navigation system or flight guidance system; and

2.4.7 Although the European Aviation Safety Agency (EASA) uses the term… › 2.4.7.1 Unlike with EFVS, an aircraft with EVS does not necessarily…

2.4.4.4 The display characteristics, dynamics, and cues that are suitable for manual control of the aircraft.

2.4.4.5 Depending on the EFVS intended function, installations designed to be eligible for EFVS Landing System operations must also have a flare cue and radio altitude. Refer to the performance criteria in paragraph 4.5 of this AC.

2.4.5 Enhanced flight vision displays both symbology and imagery.

2.4.5.1 Symbology illuminates a small fraction of the total display area of the HUD, leaving much of that area free of reflected light that could interfere with the pilot's view out the window through the display.

2.4.5.2 The EVS image is in the center of the pilot's regulated "pilot compartment view." It should be free of interference, distortion, and glare that would adversely affect the pilot's normal performance and workload. A video image can be more difficult for the pilot to see through than symbols also displayed on the HUD. Unlike symbology, the video image illuminates, to some degree, most of the total display area of the HUD with much greater potential interference with the pilot compartment view. It is sufficient for the pilot to see around the video image, but the outside scene must be visible through and around it.

2.4.6 Unlike the pilot's external view, the enhanced flight vision image is a monochrome, two-dimensional display. Some, but not all, of the depth cues found in the natural view are also found in the imagery. The quality of the enhanced flight vision image and the level of enhanced flight vision sensor performance could depend significantly on the atmospheric and external light source conditions. Gain settings of the sensor, and brightness or contrast settings of the HUD, can significantly affect image quality. Certain system characteristics could create distracting and confusing display artifacts. Finally, this is a sensor-based system that is intended to provide a conformal perspective. Refer to Figure 1 for a diagram of the system.

2.4.7 Although the European Aviation Safety Agency (EASA) uses the term “EVS” as equivalent to the FAA “EFVS,” do not confuse an EFVS with an Enhanced Vision System (EVS).

2.4.7.1 Unlike with EFVS, an aircraft with EVS does not necessarily provide the additional flight information or symbology required by 14 CFR § 91.176. An EVS is not required to use a HUD, and may not be able to present the image and flight symbology in the same scale and alignment as the outside view. An EVS can provide situation awareness to the pilot, but does not meet the regulatory requirements of 14 CFR § 91.176. An EVS cannot be used as a means to determine enhanced flight visibility or to identify the required visual references in order to gain operational credit and descend below the DA/DH or MDA.

2.4.7 Although the European Aviation Safety Agency (EASA) uses the term… › 2.4.7.2 For the primary display, the regulations also make provision…

2.4.7.2 For the primary display, the regulations also make provision for an equivalent display. Specifically, 14 CFR § 91.176(a)(1)(i)(B) states that EFVS sensor imagery, aircraft flight information, and flight symbology must be presented “on a head up display, or an equivalent display, so that the imagery, information and symbology are clearly visible to the pilot flying in his or her normal position with the line of vision looking forward along the flight path.” An equivalent display must be some type of headup presentation of the required information. A head-down display does not meet the regulatory requirement. For the monitoring display, see paragraph 4.5.2.1 of this AC.

3.2 Intended Function. › 3.2.2 EFVS

CHAPTER 3. AIRWORTHINESS PACKAGE CONTENTS

3.1 Airworthiness Package

The applicant is responsible for the following contents in the airworthiness package (for the purpose of this AC). This AC specifically addresses SVS with attitude displayed on the primary flight display (PFD), EVS/SVS/CVS with a head down display other than a PFD (such as a navigation display or multifunction display), EVS image displayed on a head up display, and an EFVS.

3.1.1 Intended function: Information on intended function can be found in section 3.2.

3.1.2 General operation: Information on the general operations and specific performance criteria can be found in Chapter 4.

3.1.3 Performance criteria and evaluation plan for the respective system. Performance evaluation is addressed in Chapter 6 with sample test considerations found in the appendices of this document, and

3.1.4 Installation considerations: Information regarding installation considerations can be found in Chapter 5 of this document.

3.2 Intended Function.

3.2.1 EVS, SVS, or CVS: Define the intended functions of your EVS, SVS or CVS. Include what features you will display and the criticality of pilot decision-making using the display features. Define additional intended functions (for example, terrain alerting) according to AC 25-11B and 14 CFR §§ 23/25/27/29.1301.

3.2.2 EFVS: Clearly define the intended function of your EFVS (EFVS Approach System or EFVS Landing System). This must include its use to assess enhanced flight visibility and to visually acquire the visual references required to operate below the DA/DH or MDA as specified in 14 CFR §§ 91.176 (a) and (b), 121.651, 125.381, and 135.225, and the criticality of pilot decision-making based on what is visible using the EFVS display. The purpose of the EFVS is to provide a visual advantage over the pilot’s out-thewindow view using natural vision. In low visibility conditions, the “enhanced flight visibility” should exceed the “flight visibility” and the required visual references should become visible to the pilot at a longer distance with an EFVS than they would out-thewindow using natural vision. Visual advantage using an EFVS must be demonstrated before descending below DA/DH or MDA because this is the point in an instrument approach procedure where the operating rules permit an EFVS to be used in lieu of natural vision for operational benefit.

Note 1: The EFVS is not intended to replace the technologies or procedures already used to safely fly the aircraft down to the MDA/MDH or DA/DH.

Note 2: While the goal of EFVS is to exceed the natural flight visibility in the majority of cases/weather conditions, there may be meteorological conditions where the EFVS does not provide a significant advantage.

Note 3: Past test data for existing EFVS sensor technology which demonstrated compliance should be considered for inclusion in this airworthiness package.

Note 4: Where appropriate, use of TSO criteria and performance can be beneficial to the FAA and the applicant.

4.1 EVS or SVS (or CVS when EVS and SVS combined) – General. › 4.1.5 The proposed system (EVS, SVS, and/or CVS):

CHAPTER 4. SYSTEM CRITERIA

4.1 EVS or SVS (or CVS when EVS and SVS combined) – General.

4.1.1 EVS/SVS/CVS Primary Displays. EVS, SVS, or CVS functionality can be superimposed on the electronic flight instrument system (EFIS), for example the primary flight display (PFD) as installed in the flight deck. In this configuration example, the EVS, SVS, or CVS image can be merged into the sky/ground shading of the attitude direction indicator. In addition to the traditional head down display PFD, this type of superimposed display could also be associated with a HUD or equivalent display system using EVS, SVS, or CVS capabilities. Maneuvering the aircraft during any phase of flight (taxi, approach, landing, rollout, etc.) shall not be predicated on EVS, SVS or CVS imagery alone.

4.1.2 EVS/SVS/CVS Secondary Displays. EVS, SVS, or CVS functionality can be selected on a multi-function display (MFD) or navigation display (ND) as one of many standalone type formats available in the flight deck. For example, an EVS, SVS, or CVS image can be one selection on the MFD, while an electrical synoptic could be another selection on the same MFD.

4.1.3 EVS, SVS, or CVS installed on side-mounted displays: While similar in concept to the MFD, side-mounted displays systems are, in general, limited due to the nature of the installation constraints of these devices. Side-mounted displays of EVS technologies can present unique certification challenges such as alignment or positioning concerns relating to the display installation. (See AC 120-76C, Guidelines for Certification, Airworthiness, and Operational Use of Electronic Flight Bag, for specific applications.)

4.1.4 The intended function for any installation of EVS/SVS/CVS must be clearly defined (appropriate 14 CFR §§ 23/25/27/29.1301), and the design and installation safety levels must be appropriate for the stated intended function. Although normally associated with use during flight, utilization of EVS display during ground operations should not be used if sensor proximity to the taxiway surface causes a distraction.

4.1.4.1 The intended function should be reasonable considering the actual functionality of the installation.

4.1.4.2 Operating limitations should be proposed to the FAA by the applicant. Operating limitations must be clearly defined and stated in the aircraft’s flight manual supplement in line with the intended function.

4.1.4.3 An EVS must not be used for flight guidance or navigation. An EVS cannot be used in lieu of natural vision to descend below DA/DH or MDA under §§ 91.176, 121.651, 125.381, or 135.225 regardless of whether it is on a HUD, or on a head down display.

4.1.5 The proposed system (EVS, SVS, and/or CVS):

4.1.6 Display Implementation. › 4.1.6.1.1 The image, or loss thereof, must not adversely affect the PFD…

4.1.5.1 Should have a means to automatically or manually control display brightness.

4.1.5.2 Must not degrade presentation of essential flight information. In other words, the pilot’s ability to see and use the required primary flight display information such as primary attitude, airspeed, altitude, and command bars/command guidance must not be hindered or compromised by the EVS/SVS/CVS image.

4.1.5.3 If the vision system uses a head-up display or the equivalent, then it may not distort the pilot compartment view, provide a distorted (i.e., nonconformal) view of the external scene, or interfere with the pilot’s ability to safely perform any maneuvers within the operating limitations of the aircraft, including taxiing, takeoff, approach, and landing. See paragraph 4.1.6.2 of this chapter.

4.1.5.4 Must not adversely affect any other installed aircraft system.

4.1.5.5 Perform its intended function in each aircraft environment where system approval is desired. For example, if the system is intended to perform in (or after exposure to) known icing conditions, a means can be required to keep the EVS sensor window clear of ice accumulation.

4.1.5.6 Should display the mode of operation (EVS, SVS, or CVS) to the pilot/crew. Consideration should be given to recording the EVS/SVS/CVS display status in a flight data recorder or some form of nonvolatile memory.

4.1.5.7 Should not have undesirable display characteristics (for example, jitter, jerky motion, and excessive delays).

4.1.6 Display Implementation. EVS/SVS/CVS can be incorporated into differing display types installed in the cockpit. AC 25-11B, Electronic Flight Displays and AC 23.1311- 1C, Installation of Electronic Display in Part 23 Airplanes, provide more information on electronic displays. The display is subject to all applicable primary flight information rules and guidance for the category of aircraft.

4.1.6.1 Primary Flight Display (PFD). Primary displays are cockpit displays used to provide information needed to guide and control the aircraft and provide the aircraft altitude, attitude, and airspeed indications. EVS/SVS/CVS can be implemented on the primary Head Down Display (HDD) in 14 CFR part 23 and 25 aircraft. Refer to AC 27-1B and AC 29- 2C for guidance on installation on rotorcraft. The following criteria apply to EVS/SVS/CVS implemented on a PFD.

4.1.6.1.1 The image, or loss thereof, must not adversely affect the PFD functionality.

4.1.6 Display Implementation. › 4.1.6.2.1 A design with EVS/SVS/CVS imagery displayed on a HUD must…

4.1.6.1.2 Align the displayed image with the aircraft’s inertial axis, physical axis or as appropriate for the intended function. The alignment can be variable and/or “phase of flight” dependent. The relationship between the image and the aircraft’s heading angle, pitch angle, roll angle, and track angle should generally align with the trajectory of the aircraft, should be recognizable by the flight crew, and not be misleading. For example, if two displays show EVS, SVS, or CVS information, or a combination (EVS on one and SVS on another), the orientation of the displays should be the same. Alignment of imagery presented on the PFD should be consistent with the real world and appropriate for the system’s intended function accounting for possible aircraft attitudes, turbulence, and wind effects.

4.1.6.1.3 Scale and align all spatially referenced symbology within each axis with the imagery so as not to present any misleading information to the pilot.

4.1.6.1.4 The Field of Regard (FOR) can be variable, but must be designed to ensure the displayed image is not distracting or misleading and does not adversely affect crew performance and workload. (Reference 14 CFR §§ 23/25/27/29.771 and §§ 23/25/27/29.1309.)

4.1.6.1.5 The display should not impede a clearly visible zero pitch reference line, distinct in visual appearance relative to any possible terrain, obstacle, or cultural feature display appearance.

Note: Including a flight path vector or velocity vector to show the pilot the aircraft’s trajectory relative to displayed terrain is recommended.

4.1.6.1.6 Per 14 CFR §§ 23/25/27/29.771 and §§ 23/25/27/29.773, pilot tasks must not be degraded by the displayed imagery. Depending on the intended function of the display information, the imagery must not provide the pilot with misleading information regarding detection, accurate identification, and avoidance of terrain, obstacles, and other flight hazards.

4.1.6.2 Head-Up Display or Equivalent. EVS/SVS/CVS can be implemented on a HUD, HDD or equivalent. The following criteria apply to EVS/SVS/CVS implemented on a HUD or equivalent display:

4.1.6.2.1 A design with EVS/SVS/CVS imagery displayed on a HUD must account for the pilot compartment view requirements found in 14 CFR §§ 23.773, 25.773, 27.773, and 29.773, including validation that the display of EVS imagery does not conflict with the pilot compartment view. The following tasks associated with the use of the pilot’s view must not be degraded below the level of safety that existed without the EVS:

 Detection, accurate identification and maneuvering, as necessary, to

avoid traffic, terrain, obstacles, and other hazards of flight.

4.2 EVS Specific Criteria. › 4.2.2 EVS installations must meet the following criteria:

 Accurate identification and utilization of visual references required for

every task relevant to the phase of flight.

Note: Although normally associated with use during flight, utilization of video imagery on the HUD or equivalent display during ground operations should not be considered if sensor proximity to the taxiway surface causes a distraction.

4.1.6.2.2 Imagery on the HUD or equivalent display must be conformal with the real world and appropriate for the system’s intended function accounting for possible aircraft attitudes, turbulence, and wind effects.

4.1.6.2.3 Society of Automotive Engineers (SAE) International design standards for HUD symbology, optical elements and video imagery are also prescribed with SAE Aerospace Standard (AS) 8055, Minimum Performance Standard for Airborne Head Up Display (HUD), dated March 1999, SAE Aerospace Recommended Practice (ARP) 5288, Transport Category Airplane Head Up Display (HUD) Systems, dated May 2001, and SAE ARP 5287, Optical Measurement Procedures for Airborne Head Up Display (HUD), dated March 1999. Apply specific design standards for resolution and line width, luminance and contrast ratio, chromaticity, and grayscale.

4.1.6.3 Secondary displays. EVS/SVS/CVS can be implemented with ego-centric “inside aircraft” views or exocentric “outside aircraft” viewpoints on head down displays. This includes installed EFBs or MFD. The following criteria apply to EVS/SVS/CVS implemented on secondary displays:

4.1.6.3.1 The orientation and perspective of the EVS/SVS/CVS view should be clear to the pilot.

4.1.6.3.2 If PFD information is displayed, it should meet PFD integrity requirements and availability criteria.

4.1.6.3.3 EVS/SVS/CVS image, or loss thereof, must not adversely affect other approved display functionality (such as navigation displays).

Note: Generally, the orientation of the secondary display should be the same as the primary display to decrease the possibility of pilot confusion.

4.2 EVS Specific Criteria.

4.2.1 An EVS requires a real-time imaging sensor and display, providing improved vision performance. These systems do not qualify for additional operational credit over and above what is already approved, and are installed on a non-interference basis.

4.2.2 EVS installations must meet the following criteria:

4.2.2 EVS installations must meet the following criteria: › 4.2.2.6.3 The image latency should be less than 100 milliseconds where…

4.2.2.1 The EVS depiction must be crew de-selectable (if on the primary display, the pilot should be able to easily and quickly declutter the EVS or remove sensor image). For an EVS image displayed on a HUD or equivalent display, the system must provide a means to allow the pilot using the display to immediately deactivate and reactivate the vision system imagery, on demand, without removing the pilot’s hands from the primary flight and power controls, or their equivalent.

4.2.2.2 The display mode (status of EVS), either through crew de-selection or as a result of a failure, should be clearly indicated or obvious to the crew.

4.2.2.3 The display and sensor FOR should be sufficient for the intended functions.

4.2.2.4 SAE design standards for EVS symbology, optical elements and video imagery are also prescribed in SAE AS 8055, SAE ARP 5288, and SAE ARP 5287. Apply the specific design standards for resolution and line width, luminance and contrast ratio, chromaticity, and grayscale.

4.2.2.5 Consider the following criteria for display characteristics for the EVS design, regardless of the display type:

4.2.2.5.1 For part 25 airplanes, apply all display characteristics listed in AC 25-11B. For part 23 airplanes, apply all display characteristics listed in AC 23.1311-1C. For other aircraft without corresponding criteria, the guidance in AC 25-11B or AC 23.1311-1C serves as recommended guidance.

4.2.2.5.2 The display should not have undesirable display characteristics (such as blooming, “burlap,” and running water).

4.2.2.6 Image characteristics.

4.2.2.6.1 On a HDD, the relationship of the display FOR to the actual field of view should be suitable for the pilot to smoothly transition from the HDD to the out-the-window real world view or HUD or equivalent display. The recommended maximum display minification is 3:1.

4.2.2.6.2 The image data should be refreshed at 15 Hz or better.

4.2.2.6.3 The image latency should be less than 100 milliseconds where the latency is measured from the image source time of applicability to the display of the image.

Note: EVS display refresh rate, when used in direct aircraft or power plant manual control tasks (such as attitude, engine parameters, etc.), equal to, or greater than 15 Hz has been found to be acceptable. Any lag introduced by the display system should be consistent with the aircraft control task

4.3.2 Image characteristics: › 4.3.2.3 The Field of Regard (FOR) should be appropriate for the…

associated with that parameter. In particular, display system lag (including the sensor) for attitude which does not exceed a first order equivalent time constant of 100 milliseconds for aircraft with conventional control system response is generally acceptable.

4.2.2.7 For display on a HUD or equivalent display, the minimum system should provide a control of the EVS display contrast/brightness which is effective in dynamically changing background (ambient) lighting. In addition, the minimum system must not:

 distract the pilot,

 impair the pilot’s ability to detect and identify visual references,

 mask flight hazards, or

 degrade task performance or safety.

4.2.2.8 When EVS is incorporated on the primary display, the EVS-based primary display must be clear and unambiguous when recovery from unusual attitudes is required. An accurate, easy, quick-glance interpretation of attitude should be possible for all unusual attitude situations and other “non-normal” maneuvers sufficient to permit the pilot to recognize the unusual attitude and initiate a recovery within one second. We recommend you use chevrons, pointers on all attitude indications to perform effective manual recovery from unusual attitudes. (For part 25 aircraft, refer to AC 25-11B. For part 23 aircraft, refer to Appendix H.)

4.3 SVS Specific Criteria.

4.3.1 Synthetic Vision Systems require a terrain and obstacle database, a precision navigation position, display, and height, attitude, and heading/track inputs. The design and installation safety levels should be appropriate for the system’s intended function. AC 25-11B and AC 23.1311-1C provide additional general display guidance.

4.3.2 Image characteristics:

4.3.2.1 Failure or de-selection of the synthetic vision depiction should be obvious to the crew.

4.3.2.2 The display can depict the scene from the pilot’s view looking through the front window (egocentric) or from outside the aircraft (exocentric). However, if implemented on a primary display, then the display should depict the scene from the pilot’s perspective looking through the front window.

4.3.2.3 The Field of Regard (FOR) should be appropriate for the system’s intended function and account for possible aircraft attitudes, turbulence, and wind effects (for example, to orient the line of sight according to

4.3.2 Image characteristics: › 4.3.2.9 The pilot’s view should not be depicted below the earth’s surface.

heading and not to track). Synthetic vision scene compression can result from FOR selections or display size limitations. Regardless, prominent topographical features should be easily identified and must be correlated with the actual external scene.

4.3.2.4 Identify dominant topographical features present in the SVS image in the outside view. Dominant topographical features present in the outside view should also be identifiable in the SVS image.

4.3.2.5 Terrain:

4.3.2.5.1 A potential terrain or obstacle conflict should be obvious to the pilot, and must not conflict with TAWS or HTAWS requirements. One mechanism for making such conflicts obvious on a primary display is an earth-based flight path vector. For guidance regarding alerts, use AC 23.1311-1C or AC 25.1322-1.

4.3.2.5.2 Displayed topographical features should not intersect guidance provided to the pilot to fly a published approach path. Terrain and 3-space position resolution should be accurate enough that topographical features should not intersect published approach paths.

4.3.2.5.3 Threatening terrain, close enough to generate a terrain warning alert, should appear above the artificial horizon zero pitch reference line if it is higher than the aircraft altitude.

4.3.2.6 SVS-based primary displays must be clear and unambiguous when recovery from unusual attitudes is required. An accurate, easy, quickglance interpretation of attitude should be possible for all unusual attitude situations and other “non-normal” maneuvers sufficient to permit the pilot to recognize the unusual attitude and initiate a recovery within one second. We recommend you use chevrons, pointers, and/or permanent ground-sky horizon on all attitude indications to perform effective manual recovery from unusual attitudes. (For part 25 aircraft, refer to AC 25-11B. For part 23 aircraft, refer to Appendix H.) Always have some indication of both sky and ground visible on the PFD for use in initiating unusual attitude recovery. SVS displays used as an attitude indicator require an egocentric orientation.

4.3.2.7 The relationship of the display FOR to the actual field of view should be suitable for the pilot to smoothly transition from the head-down display to the head-up, out-the-window real features.

4.3.2.8 The terrain depiction should include large bodies of water. Differentiation between water and sky depictions should be clearly distinguishable.

4.3.2.9 The pilot’s view should not be depicted below the earth’s surface.

4.3 SVS Specific Criteria. › 4.3.3 Position Source.

4.3.2.10 The image should be updated at 15 Hz or better and function smoothly during all expected maneuvering reasonable for the class and type of aircraft.

4.3.2.11 The image latency for a PFD or HUD or equivalent display should be consistent with the image guidance in AC 25-11B or that necessary for expected maneuvering reasonable for the class and type of aircraft. For other displays in the flight deck, a larger lag can be acceptable subject to the intended function.

4.3.2.12 Undesirable display characteristics should be minimized (for example, jitter, jerky motion, and excessive delays).

4.3.2.13 Range:

4.3.2.13.1 The scene range should be the natural horizon for both egocentric and exocentric displays. For systems intended for use in approach, missed approach, take-off, and departure operations, the scene range should be whichever is less of the following: natural horizon, 40 nautical miles, or 10 minutes at maximum cruise speed.

4.3.2.13.2 The scene range from the eye position to the terrain horizon must not be misleading and must be appropriate to the intended function. The intent is to prevent misleading information due to a SVS range limitation to the horizon that could lead to crew confusion at a critical phase of flight. At some airports the missed approach can take the aircraft on a course towards mountains. Pilots need to see that the mountains will be a factor in their missed approach long before they get to the runway. Thus, it is not acceptable for an approach to appear as if it is over flat terrain until short final when the mountains in the distance finally start appearing on the PFD.

4.3.2.14 Although every possible scenario cannot be described, the crew should be able to perceive relative distances to prominent topographical features. For example, the pilot should be able to identify an immediate terrain threat versus a distant terrain conflict.

4.3.2.15 All obstacles taller than 200 feet above ground level should be displayed. These obstacles must be displayed in the scaled and aligned position relative to other features on the synthetic vision image.

Note: Obstacle display consideration should be given to reducing clutter when objects pose no threat, yet not suddenly appear at low altitudes during periods of task saturation.

4.3.3 Position Source. The horizontal position source used for the SVS display should at least meet the criteria for TAWS or HTAWS. The horizontal position source must not provide contradictory indications of horizontal terrain clearance. Additional guidance

4.3.7 Terrain and Obstacle Database. › 4.3.7.2 Obstacle database.

for the horizontal position source can be necessary, depending on the intended functions of the SVS. TAWS guidance is contained in AC 25-23 and AC 23-18. HTAWS guidance is contained in AC 27-1B and 29-2C.

4.3.3.1 The synthetic vision display must not conflict with either the terrain warning or terrain awareness functions (for example, TAWS or HTAWS).

4.3.3.2 Any aircraft incorporating SVS from the egocentric perspective should also provide a TAWS or HTAWS or terrain warning system (refer to Appendix H for specifics on a terrain warning system). If terrain alerts and cautions are depicted on the SVS, they must be consistent across all displays in the cockpit when terrain threats are identified. In other words, terrain database sources should be consistent.

4.3.4 Altitude Source. The altitude source used for the SVS display should meet the criteria for TAWS or HTAWS installations, including the need to account for cold temperature errors which could place the aircraft closer to the surface than the altimeter indicates. The altitude source should be consistent with that used for the onboard terrain awareness and alerting system on the aircraft and must not provide contradictory indications of vertical terrain clearance. Additional criteria for the altitude source may be necessary, depending on the intended functions of the SVS. TAWS guidance is contained in AC 25-23 and AC 23-18. HTAWS guidance is contained in AC 27-1B, AC 29-2C, and TSO-C194.

4.3.5 Attitude Source. The attitude source must not conflict with attitude information or integrity criteria provided by the primary flight display.

4.3.6 Heading/Track Source. The heading/track source must not conflict with heading/track information provided by the navigation display.

4.3.7 Terrain and Obstacle Database.

4.3.7.1 Terrain and obstacle database processing. The terrain and obstacle database, along with any other database used to create the SVS image should be compliant to RTCA/DO-200A, as applicable to the intended function. The minimum terrain database resolution and accuracy must be consistent with the intended function, and should comply with the resolution and accuracy listed in TSO-C151, Appendix A, section 6.3, or for helicopters, TSO-C194.

 Position accuracy, symbology, and topographical information should

be consistent with each other.

 Runway elevations must be accurate at the approach ends and not just

at the airport center.

4.3.7.2 Obstacle database. The obstacle database should include all available physical hazards greater than 200 feet above ground level, not just terrain. The system should neither disregard nor corrupt obstacles available in the

4.4 CVS Specific Criteria. › 4.4.1 CVS requires a real-time imaging sensor and display that provides…

database greater than 200 feet above ground level. Obstacles displayed should be those deemed hazardous to the flight (or phase of flight). The applicant should provide procedures in the Instructions for Continued Airworthiness to ensure the most current obstacle database is installed.

Note: It is difficult to apply one altitude value across a wide range of aircraft performance, from rotary wing to high performance fixed wing. Generally, above 5,000 ft AGL, most obstacles are not tall enough to be hazardous. However, in the airport terminal area, even obstacles less than 1,000 ft AGL can be hazardous.

4.3.7.3 Navigation Database. The navigation database used by SVS for runway and airport information should be consistent with that used by other systems in the aircraft (for example, flight management systems). The applicant should provide procedures to document database currency in the Instructions for Continued Airworthiness.

4.3.7.4 Features. If flight path guidance features are provided by the SVS, they should complement (or correspond with) approved navigation system guidance.

4.3.7.5 Head-Up Displays. Providing complete guidance for synthetic vision systems is complicated by the many design variables available to manufacturers. Since synthetic vision displays can share many characteristics with a HUD, applicants should use HUD display guidance where appropriate.

4.3.7.6 Terrain display. If the intended function is “terrain awareness,” then “awareness” is consistent with the actual terrain. The display may not match the terrain perfectly, but the display should provide a reasonable representation of the terrain in a manner that does not misrepresent the threat posed by the terrain. The display, while possibly resolution or fieldof-view limited, may still adequately portray terrain awareness. The pilot should be aware of less than a 1:1 ratio of depiction. The pilot could be made aware of this ratio by training, the Airplane Flight Manual, symbology or other means. Display suitability must be matched against intended function.

4.4 CVS Specific Criteria.

4.4.1 CVS requires a real-time imaging sensor and display that provides demonstrated vision performance for its intended function. They also require a terrain and obstacle database and a precision navigation position for the synthetic portion of the display. The design assurance levels should be appropriate for the system’s intended function. The following criteria apply to CVS installations:

4.5.1 EFVS criteria would meet EVS criteria. › 4.5.1.3 The HUD or equivalent display and displayed FOR should be…

4.4.1.1 CVS should meet the respective criteria of the EVS and SVS implementations.

4.4.1.2 The EVS and SVS depictions should be conformal with each other.

4.4.1.3 Fusion of EVS and SVS should require the images to be aligned within 5 milliradian (mrad) laterally and vertically at the boresight of the display. Therefore, blended EVS and SVS images should not cause confusion to the flight crew. Significant image discrepancies between EVS and SVS due to failure conditions should be obvious to the crew.

Note: It is difficult to define every implementation in order to determine what is “significant.” However, the applicant is expected to reduce discrepancies to as near-zero as possible. The final determination will occur during flight test.

4.4.2 The CVS should meet the detailed performance criteria for EVS and SVS specified in paragraphs 4-2 and 4-3 of this chapter.

4.5 EFVS – General and Specific Criteria.

4.5.1 EFVS criteria would meet EVS criteria. However, there are additional EFVS general and specific criteria for operational credit, as follows:

4.5.1.1 Mitigate system failures more frequent than extremely improbable which produce effects the pilot (or the aircraft itself) cannot safely handle. Design the aircraft systems so the entire fault probability is kept to an acceptable level, and complies with 14 CFR part §§ 23/25/27/29.1309 regulations.

4.5.1.2 The sensor image, combined with the required aircraft state and position reference symbology, is presented to the flight crew on the HUD, or an equivalent display, so that they are clearly visible to the pilot flying in his or her normal position and line of vision looking forward along the flight path. For HUD or equivalent display operations, the pilot flying views the EFVS sensor and symbolic information that is properly aligned and registered to enable a one-to-one (conformal) overlay with the actual external scene.

4.5.1.3 The HUD or equivalent display and displayed FOR should be sufficient for the EFVS information to be displayed conformally over the range of anticipated aircraft attitudes, aircraft configurations, and environmental (for example, wind) conditions. The aircraft state and position reference data is presented in the form of symbology overlaying the image presentation. The flight instrument data on the HUD or equivalent display must include:

 Airspeed;

4.5.1 EFVS criteria would meet EVS criteria. › 4.5.1.6 The EFVS display controls should be visible to, and within…

 Vertical speed;

 Aircraft attitude;

 Heading;

 Altitude;

 Command guidance as appropriate for the approach to be flown;

 Path deviation indications;

 Flight path vector; and

 Flight path angle reference cue.

4.5.1.4 For an EFVS Landing System intended for landing (i.e., from DA/DH through touchdown and roll out at not less than1000ft RVR, the following specified aircraft flight information, in addition to that noted above in 4.5.1.3, must also be displayed:

 Height above ground level such as that provided by a radio altimeter or

other device capable of providing equivalent performance, and

 Flare prompt or flare guidance for achieving acceptable touchdown

performance, as discussed in paragraph 6.2.

4.5.1.5 The minimum system should include a control of EFVS display contrast/brightness which is effective in dynamically changing background (ambient) lighting, prevents distractions to the pilot, prevents impairment of the pilot’s ability to detect and identify visual references, prevents masking of flight hazards, or otherwise degrades task performance or safety. If automatic control for image brightness is not provided, it should be shown that manual setting of image brightness meets the above criteria and does not cause excessive workload.

4.5.1.6 The EFVS display controls should be visible to, and within reach of, the pilot flying from any normal seated position. If each pilot station is equipped with EFVS, the EFVS display controls should be visible to, and within reach of, the respective pilot from any normal seated position. The position and movement of the controls should not lead to inadvertent operation. The EFVS controls, except those located on the pilot’s control wheel, should be adequately illuminated for all normal background lighting conditions, and should not create any objectionable reflections on the HUD or equivalent display or other flight instruments. There must be a means to allow the pilot using the display to immediately deactivate and reactivate the vision system imagery, on demand, without removing the pilot’s hands from the primary flight and power controls, or their equivalent. (Ref 14 CFR §§ 23.773(c)(3), 25.775(e)(3), 27.773(c)(3), and 29.773(c)(3)).

4.5.1 EFVS criteria would meet EVS criteria. › 4.5.1.9 The minimum detection EFVS range (figure 3, below) can be…

4.5.1.7 The approach path situation references and command guidance should be based on the navaid for the straight-in instrument approach procedure in use.

4.5.1.8 Under 14 CFR § 91.176, upon reaching the decision altitude/decision height (DA/DH) or minimum descent altitude/minimum descent height (MDA/MDH), the required visual references presented in Table 1 must be distinctly visible and identifiable to the pilot. Sensor performance criteria can be quantified in terms of the range of the enhanced flight visibility compared to the flight visibility when low visibility conditions exist. The visual references of the runway environment must be seen by the sensor at operationally relevant distances.

Table 1. EFVS Visibility and Visual Reference Requirements

From the authorized DA/DH to 100 feet height above touchdown zone elevation of the runway of intended landing, the approach light system (if installed) or both the runway threshold and the touchdown zone are distinctly visible and identifiable to the pilot using an EFVS.

(A) The pilot must identify the runway threshold using at least one of the

following visual references -

(1) The beginning of the runway landing surface; (2) The threshold lights; or (3) The runway end identifier lights. (B) The pilot must identify the touchdown zone using at least one of the

following visual references -

(1) The runway touchdown zone landing surface; (2) The touchdown zone lights; (3) The touchdown zone markings; or (4) The runway lights At 100 feet height above touchdown zone elevation of the runway of intended landing and below that altitude, the enhanced flight visibility using EFVS is sufficient for one of the following visual references to be distinctly visible and identifiable to the pilot. For EFVS Approach System operations the listed features must be identified without reliance on the EFVS Approach System. For EFVS Landing and Rollout Operations the listed features may be identified using an EFVS Landing System.

(A) The runway threshold; (B) The lights or markings of the threshold (C) The runway touchdown zone landing surface; or (D) The lights or markings of the touchdown zone.

4.5.1.9 The minimum detection EFVS range (figure 3, below) can be derived by using an assumed minimum distance of the aircraft at the nominal

4.5 EFVS – General and Specific Criteria. › 4.5.2 EFVS General System Criteria.

Category I (200 ft) decision altitude before which the EFVS should image the runway threshold. On a 3 degree glide slope, the horizontal distance from the aircraft to the runway threshold is approximately 2816 feet (3816 feet from the precision touchdown zone markers). Use this range as a minimum performance value. These values do not take into account pilot decision time or actual atmospheric conditions, the use of non-precision approaches which can require greater distances, or the use of approaches with higher DAs, DHs, or MDAs.

Figure 3. Minimum Detection Range

4.5.1.10 The EFVS imagery displayed on the HUD or equivalent display must account for the pilot compartment view requirements found in 14 CFR §§ 25.773, 23.773, 27.773, and 29.773, including validation that the display of imagery does not conflict with the pilot compartment view. The display of EFVS sensor imagery must be on a system that compensates for the interference caused by the provided imagery. Additionally, the system must provide an undistorted and conformal view of the external scene, a means to deactivate the display and does not restrict the pilot from performing specific maneuvers. The following tasks associated with the use of the pilot’s view must not be degraded below the level of safety that existed without the video imagery:

 Detection, accurate identification and maneuvering, as necessary, to

avoid traffic, terrain, obstacles, and other hazards of flight.

 Accurate identification and utilization of visual references required for

every task relevant to the phase of flight.

Note: Although, the EFVS image requirements relate primarily to the approach and landing phases of flight, the EFVS image when viewed head up during ground operations should not create unacceptable distractions due to sensor proximity to the taxiway surface.

4.5.2 EFVS General System Criteria.

4.5.2 EFVS General System Criteria. › 4.5.2.4.3 Have acceptable display characteristics to accomplish the…

4.5.2.1 For EFVS implemented on a HUD, the image must be compatible with the FOV and head motion box of a HUD designed against SAE ARP 5288 (transport category head-up display (HUD) systems). When used in a given phase of flight, the HUD and EFVS FOR must provide a conformal image with the visual scene over the range of aircraft attitudes and wind conditions. A display that provides the pilot monitoring with EFVS sensor imagery is not required for EFVS Approach System operations. However, for EFVS Landing System operations, when a minimum flightcrew of more than one pilot is required for the conduct of the operation, the aircraft must be equipped with an operable display that provides the pilot monitoring with EFVS sensor imagery. Any display used to monitor the approach must be located in the cockpit in accordance with 14 CFR §§ 23/25/27/29.1321 so that any pilot seated at the controls can monitor the airplane’s flight path and instruments with minimum head and eye movement. Aircraft that pre-date 14 CFR §§ 23/25/27/29.1321 must meet the arrangement and visibility requirements in those sections for the installation of pilot monitoring displays. Any symbology displayed must not adversely obscure the sensor imagery of the runway environment.

4.5.2.2 EFVS display criteria must meet the airworthiness certification requirements in 14 CFR parts 21, 23, 25, 27, and 29 (as applicable), see Appendix A. Some of these requirements could be specific to EFVS and could be in addition to all other requirements applicable to the HUD and the basic avionics installation.

4.5.2.3 The current FAA guidelines for head-up displays apply with respect to EFVS. These criteria include well-established military as well as civil aviation standards for HUDs as defined in MIL-STD-1787C, Aircraft Display Symbology, and AC 25-11B. SAE design standards for HUD symbology, optical elements, and video imagery are also prescribed within SAE AS 8055, SAE ARP 5288 and SAE ARP 5287. Apply specific design standards for image size, resolution and line width, luminance and contrast ratio, chromaticity, and grayscale.

4.5.2.4 The EFVS image, when superimposed on the HUD symbology and when used in combination with other aircraft systems, must meet the criteria below. The EFVS image and installation must:

4.5.2.4.1 Be suitable for and successfully perform its intended function.

4.5.2.4.2 Allow the accurate identification and utilization of visual references, using both EFVS and natural vision as appropriate.

4.5.2.4.3 Have acceptable display characteristics to accomplish the intended function.

4.5.2 EFVS General System Criteria. › 4.5.2.7 14 CFR § 91.176 requires that the EFVS display a flight path…

4.5.2.4.4 There must be a means to allow the pilot using the display to immediately deactivate and reactivate the vision system imagery, on demand, without removing the pilot’s hands from the primary flight and power controls, or their equivalent. (Ref 14 CFR §§ 23.773(c)(3), 25.775(e)(3), 27.773(c)(3), and 29.773(c)(3)).

4.5.2.4.5 Not degrade the presentation of essential flight information on the HUD or equivalent display.

4.5.2.4.6 Not be misleading and should not cause confusion or any significant increase in pilot workload.

4.5.2.4.7 Be aligned with and scaled to the external scene, and should include the effect of near distance parallax.

4.5.2.4.8 Not cause unacceptable interference with the safe and effective use of the pilot compartment view.

4.5.2.4.9 Not misleadingly alter the color perception of the external scene so as to preclude the pilot’s performance of any required tasks by causing confusion or any significant increase in its workload, e.g. discerning PAPI lights accurately on approach.

4.5.2.4.10 Allow the pilot to recognize significantly misaligned or non-conformal conditions to the external scene that may preclude the pilot’s performance of any required maneuvers.

4.5.2.5 Additionally, the EFVS installation and image should have an effective control of EFVS display brightness without causing excessive pilot workload and not cause adverse physiological effects such as fatigue or eyestrain.

4.5.2.6 A HUD modified to display EFVS must continue to meet the conditions of the original approval and be adequate for the intended function, in all phases of flight in which the EFVS is used. An accurate, easy, quickglance interpretation of attitude should be possible for all unusual attitude situations and other “non-normal” maneuvers to permit the pilot to recognize the unusual attitude and initiate recovery within one second. We recommend you use chevrons, pointers, and/or permanent ground-sky horizon on all attitude indications to perform effective manual recovery from unusual attitudes. Refer to AC 25-11B for guidance on electronic flight deck displays.

4.5.2.7 14 CFR § 91.176 requires that the EFVS display a flight path vector (FPV) and flight path angle reference cue (FPARC) on the HUD or equivalent display. The following criteria apply to these symbols:

4.5.2.7.1 The position and motion of the FPV should correspond to the aircraft’s earth referenced flight path vector.

4.5.3 EFVS Detailed System Criteria. › 4.5.3.3 Likewise, since the purpose of the EFVS sensor is to provide a…

4.5.2.7.2 The dynamic response of FPV should follow pilot control inputs. Refer to SAE ARP 5589 for dynamic response guidance.

4.5.2.7.3 The display of the FPARC should be suitable for monitoring the vertical flight path of the aircraft.

4.5.2.7.4 The system must provide the pilot a means to select the desired descent angle that is represented by the FPARC, and may also provide a means for the descent angle to be selected automatically from a database.

4.5.2.8 The display of attitude symbology, FPV, FPARC, and other visual elements which are earth-referenced, must be aligned with and scaled (i.e., conformal) to the external view.

4.5.2.9 The EFVS display of imagery, flight information and flight symbology should be a suitable visual reference for the pilot during the manual performance of any maneuvers within the operating limitations of the aircraft, including taxiing, takeoff, approach, landing and rollout.

4.5.3 EFVS Detailed System Criteria.

4.5.3.1 The performance of EFVS imaging systems does not solely depend upon system design, but also depends upon the target scene characteristics such as the runway, light structures, electromagnetic radiation, and atmospheric conditions.

4.5.3.2 Since the purpose of the EFVS sensor is to provide a visual advantage over the pilot’s out-the-window view, the design should include a general performance analysis. This analysis includes calculated performance, which indicates the viability of the system to meet the proposed intended function, specifically including the calculated performance of the sensor operation within the range of the environment proposed.

4.5.3.3 Likewise, since the purpose of the EFVS sensor is to provide a visual advantage over the pilot’s out-the-window view, the general performance analysis should include the calculated transmission of electromagnetic energy in the visible spectrum and other relevant frequencies. The analysis should portray length of transmission over a path with generalized extinction coefficients at a given wavelength.

Note: Examples of acceptable sensor models are MODTRAN and LOWTRAN which can be used to estimate the performance of infrared systems. Other models (FASCODE) for radar systems may be used for these types of sensors and provide a basic measure of signal attenuation

helpful in assessing performance and viability for the functions required under 14 CFR § 91.176.

4.5.3 EFVS Detailed System Criteria. › 4.5.3.4.2 EFVS FOR.

4.5.3.4 Minimum system performance. Integration of the major components includes the installed sensor, its interconnections with the sensor display processor, the display device, pilot interface, and aircraft mechanical interface, which can include the radome for the sensor.

4.5.3.4.1 Latency. EFVS latency should be no greater than 100 milliseconds (msec). A longer lag time can be found satisfactory, provided it is demonstrated not to be misleading or confusing to the pilot. Latency should not be discernible to the pilot and should not affect control performance or increase pilot workload. EFVS latency causes, at best, undesirable oscillatory image motion in response to pilot control inputs or turbulence. At worst, EFVS latency may cause pilot-induced oscillations if the pilot attempts to use the EFVS for active control during precision tracking tasks or maneuvers in the absence of other visual cues.

4.5.3.4.2 EFVS FOR. The minimum fixed FOR should be 20 degrees horizontal and 15 degrees vertical. In applications where the FOR is centered on the flight path vector the minimum vertical FOR should be 5 degrees (± 2.5 degrees) and 20 degrees horizontal.

4.5.3.4.2.1 The minimum EFVS FOR should not only consider the HUD FOV (i.e., how large of an area displayed), but also the area over which this area subtends (i.e., what is shown on the conformal display). The FOR portrayed on the HUD is established by three primary determinants:

 HUD and EFVS sensor Field-Of-View;

 Orientation of the HUD with respect to the aircraft

frame of reference (for example, boresight and proximity to pilot’s eye); and

 Orientation (for example, attitude) of the aircraft.

4.5.3.4.2.2 SAE ARP 5288 states, “The design of the HUD installation should provide adequate display fields-of-view in order for the HUD to function correctly in all anticipated flight attitudes, aircraft configurations, or environmental conditions such as crosswinds for which it is approved. Limitations should be clearly specified in the AFM if the HUD cannot be used throughout the full aircraft flight envelope.” A quantitative EFVS FOR was established as minimum design criteria to be qualitatively checked during certification flight test for sufficiency in meeting its intended function. The EFVS FOR requirement resulted after consideration of the minimum field of regard criteria

4.5.3 EFVS Detailed System Criteria. › 4.5.3.4.7 Image conformality.

for various aircraft attitudes and wind conditions using a critical altitude of 200 ft height above touchdown zone elevation for EFVS visibility.

4.5.3.4.2.3 A variable FOR is permissible assuming a slewable sensor (i.e., variable field-of-regard), centered on the Flight Path Vector, with a minimum +/- 2.5 deg about the flight path vector to allow for momentary flight path perturbations and to allow sufficient fore/aft view of the required visual references.

4.5.3.4.3 Off-axis rejection. A source in object space greater than 1 degree outside the FOV should not result in any perceptible point or edge like image within the field of view. The EFVS should preclude off-axis information from folding into the primary FOR imagery, creating the potential for misleading or distracting imagery.

4.5.3.4.4 Jitter. When viewed from the HUD eye reference point, the displayed EFVS image jitter amplitude should be less than 0.6 mrad. Jitter for this use is defined in SAE ARP 5288. This implies the EFVS and HUD cannot exhibit jitter greater than that of the HUD itself.

4.5.3.4.5 Flicker. Flicker is brightness variations at frequency above 0.25 Hz per SAE ARP 5288. The minimum standard for flicker should meet the criteria of SAE ARP 5288. Flicker can cause mild fatigue and reduced crew efficiency. The EFVS and HUD cannot exhibit flicker greater than that of the HUD itself.

4.5.3.4.6 Image artifacts. The EFVS must not exhibit any objectionable noise, local disturbances, or an artifact that hazardously detracts from the use of the system. The EFVS design should minimize display characteristics or artifacts (for example, internal system noise, “burlap” overlay, or running water droplets) which obscure the desired image of the scene, impair the pilot's ability to detect and identify visual references, mask flight hazards, distract the pilot, or otherwise degrade task performance or safety.

4.5.3.4.7 Image conformality. The accuracy of the integrated EFVS and HUD image should not result in a greater than 5 mrad display error at the center of the display at a range of 2000 ft (100 ft altitude on a 3 degree glideslope). In accordance with SAE ARP 5288, the total HUD system display accuracy error as measured from the HUD eye reference point, should be less than 5.0 mrad at the HUD boresight, with increasing error allowable toward the outer edges of the HUD. Errors away from the boresight should be as defined in SAE ARP 5288. The primary EFVS error components include the installation misalignment of the EFVS sensor from aircraft/HUD boresight and sensor parallax. A range parameter is used in the EFVS conformability requirement to account for the error component associated with parallax. There is no error allowed

4.5.3 EFVS Detailed System Criteria. › 4.5.3.4.8 Sensor/sensor processor.

for the EFVS sensor, since it is assumed any error can be electronically compensated during installation. With EFVS operations, the aircraft is flown essentially irrespective of the EFVS/HUD dynamic error, to the MDA or DA. From this point to 100 ft height above touchdown zone elevation, the EFVS conformality error introduces error in the pilot’s ability to track along the extended centerline/vertical glide path as the pilot flies the flight path vector and glidepath reference line toward the EFVS image of the runway.

4.5.3.4.8 Sensor/sensor processor.

4.5.3.4.8.1 Dynamic range. The minimum required dynamic range for passive EFVS should be 48 db. For active EFVS, side lobes should be 23 db below the main beam, and 40 db dynamic range plus sensitivity time control (STC).

4.5.3.4.8.2 Sensor image calibration. Visible image calibrations and other built-in tests that cannot be achieved within a total latency of 100 milliseconds should occur only on either pilot command or be coordinated by aircraft data to only occur in non-critical phases of flight. If other than normal imagery is displayed during the non-uniformity correction (NUC) or other built-in tests, the image must be removed from the pilot’s display. This prohibits excessive times to complete maintenance or calibration functions which would remove or degrade the EFVS imagery during critical phases of flight, unless the pilot commands the action (with full knowledge of effect based on training and experience). Abnormal imagery should be removed from the display to eliminate the potential for any misleading information.

4.5.3.4.8.3 Sensor resolution. As a minimum, EFVS resolution performance shall adequately resolve (for pilot identification) the runway threshold and the touchdown zone to enable the intended function. For example, an EFVS should resolve a 60 ft wide runway from 200 ft height above touchdown zone elevation with a typical 3degree glide slope. The sensor resolution was established by providing this resolution at a minimum range, allowing the pilot to continue the descent below DA or MDA. (These values do not take into account pilot decision time or actual atmospheric conditions, or the use of nonprecision approaches which may require greater distances.) A 60 ft wide runway was chosen as the ICAO minimum runway width to support an instrument approach procedure.

4.5.3.4.8.4 Passive sensor optical distortion. Optical distortion should be 5 percent or less across the minimal FOR as defined in

paragraph 4.5.3.4.2 and no greater than 8 percent outside the minimal FOR.

4.5.3.4.8.5 Sensor sensitivity. In this context, the EFVS sensor sensitivity should be at least a noise equivalent temperature difference (NETD) of 50o mK tested at an appropriate ambient temperature, for passive EFVS systems or -20dB sm/sm (square meter/square meter) surface at Rmax from 200 ft height above touchdown zone elevation with a typical 3-degree glide slope for active EFVS systems. Passive sensors for different visible or short-wave infrared sources can require very sensitive detectors, as specified by low noise equivalent powers.

4.5.3.4.8.6 Failure messages. EFVS malfunctions detected by the system, and which can adversely affect the normal operation of the EFVS, should be annunciated. As a minimum, specific in-flight failure message(s) for sensor failure and frozen image must be displayed to the flight crew.

4.5.3.4.8.7 Blooming. The sensor should incorporate features to minimize blooming, which can create an unusable or objectionable image. Objectionable blooming is defined as the condition that obscures the required visual cues defined in Figure 3. Blooming to the extent the required visual references are no longer distinctly visible and identifiable is unacceptable.

4.5.3.4.8.8 Image persistence. The image persistence time constant should be less than 100 milliseconds. However, burn-in or longer image persistence caused by high energy sources (for example, the sun saturating the infrared sensor elements), should be removed from the image to comply with paragraph 4.5.3.4.6, Image artifacts, by a secondary on-demand process (for example, the NUC process).

4.5.3.4.8.9 Dead pixels. Dead pixels or sensor elements replaced by a “bad pixel” replacement algorithm should be limited to 1 percent average of the total display area, with no cluster greater than 0.02 percent within the minimum FOR. A small number of disparate dead pixel elements can be effectively replaced by image processing but eventually, the algorithms will degrade the image quality and accuracy due to the sheer number and closely-spaced location of the element.

4.5.3.4.8.10 Parallax. The effects of parallax caused by lateral, vertical, and longitudinal offset of the sensor from the pilots’ design eye points may not impede the EFVS from performing its

intended function, as evaluated during flight test. Parallax should not cause unsatisfactory landing performance parameters (e.g., flare height; sink rate, touchdown location; groundspeed during landing, exit and taxi) between EFVS operations and visual operations in the same aircraft.

5.1.6 EVS/SVS/CVS Required Safety Level. › 5.1.6.1.1 The airworthiness standard under which approval is sought can…

CHAPTER 5. SYSTEMS INSTALLATION CONSIDERATIONS

5.1 EVS/SVS/CVS Installations Considerations

5.1.1 EVS/SVS/CVS Pilot Controls.

5.1.1.1 The EVS/SVS/CVS display controls should be visible to, and within reach of, the pilot flying from any normal seated position. The position and movement of the controls should not lead to inadvertent operation.

5.1.1.2 The EVS/SVS/CVS controls, except those located on the pilot’s control inceptor (e.g., control wheel, yoke, stick, etc.), must be adequately illuminated for all normal background lighting conditions and must not create any objectionable reflections on other flight instruments.

5.1.1.3 There must be a means to modulate illumination unless fixed illumination of the EVS/SVS/CVS controls is shown to be satisfactory under all lighting conditions.

5.1.2 EVS/SVS/CVS Preventive Maintenance. Use manufacturer data for preventive maintenance (for example, Instructions for Continued Airworthiness, per 14 CFR § 21.50 and FAA Order 8110.54A), or other methods, techniques, and practices acceptable to the Administrator.

5.1.3 EVS/SVS/CVS Built-In Test (BIT). Provide a BIT capability that, at a minimum, limits the exposure time to latent failures consistent with the exposure limits in the system safety assessment.

5.1.4 The electrical system must be able to furnish the required power at the proper voltage for the EVS/SVS/CVS.

5.1.5 EVS/SVS/CVS System Safety Design Criteria. The overall safety requirement of the aircraft is based on installed equipment. A complete functional hazard assessment (FHA) and system safety analysis (SSA) should be conducted to identify failure modes and classify the hazard levels. To meet the safety criteria in 14 CFR §§ 23/25/27/29.1309, the system design will be demonstrated through analysis and engineering tests to preclude failures that can cause hazardously misleading information to be presented to the pilot or crew, or which can otherwise subsequently cause an unsafe condition. The following guidelines do not preclude the results of a full SSA. The results of an SSA found acceptable to the FAA should prevail.

5.1.6 EVS/SVS/CVS Required Safety Level.

5.1.6.1.1 The airworthiness standard under which approval is sought can impact criticality (for example, 14 CFR part 23, 25, 27, or 29). Recognizing that each implementation and integration of each installation can be unique, the applicant should perform a thorough FHA, SSA, and Failure Mode and

5.1.6 EVS/SVS/CVS Required Safety Level. › 5.1.6.1.4 The variables influencing the outcome of the failure…

Effects Analysis (FMEA). A system safety assessment should be performed in accordance with 14 CFR §§ 23/25/27/29.1309 that addresses both the loss as well as the incorrect display of information, including hazardously misleading information. Undetected failure conditions which cause a hazardously misleading EFVS depiction must have a probability no greater than that appropriate for the hazard effects they create.

5.1.6.1.2 To support the 14 CFR §§ 23/25/27/29.1309 analysis (as applicable), the applicant must perform a safety assessment based on the proposed installation for the given aircraft and intended function for each phase of flight. Information presented to a pilot on a PFD is considered truth unless flagged otherwise. Therefore, presenting hazardously misleading information to the pilot must be avoided. One example of hazardously misleading information (HMI) would be the aircraft level ramifications of a “frozen EVS/SVS/CVS display” that is undetected by the flight crew.

5.1.6.1.3 Once the safety assessment has been completed, for any hazard or failure classification greater than Major, a fault tree analysis (FTA) should be evaluated using the guidance found in the FAA system safety advisory circular that is applicable to the installation (e.g., AC 23.1309-1E, AC 25.1309-1A, AC 27-1B (containing AC 27.1309) and 29-2C). The FTA should include the display monitor, power supply, IR camera and sensors, cable, status annunciations, and other components that affect the top-level events.

5.1.6.1.4 The variables influencing the outcome of the failure condition and its classification vary between 14 CFR parts 23, 25, 27, and 29. In general, the sensor or system performance and level of design should be consistent with the SSA. Table 2 provides sample system operating phases for consideration. The results of an SSA found acceptable to the FAA should prevail.

Table 2. System Operating Phases for Considerations

GROUND TAKEOFF IN-FLIGHT LANDING

(1)Taxi (2) Maintenance

(1) Takeoff Roll Prior to V1, (2) Takeoff Roll After V1, (3) Takeoff After VR to 200’ (4) Rejected Takeoff

(1) Climb (2) Gear Up, (3) Cruise (4) Descent, (5) Gear Down, (6) Approach 200’ to 0’ (7) Go Around

(1) Touchdown & Rollout (2) Taxi

5.1.6.1.5 The normal operation (without malfunction) of the EVS/SVS/CVS may not adversely affect, or be adversely affected by other normally operating aircraft functions. The criticality of the EVS/SVS/CVS system’s function to display imagery, including the potential to display hazardously misleading information, should be assessed according to the applicable 14 CFR §§ 23/25/27/29.1309, AC 25-11B chapter 4, and AC 23/25/27/29.1309, System Safety Analysis and Assessment for Part 23/25 Airplanes. Likewise, the hazard effects of any malfunction of the EVS/SVS/CVS that could adversely affect interfaced equipment or associated systems should be determined and assessed according to the applicable 14 CFR §§ 23/25/27/29.1309, AC 25-11B chapter 4, and AC 23/25/27/29.1309. As applicable, similar criteria are found in SAE ARP 4754, and ARP 4761.

5.2.2 EFVS Display. › 5.2.2.2 Imagery and symbology display.

5.1.7 EVS/SVS/CVS Environmental Specifications. The EVS/SVS/CVS should meet all specified operating conditions and should provide required operating performance, life and reliability when operating within the aircraft and subsystem flight envelope as specified in RTCA DO-160F (or as revised) Environmental Conditions and Test Procedures for Airborne Equipment. These criteria must also include the high-intensity radiated fields (HIRF), electromagnetic interference (EMI), and lightning requirements as specified in the certification basis of the aircraft to be installed. A lightning zone analysis and assessment of the effects of lightning strike on the camera in conjunction with other cockpit equipment should be accomplished. The installation must be designed in a manner that lightning strikes on the EVS/SVS/CVS system does not cause catastrophic effects on the aircraft.

5.2 EFVS Display (HUD or Equivalent) Installation Considerations

5.2.1 EFVS Annunciations. Any modes of EFVS operation should be annunciated on the flight deck and visible to the crew. The modes of the EFVS operation must be made available to the flight data recorder as required.

5.2.2 EFVS Display.

5.2.2.1 Display resolution. Since the sensor can be active or passive, the EFVS display should adequately resolve a 60 ft. wide runway from 200 ft. height above touchdown zone elevation with a typical 3-degree glide slope. The pilot needs to be able to detect and accurately identify the visual references in the image.

5.2.2.2 Imagery and symbology display. Imagery must not degrade presentation of essential flight information on the HUD. The pilot's ability to see and use the required primary flight display information such as primary attitude, airspeed, altitude, and command bars must not be hindered or compromised by the EFVS image on the HUD.

5.2.5 EFVS System Safety Design Criteria to support the 14 CFR §§… › 5.2.5.1.2 The normal operation of the EFVS cannot adversely affect, or…

5.2.2.3 Flare Cue. An EFVS Landing System must have a flare cue because it is intended to enable landing in low visibility. The flare cue, whether a flare prompt or flare guidance, should demonstrate compliance to the landing criteria found in paragraph 6.2. For some aircraft, flare guidance may be required because a flare prompt is not sufficient.

5.2.2.3.1 Flare Prompt. A flare prompt is intended to notify the pilot that it is time to initiate the flare maneuver, but does not guide the pilot’s manual pitch control inputs. The pilot should use situational information (e.g., altitude, vertical rate, attitude, FPV, perspective view of the runway) from the EFVS to judge the magnitude and rate of manual pitch control inputs. The appearance and dynamic behavior of the flare prompt should be distinguishable from command guidance. The flare prompt should appear timely and conspicuously to the pilot using the HUD so that the flare maneuver will be neither too early nor too late and within the touchdown zone as described in paragraph 6.2 of this document.

5.2.2.3.2 Flare Guidance. Flare guidance provides explicit command guidance for the pilot to perform the flare maneuver in so that the flare would be neither too early nor too late and within the touchdown zone as described in paragraph 6.2 of this document.

5.2.3 EFVS Maintenance. Instructions for Continued Airworthiness are to be furnished after final design approval (reference 14 CFR § 21.50 and FAA Order 8110.54A).

5.2.4 EFVS Built-in Test (BIT). Provide a BIT capability (or equivalent means) that, at a minimum, limits the exposure time to latent failures in support of the system safety assessment.

5.2.5 EFVS System Safety Design Criteria to support the 14 CFR §§ 23/25/27/29.1309 analysis (as applicable).

5.2.5.1 The overall level of safety of the aircraft is based on installed equipment. A complete system safety analysis (SSA) should be conducted to identify failure modes and classify the hazard levels. To meet the safety criteria, the system design should preclude failures that can cause hazardously misleading information (HMI) to be presented to the pilot or crew, or which can otherwise subsequently cause an unsafe condition. For example, HMI could include information providing attitude, altitude, and distance cues as outside terrain imagery. This demonstration should be accomplished through analysis and engineering tests.

5.2.5.1.1 The EFVS system must perform its intended function for each applicable operation and phase of flight that it would use.

5.2.5.1.2 The normal operation of the EFVS cannot adversely affect, or be adversely affected by other aircraft systems. Annunciate detected

5.2.6 EFVS Approach System Required Level of Safety to support the 14… › 5.2.6.2 The applicant should demonstrate a satisfactory safety (failure…

malfunctions of the EFVS system and remove the malfunctioning display elements.

5.2.5.2 Appendix B, Table 4 lists the categories of systems and failure probabilities to meet the safety criteria in 14 CFR part 25 airplanes (AC 25.1309-1A). For 14 CFR part 23 aircraft, similar information can be found in 14 CFR § 23.1309 and AC 23.1309-1E. The following additional guidance helps assess the criticality of the EFVS display, including the potential to display HMI:

AC 25-11B (chapter 4),

AC 23.1311-1C, and

AC 27-1B and AC 29-2C, as appropriate for the installation.

5.2.5.3 Validate all alleviating flightcrew actions that are considered in the EFVS safety analysis during testing either for incorporation in the AFM/AFMS or RFM/RFMS limitation section, procedures section or for inclusion in type-specific training.

5.2.6 EFVS Approach System Required Level of Safety to support the 14 CFR §§ 23/25/27/29.1309 analysis (as applicable).

5.2.6.1 When you are designing an EFVS Approach System, establish safety design goals for airworthiness approval. The safety criteria for each phase of flight, including approach and landing systems are defined in terms of accuracy, continuity, availability, and integrity. FAA design guidance provides criteria to determine the overall required level of safety for the aircraft, in any mode of flight, for any combination of failures which can cause an unsafe condition to be fully assessed and categorized. This includes the probability of the pilot(s) to cope with these failures. The hazard level for any aircraft system depends on the ability of the pilot(s) to cope with failures. For failures where the SSA assumes a particular pilot intervention to limit the hazard effects, for example from Catastrophic or Hazardous to Major or Minor, the applicant must show the pilot can be relied on to perform that intervention. For example, the pilot might be assumed to detect a system error because of other displays or view out the window. It should be demonstrated that pilots can detect the error in a timely fashion and not be hazardously misled. The demonstration must validate the proposed hazard classification, as applicable (see Appendix B, Table 4).

5.2.6.2 The applicant should demonstrate a satisfactory safety (failure and performance) level which must not be less than the safety level required for non-EFVS Approach System based precision and non-precision approaches with decision altitudes of 200 ft. or above. In showing compliance, probabilities cannot be factored by the fraction of approaches which are made using EFVS. Consideration, however, can be given to the

5.2.7 EFVS Landing System Required Level of Safety to support the 14… › 5.2.7.2 To achieve the required safety level, the minimum baseline…

EFVS Approach System critical flight time, such as from the highest DH that can be expected for an EFVS Approach System based approach to 100 ft. above the TDZE.

5.2.6.3 The design assurance levels (DALs) are directly linked to the specific intended use and to the specific EFVS Approach System installation as an integrated part of the cockpit flight information system.

5.2.6.4 There are failure modes within the EFVS Approach System which determine that software and hardware DALs should be RTCA/DO-178C (or latest version). In no case should the DAL for EFVS Approach System be less than Level C. However, dependent upon the mitigations for failure conditions in the design, stemming from the specific EFVS and cockpit installations, the DALs can be higher than Level C.

5.2.6.5 The aircraft level functional hazard analysis (FHA) you prepare should determine whether the minimum required DAL level C is adequate for your specific installation. An example FHA is shown in Appendix B, but is a model case only and cannot be applied to any specific aircraft without independent analysis.

5.2.6.6 For general guidance only. An example system safety analysis (SSA) of an EFVS Approach System was performed for a certification on an instrument flight capable aircraft for straight-in landings from nonprecision and precision approach and landing operations per 14 CFR § 91.176(b) is shown in Appendix B. The applicant must provide the applicable 14 CFR §§ 23, 25, 27, and 29.1309 analysis that is specific for each installation approval.

5.2.6.7 Conduct a safety analysis to show the EFVS Approach System meets all the integrity criteria for the aircraft, HUD, and EFVS. Demonstrate system and subsystem malfunctions which are not shown to be extremely improbable as appropriate in a simulation or in flight. The malfunction annunciation and fault detection schemes must achieve the determined level of safety.

5.2.7 EFVS Landing System Required Level of Safety to support the 14 CFR §§ 23/25/27/29.1309 analysis (as applicable).

5.2.7.1 The applicant must demonstrate a satisfactory level of safety (failure and performance) appropriate to the operations being addressed, but with the visual segment primarily accomplished by the use of an EFVS Landing System rather than natural vision.

5.2.7.2 To achieve the required safety level, the minimum baseline safety levels required for the installed EFVS Landing System equipment regardless of visibility, should be dependent on the demonstrated performance.

5.2.8 System Safety Assessment to support the 14 CFR §§… › 5.2.8.2 The DALs are directly linked to the specific intended use and…

5.2.7.3 An aircraft level Functional Hazard Analysis (FHA) and System Safety Assessment (SSA) should be prepared by the applicant to assess the hazard level associated with system failure conditions and to determine the minimum required software and hardware Design Assurance Levels (DAL) based on the applicant’s specific installation. Mitigating system design features include redundancy, independent guidance display, system monitoring, pilot in the loop, pilot not flying, etc. In no case should the DAL be less than DAL C.

5.2.7.4 The minimum required safety level for an EFVS Landing System (EFVS to touchdown and roll out in visibilities not less than RVR 1000 feet) is based on the assumption that the EFVS being certified can demonstrate that the flight crew verify that the aircraft is safely approaching the runway for EFVS Landing System based landing, or, if not, to initiate a timely go around at the RVR level that the applicant is requesting. This provides additional integrity to the operation. Depending on the applicant’s design, it may be possible that the proposed visibility can also compensate for loss of EFVS imagery, such that the pilot can use the remaining symbolic flight information on the HUD and the external view to safely land. System evaluation should consider EFVS Landing System failure modes and whether the pilot can safely land and rollout with available natural vision plus whatever remains of EFVS Landing System. In no case should the pilot continue the landing if enhanced or natural vision is not at least that specified in the instrument approach procedure. A Safe landing should not be assumed with only available natural vision after total loss of EFVS Landing System (i.e., symbology and image).

Continue reading ↓ 120 of 245 passages shown