AC 20-167 Airworthiness Approval of Enhanced Vision System, Synthetic Vision System, Combined Vision System, and Enhanced Flight Vision System Equipment
a. In this advisory circular (AC), the Federal Aviation Administration (FAA) provides guidance on airworthiness approval of enhanced vision system (EVS), synthetic vision system (SVS), combined vision system (CVS), and enhanced flight vision system (EFVS) equipment installation. b. This AC provides specific system performance guidance on enhanced and synthetic vision systems and equipment. Other existing ACs address flight guidance symbology, head-up displays (HUD) and visual display characteristics (for example, AC 25-11A, Electronic Flight Deck Displays, and AC 25.1329-1B, Approval of Flight Guidance Systems). For a complete listing of related regulations and guidance, refer to appendix 9. This AC complements existing guidance. c . In this AC, terrain awareness and warning system (TAWS) refers to a system used for fixed-wing aircraft and helicopter terrain awareness and warning system (HTAWS) refers to a system used for rotorcraft. d. This AC is not mandatory and does not constitute a regulation. This AC describes an acceptable means, but not the only means, to install enhanced and synthetic vision technologies. However, if you use the means described in this AC, you must follow it in all aspects.
This document is cancelled. It may have been replaced. Check the official source before relying on it.
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: 6/22/10 Initiated by: AIR-130
AC No: 20-167
Foreword
This advisory circular (AC) provides guidance for installing 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 aircraft or rotorcraft.
Susan J. M. Cabler Assistant Manager, Aircraft Engineering Division
ii
Table of Contents
Paragraph Page
Chapter 1. Introduction … 1
Chapter 1. Introduction … 1
1-1. Purpose … 1
1-2. AC Audience … 1
1-3. Applicability … 1
1-4. How to Use This Document … 2
1-5. Cancellation … 2
Chapter 2. Vision Systems Overview … 3
2-1. Enhanced Vision System (EVS) … 3
2-2. Synthetic Vision System (SVS) … 4
2-3. Combined Vision System (CVS) … 7
2-4. Enhanced Flight Vision System (EFVS) … 8
2-4. Enhanced Flight Vision System (EFVS) … 8
Chapter 3. Airworthiness Package Contents … 11
3-1. Airworthiness Package … 11
3-2. Intended Function … 11
Chapter 4. System Requirements … 12
4-1. EVS/SVS/CVS – General Requirements … 12
4-2. EVS Specific Requirements … 15
4-3. SVS Specific Requirements … 16
4-4. CVS Specific Requirements … 20
4-4. CVS Specific Requirements … 20
4-5. EFVS – General and Specific Requirements … 21
Chapter 5. Systems Installation Considerations … 30
5-1 EVS/SVS/CVS Installation Considerations … 30
5-2. EFVS Installation Considerations … 31
5-3. HIRF Considerations … 34
Chapter 6. Performance Evaluation … 35
6-1. EVS/SVS/CVS/EFVS Performance Demonstration … 35
6-1. EVS/SVS/CVS/EFVS Performance Demonstration … 35
iii
6-2. Environmental Qualification … 36
Appendix 1. FAA EFVS 14 CFR Compliance … A1-1
1-1. Airworthiness Standards … A1-1
1-2. EFVS Compliance … A1-1
Appendix 2. EFVS Systems Safety Requirements Guidance … A2-1
2-1. General … A2-1
2-2. Required Level of Safety … A2-1
2-2. Required Level of Safety … A2-1
2-3. Demonstration … A2-2
2-4. State Data … A2-2
Appendix 3. EFVS Safety Standards … A3-1
3-1. Safety Factors for EFVS Described in this AC … A3-1
3-2. Limitations … A3-1
3-3. Features … A3-2
3-4. Demonstration … A3-2
Appendix 4. Sample EFVS Flight Test Considerations … A4-1
Appendix 5. Sample Airplane Flight Manual Supplement … A5-1
Appendix 5. Sample Airplane Flight Manual Supplement … A5-1
Appendix 6. Installation of Enhanced Vision System and/or Synthetic Vision System on Rotorcraft … A6-1
6-1. General … A6-1
6-2. Applicability … A6-1
6-3. Airworthiness Approval … A6-1
6-4. Design Considerations … A6-1
Appendix 7. Additional Part 23 Considerations for Enhanced Vision System
Appendix 7. Additional Part 23 Considerations for Enhanced Vision System
and/or Synthetic Vision System for Situation Awareness Only … A7-1
7-1. Introduction … A7-1
7-2. Terrain Alerting … A7-1
7-3. Moving Map Display that Corresponds to and Complements SV PFD…. A7-2
iv
7-4. Minimum Audio Callout Capability … A7-2
7-5. Digital Elevation Model (DEM) Resolution … A7-2
7-6. Aircraft Flight Manual Supplement … A7-3
7-6. Aircraft Flight Manual Supplement … A7-3
7-7. SVS Unusual Attitude Recovery … A7-3
7-8. Pilot Evaluation … A7-3
Appendix 8. Definitions and Acronyms … A8-1
8-1. Definitions … A8-1
8-2. Acronyms … A8-5
Appendix 9. Publications … A9-1
9-1. Related Publications … A9-1
9-2. How to Get Publications … A9-2
9-2. How to Get Publications … A9-2
List of Figures Figure Page
Figure 1. Enhanced Vision Diagram … 4
Figure 2. Synthetic Vision Diagram … 7
Figure 3. Minimum Detection Range … 23
Figure 4. Field of View … A8-3
List of Tables Table Page
Table 1. 14 CFR § 91.175 (l) Operating Requirements … 22
Table 2. System Operating Phases for Consideration … 30
Table 3. Required Level of Safety, 14 CFR part 25 Aircraft … A2-2
Table 4. Example EFVS/HUD Functional Hazard Assessment, 14 CFR part 25 Aircraft, ILS Approaches to 100 ft Height Above Touchdown, RVR 1200 ft A2-3
Chapter 1. Introduction
Chapter 1. Introduction
1-1. Purpose.
a. In this advisory circular (AC), the Federal Aviation Administration (FAA) provides guidance on airworthiness approval of enhanced vision system (EVS), synthetic vision system (SVS), combined vision system (CVS), and enhanced flight vision system (EFVS) equipment installation.
b. This AC provides specific system performance guidance on enhanced and synthetic vision systems and equipment. Other existing ACs address flight guidance symbology, head-up displays (HUD) and visual display characteristics (for example, AC 25-11A, Electronic Flight Deck Displays, and AC 25.1329-1B, Approval of Flight Guidance Systems). For a complete listing of related regulations and guidance, refer to appendix 9. This AC complements existing guidance.
c. In this AC, terrain awareness and warning system (TAWS) refers to a system used for fixed-wing aircraft and helicopter terrain awareness and warning system (HTAWS) refers to a system used for rotorcraft.
Note: A TAWS is defined in TSO-C151, Terrain Awareness and Warning System, and TSO-C194, Helicopter Terrain Awareness and Warning System. Installation of TAWS is defined in AC 23-18, Installation of Terrain Awareness and Warning System (TAWS) Approved for Part 23 Airplanes, and AC 25-23, Airworthiness Criteria for the Installation Approval of Terrain Awareness and Warning System (TAWS) for Part 25 Airplanes. Installation of HTAWS is defined in AC 27-1B, Certification of Normal Category Rotorcraft, and AC 29-2C, Certification of Transport Category Rotorcraft.
d. This AC is not mandatory and does not constitute a regulation. This AC describes an acceptable means, but not the only means, to install enhanced and synthetic vision technologies. However, if you use the means described in this AC, you must follow it in all aspects. 1-2. AC Audience. This AC is for airplane and rotorcraft manufacturers, modifiers, and type certification engineers seeking certification or installation guidance for their visual display system. 1-3. Applicability.
a. 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 equipped with SVS, EVS, CVS, or EFVS equipment.
b. 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. There is no operational credit for EVS, SVS, or CVS, unlike the credit provided for EFVS in 14 CFR §91.175(l). Installation of EFVS is associated with operational credit in accordance with 14 CFR 91.175(l). AC 90-EFVS provides operational guidance for EFVS technology.
c. Appendix 6 addresses specific installation guidance for EVS and/or SVS on rotorcraft. Appendix 7 addresses additional part 23 considerations for situation awareness only.
1-4. How to Use This Document.
a. This AC provides methods, procedures, and practices acceptable to the FAA for complying with regulations. A partial list of EFVS compliance references is listed in Appendix 1.
b. This material does not alter regulatory requirements.
c. This AC describes system performance.
d. EFVS safety standards and sample flight test considerations are in Appendix 3 and 4, respectively.
e. A sample flight manual supplement is outlined in Appendix 5.
f. Definitions and acronyms are in appendix 8.
g. Certain material within this AC is from RTCA/DO-315, Minimum Aviation System Performance Standards (MASPS) for Enhanced Vision Systems, Synthetic Vision systems, Combined Vision Systems, and Enhanced Flight vision Systems. RTCA/DO-315 is copyrighted by RTCA, Inc. and used with permission. Purchase information is in Appendix 9. 1-5. Cancellation. Advisory Circular 23-26, Synthetic Vision and Pathway Depictions on the Primary Flight Display, dated December 22, 2005, is canceled.
Chapter 2. Vision Systems Overview
Chapter 2. Vision Systems Overview
2-1. Enhanced Vision System (EVS).
a. 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 does not necessarily provide the additional flight information/symbology required in 14 CFR § 91.175(m) on a HUD or equivalent display. EVS can provide additional situation awareness, but no 14 CFR § 91.175(l) operational credit. Enhanced vision systems share a similarity with EFVS technology, but an EVS does not have to be integrated with a flight guidance system. The elements of an installed EVS are listed below, with the EVS diagram shown in Figure 1:
1. EVS sensor system. 2. Sensor display processor. 3. EVS display. 4. System installation (pilot controls/interface). 5. Aircraft installation (including the sensor window and multispectral radome).
b. The categories of current EVS sensors are passive or active (e.g., infrared thermal imaging or radar) sensors.
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 by 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. 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.
c. Unlike the pilot's external view, the enhanced vision image can be a monochrome, twodimensional 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 depends on the atmospheric and external visible and non-visible energy 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.
(Dashed lines and shading represent individual
system boundaries for EVS and EFVS)
Figure 1. Enhanced Vision Diagram
2-2. Synthetic Vision System (SVS).
a. Synthetic vision is a computer-generated image of the external scene topography from the perspective of the flight deck, 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 depiction 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 no operational credit. The application of synthetic vision systems is through a primary flight display from the perspective of the flight
Visible
External Scene Energy
Atm osphere
Sensor
Sensor C onversion
Sensor System
D isplay Processor
P ilot's Eye
Enhanced Flight Vision
System
Aircraft State
D ata
H ead-up D isplay
Processing
H ead-up
D isplay
Enhanced
Vision System
EVS D isplay
Pilot C ontrols
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.
1. Display (includes interface and installation). 2. System interface. 3. Terrain and obstacle database. 4. Position source. 5. Altitude source. 6. Attitude source. 7. Heading and track source. b. Synthetic vision coordinate referenced databases are usually referenced to digital terrain elevation data (DTED), developed by the National Imagery and Mapping Agency. 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:
1. DTED Level 0 uses 30 arc second spacing (nominally one kilometer). 2. DTED Level 1 uses 3 arc second spacing (approximately 100 meters). 3. DTED Level 2 uses one arc second spacing (approximately 30 meters).
c. With the exception of terrain and database processing (addressed in chapter 4, paragraph 4-3.g.), synthetic vision characteristics may include:
1. Display factors, such as:
(a) Conformality. (b) Refresh rate. (c) Field of regard (FOR): the amount of the outside world the sensor can see. (d) Field of view (FOV): describes how much of the sensor’s field of regard is displayed to the pilot (a function of “zoom” or magnification/minification for fixed position sensors, different from the Appendix 8 definition).
2. Display placement factors, such as:
(a) Pilot’s primary FOV versus pilot’s secondary FOV. (b) Heads down display (HDD) versus Heads up display (HUD).
3. Terrain presentation factors, such as:
(a) Depiction (such as monochromatic, photo-realistic, elevation coloring). (b) Gridding (presence versus absence, spacing).
(c) Color, shading, shadowing, and texturing. (This AC does not document standardized values for these items.)
(d) Resolution: DEM resolution and DTED level. (e) Range indication (such as terrain based range marks, color scheme).
4. Terrain and Cultural Features, such as:
(a) Rivers, valleys, and mountains. (b) Major landmarks, highways, and buildings within close proximity to airport. (c) Hue and contrast between terrain and sky. (d) Man-made obstacles (such as radio towers, bridges, tall buildings) and airport depiction.
(e) Airport depiction, including markings (for example, extended runway centerline and numbers, taxiway markings, approach lighting system).
(f) Range marks or indications.
5. Functions, such as:
(a) Alerting (terrain, obstacles, traffic, and airspace). (b) Declutter. (c) Mode reversion. (d) Image control (FOV, brightness, contrast, registration). 6. Integration of Guidance Symbology (if incorporated), such as: (a) Guidance cues (flight path vector, velocity vector, command guidance cues, deviation indicators, and trend indicators).
(b) Airplane reference relative to terrain (indication of relationship between zero pitch line and terrain).
(c) Pathway markings (breadcrumbs, rectangles) and boundaries, to indicate past or intended future aircraft track.
(d) Navigation information (course lines, fixes, icons, special-use airspace). (e) Unusual attitude recovery. (f) Crosswind indication (and image display based on cross-track).
(Dashed lines represent individual system boundaries.
External scene visible image is not affected by SVS.)
Figure 2. Synthetic Vision Diagram
2-3. Combined Vision System (CVS).
a. The CVS concept involves a combination of synthetic and enhanced systems. 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 combined vision system seeking approval. 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. CVS can provide situation awareness, but not necessarily 14 CFR § 91.175(l) operational credit.
Visible
External Scene Energy
Atmosphere
Aircraft Altitude, Attitude, Position
Database
Synthetic
Vision
Display Processing
Pilot's Eye
Display
b. This AC usually considers Combined Vision Systems as incorporating both EVS and SVS. For systems and displays incorporating both EFVS and SVS, applicants are expected to meet applicable performance criteria to EFVS and SVS. 2-4. Enhanced Flight Vision System (EFVS).
a. Under FAA regulations, an EFVS, as defined in 14 CFR §1.1, is “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, such as a forward looking infrared, millimeter wave radiometry, millimeter wave radar, low light level image intensifying.” During an instrument approach, the enhanced vision image is intended to enhance the pilot's ability to detect and identify "visual references for the intended runway" (refer to 14 CFR § 91.175(c)(3)).
b. 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 enhanced flight visibility 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.b., could be used provided it meets the performance requirements in this AC. c. The elements of an installed EFVS are defined in 14 CFR § 91.175(m), and are listed below, with the EFVS diagram in Figure 1:
1. 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, such as a forward-looking infrared, millimeter wave radiometry, millimeter wave radar, and low-light level image intensifying;
2. The EFVS sensor imagery and aircraft flight symbology (i.e., at least airspeed, 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) are presented on a head-up display, or an equivalent display, so they are clearly visible to the pilot flying in his or her normal position and line of vision and looking forward along the flight path, to include:
(a) The displayed EFVS imagery, attitude symbology, flight path vector, and flight path angle reference cue, and other cues, which are referenced to this imagery and external scene topography, must be presented so they are aligned with and scaled to the external view;
(b) The flight path angle reference cue must be displayed with the pitch scale, selectable by the pilot to the desired descent angle for the approach, and suitable for monitoring the vertical flight path of the aircraft on approaches without vertical guidance; and
(c) The displayed imagery and aircraft flight symbology do not adversely obscure the pilot's outside view or field of view through the cockpit window.
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
4. The display characteristics and dynamics are suitable for manual control of the aircraft.
d. Enhanced flight vision technology can use either stroke or raster technology.
1. Stroke 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. A raster infrared image in the center of the pilot's regulated "pilot compartment view." A "raster" image is comprised of a set of horizontal lines continuously sweeping across the display to form a picture by modulating their intensity (luminance). It must be free of interference, distortion, and glare that would adversely affect the performance of the pilot's normal performance and workload. A raster image can be more difficult for the pilot to see through than stroke-written symbols also displayed on the HUD. Unlike stroke symbology, the raster 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 raster image, but the outside scene must be visible through it.
e. Unlike the pilot's external view, the enhanced flight vision image is a monochrome, twodimensional 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.
f. 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).
1. Unlike with EFVS, an aircraft with EVS does not necessarily provide the additional flight information or symbology required by 14 CFR § 91.175(m). 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.175(m). An EVS cannot be used as a means to
determine enhanced flight visibility or to identify the required visual references in order to descend below the DA or MDA.
2. The regulations also make provision for an equivalent display. Specifically, 14 CFR § 91.175(m) states that the EFVS sensor imagery and aircraft flight symbology must be presented “…on a head-up display, or an equivalent display, so that they are clearly visible to the pilot flying in his or her normal position and line of vision and looking forward along the flight path…” An equivalent display must be some type of head-up presentation of the required information. A head-down display does not meet the regulatory requirement. A head-down display used to provide situation awareness for the pilot not flying is permitted (not required). However, this display may not be used to maneuver the airplane or to descend below DA or MDA. The FAA may require a proof of concept and then establish additional airworthiness criteria for equivalent displays.
Chapter 3. Airworthiness Package Contents
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.
a. Intended function, b. General operation, c. Performance requirements for the respective system, d. Performance evaluation plan for the respective system, and e. Installation considerations.
Note: Depending on the system (for example, EVS, SVS, CVS, or EFVS), the appropriate requirements will depend on the respective system.
3-2. Intended Function
3-2. Intended Function
a. EVS, SVS, or CVS: Define the intended functions of your EVS or 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-11A and 14 CFR § 2X.1301. b. EFVS: Clearly define the intended function of your EFVS. This must include its use to visually acquire the references required to operate below the MDA/MDH or DA/DH as described in 14 CFR § 91.175(l), and the criticality of pilot decision-making from the visible display. The purpose of the EFVS is to provide a visual advantage over the pilot’s out-thewindow view. 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 out-the-window.
Note 1: The EFVS is not intended to change the technologies or procedures already used to safely fly the aircraft down to the MDA/MDH or DA/DH. The EFVS sensor provides a visual advantage over the pilot's out-thewindow view. 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 in the EFVS than outthe-window. The EFVS complements other instrument approach equipment by providing a means for the pilot to see (with the EFVS) the required visual references that might otherwise not be visible. Note 2: While the goal of EFVS is to exceed the natural flight visibility in the majority of cases/weather conditions, there may be cases where the EFVS does not provide a significant advantage.
Chapter 4. Systems Requirements
Chapter 4. Systems Requirements
4-1. EVS or SVS (or CVS when EVS and SVS combined) – General Requirements.
a. 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.
b. 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 stand-alone 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.
c. EVS, SVS, or CVS installed on side-mounted displays: While similar in concept to the MFD, side-mounted EFB systems are, in general, limited due to the nature of the installation constraints of these devices. EFB using EVS technologies can present unique certification challenges such as alignment or positioning concerns relating to the EFB installation. (See AC 120-76A, for specific applications.)
d. The intended function for any installation of EVS/SVS/CVS must be clearly defined (appropriate 14 CFR § 2X.1301), and the design and installation safety levels should 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.
e. Although EVS/SVS/CVS installations do not provide additional operational credit the proposed system (EVS, SVS, and/or CVS) must:
1. Have a means to automatically or manually control display brightness. 2. 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.
3. Continue to meet requirements of original approval, if applicable (i.e., display system modified to display EVS/SVS/CVS).
4. Not adversely affect any other installed aircraft system. 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.
6. 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.
7. Not have undesirable display characteristics (for example, jitter, jerky motion, and excessive delays).
f. Display implementation. EVS/SVS/CVS can be incorporated into differing display types installed in the cockpit. There are unique tactical and strategic requirements for each of these displays. AC 25-11A and AC 23.1311-1 provide more information on electronic displays. The display is subject to all applicable primary flight information rules and guidance for the category of aircraft.
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 requirements apply to EVS/SVS/CVS implemented on a PFD.
(a) The image, or loss thereof, must not adversely affect the PFD functionality. (b) Align the displayed image with the airplane’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 airplane’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 must be consistent with the real world and appropriate for the system’s intended function accounting for possible aircraft attitudes, turbulence, and wind effects.
(c) Scale and align all spatially referenced symbology within each axis with the imagery so as not to present any misleading information to the pilot.
(d) 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 §§ 2X.771 and 2X.1309.)
(e) The display must 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: Consider including a flight path vector or velocity vector to show the pilot the aircraft’s trajectory relative to displayed terrain.
(f) Per 14 CFR 2x.771 and 2x.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.
2. Head-Up Display. EVS/SVS/CVS can be implemented on a HUD or equivalent. The following requirements apply to EVS/SVS/CVS implemented on this display:
(a) A design with EVS/SVS/CVS imagery displayed on a HUD 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 EVS imagery does not conflict with the pilot compartment view. For part 25 airplanes, the FAA will issue special conditions to achieve the intended level of safety in 14 CFR § 25.773. 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:
(1) Detection, accurate identification and maneuvering, as necessary, to avoid traffic, terrain, obstacles, and other hazards of flight.
(2) 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 during ground operations should be considered if sensor proximity to the taxiway surface causes a distraction.
(b) The safety and performance of the pilot tasks associated with the use of the pilot compartment view must not be degraded by the display of imagery on the HUD. Per 14 CFR § 2X.773, pilot tasks which must not be degraded by the imagery include:
(1) Detection, accurate identification, and maneuvering, as necessary, to avoid traffic, terrain, obstacles, and other hazards of flight.
(2) Accurate identification and utilization of visual references required for every task relevant to the phase of flight.
(c) Imagery on the HUD must be conformal with the real world and appropriate for the system’s intended function accounting for possible aircraft attitudes, turbulence, and wind effects.
(d) 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.
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 Multi-Function Displays (MFD). The following requirements apply to EVS/SVS/CVS implemented on secondary displays:
(a) The orientation and perspective of the EVS/SVS/CVS view must be clear to the pilot.
(b) If PFD information is displayed, it should meet PFD integrity and availability requirements.
(c) 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 Requirements.
a. 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.
b. EVS installations must meet the following requirements:
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, provide a control which permits the pilot flying to deactivate and reactivate the display of the EVS image on demand without removing the pilot’s hands from the primary flight controls (yoke or equivalent) or thrust control.
2. The display mode (status of EVS), either through crew de-selection or as a result of a failure, must be clearly indicated or obvious to the crew.
3. The display and sensor FOR should be sufficient for the intended functions. 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.
5. Consider the following requirements for display characteristics for the EVS design, regardless of the display type:
(a) For part 25 airplanes, apply all display characteristics listed in AC 25-11A. For part 23 airplanes, apply all display characteristics listed in AC 23.1311-1. For other aircraft without corresponding criteria, the guidance in AC 25-11A or AC 23.1311-1 serves as recommended guidance.
(b) The display should not have undesirable display characteristics (such as blooming, “burlap,” and running water).
6. Image Characteristics
6. Image Characteristics
(a) 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.
(b) The image data must be refreshed at 15 Hz or better.
(c) The image latency must 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 refresh rate, when used in direct airplane 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 airplane control task 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 airplanes with conventional control system response is generally acceptable.
7. For display on a HUD, the minimum system must include:
(a) A control of EVS display contrast/brightness which is effective in dynamically changing background (ambient) lighting,
(b) Prevents distractions to the pilot, prevents impairment of the pilot’s ability to detect and identify visual references,
(c) Prevents masking of flight hazards, or otherwise (d) Degrades task performance or safety.
4-3. SVS Specific Requirements.
a. 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-11A and AC 23.1311-1 provide additional general display guidance.
b. Image characteristics:
1. Failure or deselection of the synthetic vision depiction must be obvious to the crew. 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 must depict the scene from the pilot’s perspective looking through the front window.
3. The 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 heading and not to track). Synthetic vision scene compression can result from FOR selections or display size limitations. Regardless, prominent topographical features must be easily identified and correlated with the actual external scene.
4. Identify dominant topographical features present in the SVS image in the outside view. The converse is also a requirement; dominant topographical features present in the outside view should be identifiable in the SVS image.
5. Terrain:
(a) A potential terrain or obstacle conflict must be obvious to the pilot, and 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 requirements and guidance regarding alerts, use AC 23.1311-1 or AC 25.1311.
(b) Displayed topographical features must not intersect guidance provided to the pilot to fly a published approach path. Terrain and 3-space position resolution must be accurate enough that topographical features must not intersect published approach paths.
(c) 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.
6. SVS based primary displays 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, 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-11A. For 14 CFR part 23 aircraft, refer to appendix 7.) 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.
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.
8. The terrain depiction should include large bodies of water and rivers. Differentiation between water and sky depictions must be clearly distinguishable.
9. The pilot’s view must not be depicted below the earth’s surface. 10. The image must be updated at 15 Hz or better and function smoothly during all expected maneuvering reasonable for the class and type of aircraft.
11. The image latency for a PFD or HUD must be consistent with the image requirements of AC 25-11A 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.
12. Undesirable display characteristics must be minimized (for example, jitter, jerky motion, and excessive delays).
13. Range:
(a) 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 must be whichever is less of the following: natural horizon, 40 nautical miles, or 10 minutes at maximum cruise speed.
(b) The scene range from the eye position to the terrain horizon must not be misleading and must be appropriate to the intended function. One example that this requirement is trying to prevent is 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 look like it is in the plains until short final when the mountains in the distance finally start appearing on the PFD.
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.
15. All obstacles taller than 200 feet above ground level must be displayed conformally on the synthetic vision image.
Note: Obstacle display consideration should be given to reducing clutter when objects pose no threat, yet not causing a sudden appearance at low altitudes during periods of task saturation. c. 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 requirements 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.
1. The synthetic vision display must not conflict with either the terrain warning or terrain awareness functions (for example, TAWS or HTAWS).
2. Any aircraft incorporating SVS from the egocentric perspective must also provide a TAWS or HTAWS or terrain warning system (refer to appendix 7 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.
d. 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 requirements for the altitude 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, AC 29-2C, and TSO-C194, Helicopter Terrain Awareness and Warning System.
e. Attitude Source. The attitude source must not conflict with attitude information or integrity requirement provided by the primary flight display.
f. Heading/Track Source. The heading/track source must not conflict with heading/track information provided by the navigation display.
g. Terrain and Obstacle Database.
1. Terrain and obstacle database processing. The terrain and obstacle database, along with any other database used to create the SVS image must 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 comply with the resolution and accuracy listed in TSO-C151, appendix 1, section 6.3, or for helicopters, comply with TSO-C194, Helicopter Terrain Awareness and Warning System.
(a) Position accuracy, symbology, and topographical information should be consistent with each other.
(b) Runway elevations must be accurate at the approach ends and not just at the airport center.
2. Obstacle Database. The obstacle database must include all available physical hazards greater than 200 feet above ground level, not just terrain. The system must neither disregard nor corrupt obstacles available in the database greater than 200 feet above ground level. Obstacles displayed must 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.
3. Navigation Database. The navigation database used by SVS for runway and airport information must be consistent with that used by other systems in the airplane (for example, flight management systems). The applicant should provide procedures to document database currency in the Instructions for Continued Airworthiness.
4. Features. If flight path guidance features are provided by the SVS, they must complement (or correspond with) approved navigation system guidance.
5. Head-Up Displays. Providing complete guidance for SV systems is complicated by the many design variables available to manufacturers. Since SV displays can share many characteristics with a HUD, applicants should use HUD display guidance where appropriate.
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 field-of-view limited, may still adequately portray terrain awareness. The pilot should be aware of less than a 1:1 ratio of depiction. Display suitability must be matched against intended function. 4-4. CVS Specific Requirements.
a. 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 requirements apply to CVS installations:
1. CVS must meet the respective requirements of the EVS and SVS implementations. 2. The EVS and SVS depictions must be conformal with each other. 3. Fusion of EVS and SVS must 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 must not cause confusion to the flight crew. Image discrepancies between EVS and SVS due to failure conditions must 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. b. The CVS must meet the detailed performance requirements for EVS and SVS specified in paragraphs 2 and 3 of this chapter. 4-5. EFVS – General and Specific Requirements. a. EFVS requirements would meet EVS requirements. However, there are additional EFVS general and specific requirements needed to be eligible for operational credit, as follows:
1. Mitigate system failures more frequent than extremely improbable which produce effects the pilot (or the aircraft itself) can not safely handle. Design the aircraft systems so the entire fault probability is kept to an acceptable level, which is normally accomplished by redundancy and system monitoring.
2. The sensor image, combined with the required aircraft state and position reference symbology, is presented to the flight crew on the HUD or other appropriate, equivalent display. For HUD 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.
3. The HUD 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 must include:
(a) Airspeed; (b) Vertical speed; (c) Aircraft attitude; (d) Heading; (e) Altitude; (f) Command guidance as appropriate for the approach to be flown; (g) Path deviation indications; (h) Flight path vector; and (i) Flight path angle reference cue. 4. The minimum system must 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 must be shown that manual setting of image brightness meets the above criteria and does not cause excessive workload.
5. The EFVS display controls must be visible to, and within reach of, the pilot flying from any normal seated position. The position and movement of the controls must not lead to
inadvertent operation. The EFVS controls, except those located on the pilot’s control wheel, must be adequately illuminated for all normal background lighting conditions, and must not create any objectionable reflections on the HUD or other flight instruments. Unless fixed illumination of the EFVS controls is shown to be satisfactory under all lighting conditions for which approval is sought, there must be a readily accessible control provided that permits the pilot to immediately deactivate or reactivate the display of the EFVS image on a HUD. This control must be on demand without removing the pilot’s hands from the primary flight controls (yoke or equivalent) and thrust control.
6. Base the approach path situation information references and command guidance information on the navaids dictated by the straight-in instrument approach procedure in use.
7. Under FAA regulations, as defined in 14 CFR § 91.175, upon reaching the decision altitude/decision height (DA/DH) or minimum descent altitude/minimum descent height (MDA/MDH), the required visual references presented in figure 3 must be distinctly visible and identifiable to the pilot.
Table 1. 14 CFR § 91.175 (l) Operating Requirements
In order to operate an aircraft below DA/DH/MDA/MDH down to 100 feet height above TDZE, the following visual references for the intended runway shall be distinctly visible and identifiable to the pilot using the enhanced flight vision system: i. Approach light system, if installed; OR ii. visual references in BOTH paragraphs (l)(3)(ii)(A) and (B) -- (l)(3)(ii)(A) Runway threshold, identified by at least one of the following – -- beginning of the runway landing surface, -- threshold lights, or -- runway end identifier lights AND (l)(3)(ii)(B) Touchdown zone, identified by at least one of the following – -- runway touchdown zone landing surface, -- touchdown zone lights, -- touchdown zone markings, or -- runway lights. 8. In terms of sensor design requirements, sensor performance criteria can be quantified in terms of the range of the enhanced flight visibility when low visibility conditions exist. The visual references of the runway environment must be seen by the sensor at operationally relevant distances.
9. The minimum detection EFVS range (figure 3, below) can be derived by using an assumed minimum distance of the aircraft at the nominal Category I (200 ft) decision altitude before which the EFVS must 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 requirement. These values do not take into account pilot decision time or actual atmospheric conditions, or the use of non precision approaches which can require greater distances.
Figure 3. Minimum Detection Range
10. There is the potential for the image to improve the pilot's ability to detect and identify items of interest. The EFVS needs to be evaluated to determine that the imagery does not adversely affect the pilot's ability to see outside the window through the image. 14 CFR § 25.773(a)(2) states: Each pilot compartment must be free of glare and reflection that could interfere with the normal duties of the minimum flight crew.
11. The EFVS imagery displayed on the HUD 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. For part 25 airplanes, the FAA issues special conditions to provide regulatory means to approve EFVS video imagery on the HUD with an equivalent level of safety to 14 CFR § 25.773. Video imagery on the HUD must not degrade the safety of flight or interfere with the effective use of outside visual references for required pilot tasks during any phase of flight in which it is to be used. 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:
(a) Detection, accurate identification and maneuvering, as necessary, to avoid traffic, terrain, obstacles, and other hazards of flight.
(b) 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 during ground operations should be considered if sensor proximity to the taxiway surface causes a distraction.
b. EFVS System Requirements
1. The EFVS 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). The HUD and EFVS FOR must provide a conformal image with the visual scene over the range of aircraft attitudes and wind conditions for each mode of operation.
2. EFVS display criteria must meet the airworthiness certification requirements in 14 CFR parts 21, 23, 25, 27, and 29 (as applicable). Specifically, the EFVS system installation and operations must demonstrate compliance with the requirements listed in Appendix 1, EFVS compliance checklist. These requirements are specific to EFVS and are in addition to all other requirements applicable to the HUD and the basic avionics installation.
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-11A. 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. The EFVS image, when superimposed on the HUD symbology and when used in combination with other airplane systems, must meet the requirements below. The EFVS image and installation:
(a) Must be suitable for and successfully perform its intended function.
(b) Must allow the accurate identification and utilization of visual references, using both EFVS and natural vision as appropriate.
(c) Must not degrade safety of flight.
(d) Must not have unacceptable display characteristics.
(e) Must have an effective control of EFVS display brightness without causing excessive pilot workload.
(f) Must have a readily accessible control to remove EFVS image from the HUD.
(g) Must not degrade the presentation of essential flight information on the HUD.
(h) Must not be misleading and must not cause confusion or any significant increase in pilot workload.
(i) Must be aligned and conform to the external scene, including the effect of near distance parallax.
(j) Must not cause unacceptable interference with the safe and effective use of the pilot compartment view.
(k) Must not cause adverse physiological effects such as fatigue or eyestrain.
(l) Must not significantly alter the color perception of the external scene.
(m) Must allow the pilot to recognize misaligned or non-conformal conditions.
5. A HUD modified to display EFVS must continue to meet the requirements 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, quick-glance 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-11A for guidance on electronic flight deck displays.
6. As outlined in 14 CFR § 91.175, a flight path vector and flight path angle reference cue must be displayed on the HUD (or equivalent display). The position of the flight path vector symbol must correspond to the aircraft’s earth referenced flight path vector. The dynamic response of the flight path vector symbol must follow pilot control inputs. Follow the dynamic response requirements for the flight path vector symbology in SAE ARP 5589.
c. EFVS Detailed System Requirements
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.
2. Since the purpose of the EFVS sensor is to provide a visual advantage over the pilot’s out-the-window view, the design must 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. Use standard means of performance calculations.
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 must include the calculated transmission of electromagnetic energy in the visible spectrum and other frequencies that can assess 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 defined in 14 CFR § 91.175. 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.
(a) 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, as a general requirement, should not be discernable 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.
(b) EFVS FOR. The minimum fixed FOR must be 20 degrees horizontal and 15 degrees vertical. In applications where the FOR is centered on the flight path vector the minimum vertical FOR must be 5 degrees (± 2.5 degrees) and 20 degrees horizontal.
(1) The requirement for a 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:
(i) HUD and EFVS sensor Field-Of-View;
(ii) Orientation of the HUD with respect to the aircraft frame of reference (for example, boresight and proximity to pilot’s eye); and,
(iii) Orientation (for example, attitude) of the aircraft.
(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 can not be used throughout the full aircraft flight envelope.” A quantitative EFVS FOR requirement 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 requirements for various aircraft attitudes and wind conditions using a critical altitude of 200 ft height above touchdown zone elevation for EFVS visibility.
(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.
(c) Off-axis Rejection. A source in object space greater than 1 degree outside the FOV must 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.
(d) Jitter. When viewed from the HUD eye reference point, the displayed EFVS image jitter amplitude must 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.
(e) Flicker. Flicker is brightness variations at frequency above 0.25 Hz per SAE ARP 5288. The minimum standard for flicker must meet the criteria of SAE ARP 5288. Flicker can cause mild fatigue and reduced crew efficiency. This requirement implies the EFVS and HUD cannot exhibit flicker greater than that of the HUD itself.
(f) 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 must minimize unacceptable 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.
(g) Image Conformality. The accuracy of the integrated EFVS and HUD image must 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 bore sight must 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 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 glidepath as the pilot flies the flight path vector and Glidepath Reference Line toward the EFVS image of the runway.
(h) Sensor/Sensor Processor.
(1) Dynamic Range. The minimum required dynamic range for passive EFVS must be 48 db. For active EFVS, side lobes must be 23 db below the main beam, and 40 db dynamic range plus sensitivity time control (STC).
(2) Sensor Image Calibration. Visible image calibrations and other built-in tests that cannot be achieved within a total latency of 100 milliseconds must 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 requirement 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.
(3) Sensor Resolution. As a minimum, the sensor resolution performance requirement shall adequately resolve (for pilot identification) the runway threshold and the touchdown zone to enable the intended function. For example, a radar-based EFVS should resolve a 60 ft wide runway from 200 ft height above touchdown zone elevation with a typical 3degree glide slope. The required 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 non precision 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) Passive Sensor Optical Distortion. Optical distortion must be 5 percent or less across the minimal FOR as defined in paragraph 4-5.c.(4)(b) and no greater than 8 percent outside the minimal FOR.
(5) Sensor Sensitivity. In this context, the EFVS sensor sensitivity must 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.
(6) Failure Messages. EFVS malfunctions detected by the system, and which can adversely affect the normal operation of the EFVS, must be annunciated. As a minimum, specific in-flight failure message(s) for sensor failure and frozen image must be displayed to the flight crew.
(7) Blooming. The sensor must incorporate features to minimize objectionable 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 discernable is unacceptable.
(8) Image persistence. The image persistence time constant must 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), must be removed from the image to comply with paragraph 4-5, c.(4)(f), Image Artifacts, by a secondary on-demand process (for example, the NUC process).
(9) Dead Pixels. Dead pixels or sensor elements replaced by a “bad pixel” replacement algorithm must 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 shear number and closely-spaced location of the element.
Chapter 5. Systems Installation Considerations
Chapter 5. Systems Installation Considerations
5-1. EVS/SVS/CVS Installation Considerations.
a. EVS/SVS/CVS Pilot Controls.
1. The EVS/SVS/CVS display controls must be visible to, and within reach of, the pilot flying from any normal seated position. The position and movement of the controls must not lead to inadvertent operation.
2. The EVS/SVS/CVS controls, except those located on the pilot’s control wheel, must be adequately illuminated for all normal background lighting conditions and must not create any objectionable reflections on other flight instruments.
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.
b. EVS/SVS/CVS Preventive Maintenance Requirements. Use manufacturer data for preventive maintenance requirements (for example, Instructions for Continued Airworthiness, per 14 CFR § 21.50 and FAA Order 8110.54).
c. 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.
d. EVS/SVS/CVS System Safety Design Criteria. The overall safety requirement of the aircraft is based on installed equipment. A complete fault hazard analysis (FHA) and system safety analysis (SSA) should be conducted to identify failure modes and classify the hazard levels. To meet the safety criteria, 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.
e. EVS/SVS/CVS Required Safety Level.
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 Effects Analysis (FMEA). Any failure or malfunction that could cause misleading synthetic vision depiction should be immediately annunciated and the synthetic vision depiction should be removed.
2. The applicant should perform a FHA, SSA, etc., 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 HMI would be the aircraft
level ramifications of a “frozen EVS/SVS/CVS display” that is undetected by the flight crew. In general, the sensor or system requirements and level of design must be consistent with the SSA.
3. 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 requirements shall 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.
4. The normal operation of the EVS/SVS/CVS may not adversely affect, or be adversely affected by other normally operating airplane systems. 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 part § 2x.1309, AC 25-11A chapter 4, and AC 2x.1309. 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 § 2x.1309, AC 25-11A chapter 4, and AC 2x.1309. As applicable, similar criteria is found in SAE ARP 4754, and ARP 4761.
Table 2. System Operating Phases for Consideration
GROUND (1) Taxi, (2) Maintenance
TAKEOFF (1) Takeoff Roll
Prior to V1, (2) Takeoff Roll
After V1, (3) Takeoff After VR
to 200', (4) Rejected Takeoff
IN-FLIGHT (1) Climb, (2) Gear Up, (3) Cruise, (4) Descent, (5) Gear Down, (6) Approach 200' to 0', (7) Go Around
LANDING (1) Touchdown &
Rollout, (2) Taxi
f. EVS/SVS/CVS Environmental Specifications. The EVS/SVS/CVS must meet all specified operating requirements and must provide required operating performance, life and reliability when operating within the aircraft and subsystem flight envelope as specified in RTCA/DO-160F (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. 5-2. EFVS Installation Considerations.
a. EFVS Annunciations. Any modes of EFVS operation must 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.
b. EFVS Display
1. Display Resolution of the HUD. Since the sensor can be active or passive, the EFVS display must 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.
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.
c. EFVS Maintenance Requirements. Instructions for Continued Airworthiness are to be furnished after final design approval (reference 14 CFR § 21.50 and FAA Order 8110.54).
d. 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.
e. EFVS System Safety Design Criteria.
1. The overall safety requirement 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 will be demonstrated through analysis and engineering tests to 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.
(a) The EFVS system must perform its intended function for each operation and phase of flight that it would use.
(b) The normal operation of the EFVS cannot adversely affect, or be adversely affected by other airplane systems. Annunciate detected malfunctions of the EFVS system and remove the malfunctioning display elements.
2. Table 3 lists the categories of systems and failure probabilities to meet the safety requirements required in 14 CFR part 25 airplanes (AC 25.1309-1). For 14 CFR part 23 aircraft, similar information can be found in 14 CFR §23.1309 and AC 23.1309. The relationship among airplane classes, probabilities, severity of failure conditions and software development assurance levels is found in AC 23.1309-1C. The following additional guidance helps assess the criticality of the EFVS display, including the potential to display HMI:
(a) Applicable 14 CFR § 2X.1309, (b) AC 25-11A (chapter 4), (c) AC 23.1311-1, and (d) AC 27-1B and AC 29-2C, as appropriate for the installation.
3. Validate all alleviating flight crew 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.
f. EFVS Required Safety Level.
1. When you are designing an EFVS, 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 the overall safety requirement of 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 that pilot indeed 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 must be demonstrated that pilots will indeed detect the error in a timely fashion and not be hazardously misled. The demonstration must validate the proposed hazard classification of Major or Minor, as applicable (see Appendix 2, Table 3).
2. You must demonstrate a satisfactory safety (failure and performance) level which must not be less than the safety level required for non-EFVS based precision and non-precision approaches with decision altitudes of 200 ft or above. In showing compliance with these safety requirements, probabilities cannot be factored by the portion of approaches which are made using EFVS. Consideration, however, can be given to the EFVS critical flight time, such as from the highest DH that can be expected for an EFVS based approach to 100 ft above the TDZE.
3. The required design assurance levels (DALs) are directly linked to the specific intended use and to the specific EFVS installation as an integrated part of the cockpit flight information system.
4. There are failure modes within the EFVS which determine that software and hardware DALs must be RTCA/DO-178B level C (major) as a minimum. However, dependent upon the mitigations you utilize, stemming from the specific EFVS and cockpit installations, the DALs required can be higher than this minimum level.
5. The airplane level functional hazard analysis (FHA) you prepare must determine whether the minimum required DALs of level C are adequate for your specific installation. An example FHA is shown in Appendix 2, but is a model case only and cannot be applied to any specific aircraft without independent analysis.
6. A system safety analysis (SSA) of an EFVS was performed for a certification on an instrument flight capable airplane for straight-in non-precision and precision approach and landing operation per 14 CFR §91.175(l) and (m). This SSA is shown in appendix 2 for example and general guidance only. You must provide the applicable 14 CFR §§ 23, 25, 27, and 29.1309 analysis.
7. Conduct a safety analysis to show the EFVS meets all the integrity requirements for the airplane, 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 satisfy the required level of safety.
g. EFVS Fail Safe Features. The normal operation of the EFVS may not adversely affect, or be adversely affected by other normally operating airplane systems. Malfunctions of the EFVS which could cause display of misleading information must be annunciated and the misleading information removed. The criticality of the EFVS’s function to display imagery, including the potential to display hazardously misleading information, should be assessed according to 14 CFR § 25.1309, AC 25-11A chapter 4, and AC 25.1309-1A. Likewise, the hazard effects of any malfunction of the EFVS that could adversely affect interfaced equipment or associated systems should be determined and assessed according to 14 CFR § 25.1309, AC 25-11A chapter 4, and AC 25.1309-1A. As applicable, similar criteria is found in 14 CFR § 23.1309, and AC 23.1309-1C. This requirement must be met through a system safety assessment and documented via FTA, failure mode and effects analysis (FMEA), and failure mode and effects analysis substantiation (FMEA Substantiation), or equivalent safety documentation.
h. EFVS Environmental Specifications. The EFVS must meet all specified operating requirements and must provide required operating performance, life and reliability when operating within the aircraft and subsystem flight envelope as specified in RTCA/DO-160F (as revised) Environmental Conditions and Test Procedures for Airborne Equipment, or future versions. These criteria must also include the HIRF, EMI and lightning requirements as specified in the certification basis of the aircraft to be installed. 5-3. HIRF Considerations for All Installations (EVS, SVS, CVS, and EFVS).
a. The immunity of critical avionics/electronics and electrical systems to High-Intensity Radiated Fields (HIRF) must be established. Critical functions are those whose failure would contribute to or cause a failure condition that would prevent the continued safe flight and landing of the airplane. Refer to AC 20-158, The Certification of Aircraft Electrical and Electronic Systems for Operation in the High-Intensity Radiated Fields (HIRF) Environment, for compatibility with other systems.
b. New avionics/electronics and electrical systems performing critical functions should be designed and installed to preclude component damage and interruption of function due to both the direct and indirect effects of HIRF. For these systems, compliance must be shown to 14 CFR §§ 23.1308(a), 25.13l7(a), 27.13l7(a), or 29.1317(a), as appropriate.
Note: AC 20-158 (paragraph 6) provides guidance on Approaches to Compliance.
Chapter 6. Performance Evaluation 6-1. EVS/SVS/CVS/EFVS Performance Demonstration.
a. The performance demonstration, establishing aircraft system compliance with applicable FAA regulations, will require bench testing, flight testing, data collection, and data reduction to show that the proposed performance criteria can be met. Minimal performance standards require an evaluation of the system used during anticipated operational scenarios. The performance evaluations should therefore include demonstrations of taxi, take-off, approach, missed approaches, failure conditions, cross wind conditions, and approaches into specific airports as appropriate for the system’s intended function. For EFVS, the applicant must demonstrate performance at the lateral and vertical limits for the type of approach (for example, precision, nonprecision, and approach with vertical guidance) credit being sought. Appendix 4 provides sample EFVS flight test considerations.
b. No specific test procedures are cited, as it is recognized that alternative methods can be used. Alternate procedures can be used if it can be demonstrated that they provide all the required information. System performance tests as they relate to operational capability are the most important tests. Subsystem tests are used as subsystems are added during system buildup to ensure appropriate subsystem performance as it relates to overall system performance.
c. Use any of these four general verification methods (refer to AC 25.1329-1):
1. Analysis – demonstrate compliance to the requirement with an engineering analysis.
2. Flight Test – demonstrate compliance to the requirement on an appropriate aircraft (in the air or on the ground).
3. Laboratory Test – demonstrate compliance to the requirement on an engineering bench representative of the final EVS/SVS/CVS/EFVS system being certified.
4. Simulation – demonstrate compliance to the requirement in a flight simulator. d. Specify the individual verification methods that you use in the certification plan. Confirm the appropriate certification office agrees with your plan before you begin. For extensions, features, and design decisions not explicitly specified in this AC, conduct human factors evaluations. Conduct these evaluations through bench, simulation, or flight testing.
e. Verify both the installed system and the individual system components meet the EVS/SVS/CVS/EFVS requirements described in Chapter 4.
f. Demonstrate general requirements by flight test and other appropriate means, which can include use of a flight simulator. An example of a flight test program that would satisfy these minimum requirements for EFVS is described in appendix 4 in this AC. The flight test program assumes that the guidance system utilized to satisfactorily position the airplane at the DA/DH has been separately tested and shown to fully perform its intended function. Testing and data
collection to demonstrate this is not part of this document.
g. Airframe and equipment manufacturer based tests or analysis as applicable must be developed and conducted to validate the detailed system requirements. No specific test procedures are cited because alternative methods can be used. You can use alternate procedures if you can demonstrate that they provide all the required information. System performance tests as they relate to operational capability are the most important tests. Subsystem tests are used as subsystems are added during system buildup to ensure appropriate subsystem performance as it relates to overall system performance.
h. Minimal performance standards require an evaluation of the system used during anticipated operational scenarios.
6-2. Environmental Qualification.
a. Installed equipment meets the requirements in RTCA/DO-160F (as revised), Environmental Conditions and Test Procedures for Airborne Equipment.
b. Design Assurance.
1. Follow the requirements of RTCA/DO-178B, Software Considerations in Airborne Systems and Equipment Certification, to conduct software design assurance tests. The issue must be current at time of application.
2. Follow the requirements of RTCA/DO-254, Design Assurance Guideline for Airborne Electronic Hardware, to conduct hardware design assurance tests, if applicable. The issue must be current at time of application.
Appendix 1. FAA EFVS 14 CFR Compliance (Partial List)
Appendix 1. FAA EFVS 14 CFR Compliance (Partial List)
1-1. Airworthiness Standards: This appendix does not supersede the following airworthiness standards:
a. Certification Procedures for Products and Parts (14 CFR part 21). b. Normal, Utility, Acrobatic, and Commuter Category Airplanes (14 CFR part 23). c. Transport Category Airplanes (14 CFR part 25). d. Normal Category Rotorcraft (14 CFR part 27). e. Transport Category Rotorcraft (14 CFR part 29). 1-2. EFVS Compliance. The following requirements address EFVS and are in addition to HUD requirements. The amount of new test data can be determined by the individual application, availability, and relevance of data.
14 CFR § Description Acceptable Method of
14 CFR § Description Acceptable Method of
Compliance
23/25/27/29.1 Applicability
23/25/27/29.251 Vibration and Buffeting Flight Test
23/25/27/29.301 Loads Analysis
23/25/27/29.303 Factor of safety Analysis
23/25/27/29.307 Proof of structure Analysis
25.561/25.562(c)(5)) General Emergency Landing Conditions; Head Injury Criterion (HIC)
Analysis
25/27/29.571 and 23.573 Damage-tolerance Analysis
25.571(e) Damage Tolerance (discrete source) evaluation
Analysis and/or Test (See Note)
14 CFR § Description Acceptable Method of Compliance
14 CFR § Description Acceptable Method of Compliance
25.581 Lightning Protection Analysis
23/25/27/29.601 General Drawing
23/25/27/29.603 Materials Drawing
23/25/27/29.605 Fabrication methods Drawing
23/25/27/29.609 Protection of structure Drawing
23/25/27/29.611 Accessibility provisions Drawing
25.581 Lightning Protection Analysis
23/25/27/29.613 Material Strength properties and material design values
Drawing, Analysis, Test (See Note)
23/25/27/29.619 Special factors Analysis
23/25/27/29.625 Fitting Factors Analysis
25.629 (d)(8) Aeroelastic stability requirements Analysis, Test
25.631 Bird Strike Damage Analysis, or test if necessary. (Testing is required unless the analysis shows that the integrity of the original structure has not been compromised by EFVS installation modification.)
23/25/27/29.771 Pilot compartment Flight Test
23/25/27/29.773 Pilot compartment view Flight Test
23/25/27/29.777 Flight deck controls Flight Test
23/25/27/29.1301 Function and installation Flight Test
23/25/27/29.1309 Equip, systems, and install Analysis/Data
14 CFR § Description Acceptable Method of Compliance
14 CFR § Description Acceptable Method of Compliance
25.1316 System lightning protection Ground Test
23.1308, and 25/27/29.1317 High Intensity Radiated Fields Analysis/Data
23/25/27/29.1321 Arrangement and visibility Flight Test
23/25/27/29.1322 Warning, caution, advisory lights Flight Test
25.1323 Airspeed indicating systems Flight Test
25.1335 Flight director systems Flight Test
23/27.1351 General, Electrical Systems and Equipment
Analysis
25/29.1353 Electrical equipment and installation Analysis
23/25/27/29.1357 Circuit protective devices Analysis/Ground Test
23/25/27/29.1381 Instrument lights Flight Test
23/25/27/29.1419 Ice Protection Analysis
23/25/29.1431(a)(c) Electronic equipment Analysis
23/25/27/29.1459(e) Flight data recorders Flight test
23/25/27/29.1501 General (operating limitations) Flight Test
23/25/27/29.1525 Kind of Operation Flight Test
23/25/27/29.1529 Instructions for Continued Airworthiness
Data
23/25/27/29.1581 Aircraft flight manual Data/Flight Test
14 CFR § Description Acceptable Method of Compliance
23/25/27/29.1583 Operating limitations Data/Flight Test
23/25/27/29.1585 Operating procedures Data/Flight Test
26.47 Holders of and applicants for a supplemental type certificate - alterations and repairs to alterations.
Analysis
Note: In some cases, previously approved test data for the airplane may be resubmitted for compliance to some or all of the test requirements, if analysis can establish that the data remains valid for the airplane with the new modification.
Appendix 2. EFVS Systems Safety Requirements Guidance
Appendix 2. EFVS Systems Safety Requirements Guidance
2-1. General.
a. Safety criteria. Safety criteria for approach and landing systems generally consider four elements: accuracy, continuity, availability, and integrity. These criteria apply to both the external navigation systems as well as airborne navigation equipment. Trajectory management or flight technical error, which can be interpreted as signal structure contributing to roughness, bends and scalloping of ILS-based guidance, must also be considered. They also define how the airspace and aircraft are integrated together to make a safe approach and landing. The FAA developed, in conjunction with the other governments, definitions related to safety and performance for a landing system.
b. Transport Category Airplanes. 14 CFR § 25.1309 and AC 25.1309 define the safety requirements for any aircraft systems, and the means for verifying that they are met. The overall safety requirement of each catastrophic failure condition must be 10 -9 or less per flight hour considering any mode of flight, any combination of failures causing an unsafe condition, and including the probability of the crew to cope with the failures. The FAA accepts this number to assure a negligible adverse effect on accident rates, and to help reduce them as new systems come on line.
c. General Aviation or Non-Transport Category Airplanes. Similar information can be found in 14 CFR § 23.1309 and AC 23.1309. The relationship among airplane classes, probabilities, severity of failure conditions and software development assurance levels is found in AC 23.1309-1.
2-2. Required Level of Safety. The required level of safety for any aircraft systems, therefore, depends on the ability of the crew to cope with failures as shown in Table 3, which lists the categories of systems and failure probabilities to meet the safety requirements required in 14 CFR parts 23 and 25 airplanes. For part 23 airplane, similar information can be found in 14 CFR §23.1309 and AC 23.1309. The relationship among airplane classes, probabilities, severity of failure conditions and software development assurance levels is found in AC 23.1309-1D.
Table 3. Required Level of Safety, 14 CFR part 25 Aircraft
Required Level of Safety, 14 CFR part 25 airplanes
Classification Effect Target Probability P
Minor Slight reduction in safety margins or functional capabilities. Slight increase in crew workload. Some inconvenience to occupants.
1E-3 > P > 1E-5
Major Significant reduction in safety margins or functional capabilities. Significant increase in crew workload or in conditions impairing crew efficiency. Some discomfort to occupants.
1E-5 > P > 1E-7
Hazardous/ Severe Major
Large reduction in safety margins or functional capabilities. Higher workload or physical distress such that the crew could not be relied upon to perform tasks accurately or completely. Adverse effects upon occupants including serious or fatal injury to a relatively small number of occupants other than the flight crew.
1E-7 > P > 1E-9
Catastrophic Failure conditions which would prevent continued safe flight and landing, resulting in multiple fatalities, usually with the loss of the airplane.
1E-9 > P
2-3. Demonstration. To meet the safety criteria, the EFVS design will be demonstrated through analysis and engineering tests to preclude any critical failure combinations that can cause hazardously misleading information to be presented to the crew, or which can otherwise subsequently cause an unsafe condition. Failures which are self-evident or made obvious to the crew, and with which they can safely cope, need not be specifically monitored. 2-4. State Data. The aircraft state data is provided by the standard inertial, air data, and radio guidance sensors. The HUD or display processor will be required to be at a sufficient level of safety for the aircraft type and application to detect critical random, or common, faults that could otherwise cause an unsafe condition. The ability to continue the approach below the standard Category I DA/DH/MDA/MDH therefore is strictly borne by the pilot, a safety factor already accounted for in the safety analysis for standard Category I operations. The example below is a model case and cannot be applied for any specific aircraft. Functional hazard assessments as required by the FAA are aircraft and systems specific.
Table 4. Example EFVS/HUD Functional Hazard Assessment, 14 CFR part 25 Aircraft, ILS
Approaches to 100 ft Height Above Touchdown, RVR 1200 ft
FHA NO.
FAILURE CONDITION PHASE OF FLIGHT
PILOT ACTION
HAZARD INDEX OBJECTIVE
1.0 LOSS OF FUNCTION
1.1 Loss of EFVS imagery on HUD
Taxi and Takeoff Enroute Terminal Arrival Final Approach - Above 100 ft. EFVS height above touchdown zone elevation Go-Around
1.1 Loss of EFVS imagery on HUD
Crew would revert to standard headup and/or head down procedures
MINOR 1E-03
1.2 Loss of EFVS imagery on HUD
Final Approach - From 100 ft. height above touchdown zone elevation to Landing
Crew performs a go-around or possibly a minimum flare landing
MINOR
1E-03
1.3 Loss of HUD symbology
1.3 Loss of HUD symbology
Taxi and Takeoff Enroute Terminal Arrival Final Approach - Above 100 ft. height above touchdown zone elevation Go-Around
Crew would revert to standard head down procedures
MINOR 1E-03
1.4 Loss of HUD symbology
Final Approach - From 100 ft. height above touchdown zone elevation to Landing
1.4 Loss of HUD symbology
Pilot would continue the approach and land
MINOR 1E-03
1.5 Loss of HUD and EFVS Imagery
Final Approach - From 100 ft. height above touchdown zone elevation to Landing
Pilot would continue the approach and land
MINOR 1E-03
FHA NO.
FAILURE CONDITION PHASE OF FLIGHT
FAILURE EFFECT
HAZARD INDEX OBJECTIVE
Continue reading ↓ 120 of 193 passages shown