From Paper to Pixels: Electronic Flight Bag (EFB) in ICAO, EASA, FAA environment

This article provides a general overview of Electronic Flight Bags (EFBs) and the regulatory frameworks for airworthiness and operational approvals as outlined in ICAO, EASA, and FAA standards and regulations. To begin, let's first define what a "Portable Electronic Device (PED)" is before delving into the specifics of EFBs.

Portable Electronic Device (PED):

As per EASA, “PED is any kind of electronic device, typically, but not limited to, consumer electronics that is brought on board the aircraft by crew members, passengers, or as part of the cargo, and that is not included in the configuration of the certified aircraft. It includes all equipment that is able to consume electrical energy. The electrical energy can be provided from internal sources such as batteries (chargeable or non-rechargeable), or the devices may also be connected to specific aircraft power sources.”

Electronic Flight Bag (EFB):

As per ICAO and EASA, an EFB is “an electronic information system, comprised of equipment (hardware) and applications (software) for flight crew, which allows for storing, updating, displaying and processing of EFB functions to support flight operations or duties” (ICAO Annex-6, EASA AMC 20-25).

In simple terms:

EFB = Hardware (PED or Installed) + Software (Type-A or B)

Types of EFBs:

Portable EFB:

Portable EFB is not part of aircraft configuration (type certificate) and Airworthiness approval is not required.

Installed EFB:

Installed EFB is part of aircraft configuration (type certificate) and associated Airworthiness approval is mandatory.

In case of "portable" EFB which requires installed resources (i.e. EFB mounting device, connecting cables, control devices, remote display etc.), an airworthiness approval is necessary for such installed resources. Normally, the installed resources are dedicated to EFB functions only. If in the case of use of resources shared with aircraft avionics systems, this has to be part of the approved type design. (EASA AMC 20-25)

EFB Software Applications:

Type-A software:?

Type-A applications do not have safety effect in case of failure condition.

Type-B software:

Type-B applications have minor safety effect in case of failure condition. Safety effect cannot be worse than minor.

For a PED to be considered an EFB, the PED must actively display Type-A and/or Type-B software application. For instance, when a PED is displaying personal email, the PED is not considered an EFB; when the same PED is authorized and actively displaying, e.g. aeronautical chart application (Type-B software), it is then considered an EFB (FAA AC 120-76E).

EFB software applications are not part of the configuration of the certified aircraft and have no certification requirements for installation under aircraft type design (FAA AC 20-173 and EASA AMC 20-25).

Typical examples of Type-A software applications:

1. Minimum equipment lists (MEL).
2. Configuration Deviation Lists (CDL).
3. Aeronautical Information Publications (AIP).
4. Pilot flight and duty-time logs.
5. Aircraft captain’s logs.
6. Airline Policy and Procedures Manuals (PPM).
7. Service Bulletins (SB)/published Airworthiness Directives (AD), etc.

Typical examples of Type-B software applications:

1. Airplane Flight Manuals (AFM)
2. Maintenance manuals.
3. W&B calculations.
4. Operations specifications (OpSpecs).
5. Runway limiting performance calculations
6. Electronic aeronautical charts.
7. Autopilot approach and autoland records.

Note: Complete list of Type-A & B software applications can be checked in “EASA Part-CAT.GEN.MPA.141” as well as in “Appendix-A & B to the FAA AC 120-76E”.

Typical EFB System:

Regulatory Framework:

ICAO has published Standards and Recommended Practices (SARPS) in Annex 6 (Parts I, II, III) and in the associated manual (Doc 10020), which requires that any installed EFB or installed components of a portable EFB must be certified. Operators are required to conduct a risk assessment of the EFB functions (software), ensure redundancy of the systems/information, and establish an EFB Management System, which includes procedures for EFB use and periodic training for crew. These ICAO SARPS have been incorporated into EASA and FAA regulations as follows:

EU / EASA Regulations:

1. Regulations (EU) 2018/1975.
2. ED Decision 2019/008R.
3. Certification Specifications (CS) 23, 25, 27, 29 (installed EFB / installed resources)
4. Part-21 (Non-installed Equipment-NIE) (software applications)
5. Part-CAT, Part-SPA, Part-NCC, Part-SPO (Portable EFB, Software applications).
6. AMC 20-25 (installed EFB, installed resources)
7. EUROCAE ED-273 (Software applications)

FAA Regulations:

1. FAR-21, 23, 25, 27, 29 (installed EFB / installed resources)
2. FAR-91, 121, 125, 135 (portable EFB)
3. Advisory Circular (AC) 20-173 (installed EFB / installed resources)
4. AC 120-76E (portable EFB, Software applications)

Role of State of Design (SoD):

SoD issues airworthiness approval to the installed EFB (or installed resources of portable EFB) as part of aircraft’s Type Certificate (TC) or, for in-service aircraft, as per Supplemental Type Certificate (STC).

Role of State of Registry (SoR):

SoR issues airworthiness approval of the modifications to the aircraft (e.g. installation of EFB mounting device etc.) to use portable EFBs.

Role of Type Certificate (TC) / Supplemental Type Certificate (STC) Holders:

For installed EFBs:

TC / STC holders for installed EFBs should compile and maintain guidelines to provide a set of limitations, considerations, and guidance to design, develop, and integrate software applications into the installed EFB or with certified resources for portable EFB.

For “installed resources” of Portable EFBs:

TC / STC holders for installed resources of portable EFBs should provide a set of requirements and guidelines to integrate the portable EFB into the installed resources, and to design and develop EFB software applications.

Role of State of Operator:

State of Operator issues operational approval to use EFB as part of Air Operator Certificate (AOC) Operations Specifications (Ops. Specs.)

Role of Airline Operators:

Operators develop and implement the EFB management system (policies / procedures for EFB use, risk assessments, trainings etc.) as part of Operations Manual (OM) and incorporate in to Minimum Equipment List (MEL), if applicable.

Definitions:

EFB management: Contains all procedures related to the operator’s EFB management system as listed in the ICAO Doc 10020 section “EFB management”.

Installed resources: Hardware/software installed in accordance with airworthiness requirements. For example: Mounting device, Characteristics and placement of the EFB display, EFB data connectivity, Connecting cables, Power Provisions, Controls etc.

EFB Mounting device: An EFB mounting device is an aircraft certified part that secures portable or installed EFB, or EFB system components.

EFB Function: non-critical software function related to operations used by pilots to support their operational duties.

EFB software application: software containing at least one EFB function.

Further reading:

1. EASA AMC 20-25 (https://www.easa.europa.eu/en/document-library/certification-specifications/amc-20-amendment-23)
2. ICAO Doc 10020 (https://efb-soft.com/attachments/article/122/ICAO%20DOC%2010020%20(en).pdf)
3. FAA AC 120-76E (https://www.faa.gov/regulations_policies/advisory_circulars/index.cfm/go/document.information/documentID/1042829)
4. FAA AC 20-173 (https://www.faa.gov/documentlibrary/media/advisory_circular/ac_20-173.pdf)

References:

1. ICAO Annex-6
2. ICAO Doc 10020
3. EASA AMC 20-25
4. EASA Part-CAT
5. FAA AC 120-76E
6. FAA AC 20-173