4.1 An Electronic Flight Bag (EFB) is a digital information system for a flight deck crew member, which performs functions in support of flight operations or duties. EFBs can display a variety of aeronautical data or perform calculations (e.g. performance data, fuel calculations, etc.), and some EFB systems carry out more challenging functions not previously achievable with paper based products (e.g. interactive chart viewers, interactive checklists, navigation displays, datalink services, etc.). With EFB systems being used for more challenging and potentially hazardous functions it is imperative that EFB systems are designed with a level of integrity commensurate with their intended function.
4.2 This chapter presents the Authority prescribed airworthiness design requirements for EFB systems. The EFB design requirements are based largely on Federal Aviation Administration (FAA) and European Aviation Safety Agency (EASA) EFB guidance, however, unlike EASA/FAA the requirements in this chapter focus on technical issues whereas the FAA and EASA guidance also consider the operational management of EFBs to complement the technical requirements. The Authority is exploring whether operational regulations, and perhaps operational approvals, should be employed as an adjunct to the design requirements in this chapter. A decision on the need for operational regulation/approval should be made by mid-2022.
4.3 An EFB is a system comprising of hardware, a resident operating system, hosted software applications (maps, databases, etc.), and where required mounting components and physical interfaces for connecting to aircraft power and data ports, etc. An EFB may be designed to be installed as part of the aircraft configuration, be portable with a combination of installed hardware mounting components and physical connections, or be portable without physical connectivity to the aircraft. Installed elements of an EFB are considered to be an aircraft part and appliance per the DASR and are subject to aircraft type certification approval.
4.4 Portable EFBs are typically specific approval role equipment and the requirements prescribed in Section 5 Chapter 6 – Role Equipment and Portable Electronic Equipment are equally applicable and must be considered prior to authorising a portable EFB for use.
4.5 The potential failure effects of an EFB influence the hardware design, software design and level of integration required, and a system safety analysis needs to be undertaken to identify and analyse EFB failure conditions. Depending on the severity of the identified failure conditions an EFB may need to be installed into the aircraft.
4.6 Design Requirement (Essential). A system safety analysis must be utilised to determine the worst credible failure condition of the EFB.
4.7 The usage of EFBs may introduce hazards that affect safe operation of Defence aircraft. For the initial EFB design and any subsequent modification to the design, a system safety analysis must be carried out to determine the worst credible failure condition of the EFB and each installed software application. The Authority prescribed system safety airworthiness design requirements are presented in Section 2 Chapter 2 – System Safety.
4.8 Design Requirement (Essential). EFBs with a failure condition classified greater than Minor (FAA AC 2X.1309) must be installed into the aircraft and are subject to aircraft type certification approval.
4.9 Portable electronic devices used as EFBs are typically not designed to be certified for aviation use and the lack of an aviation focus during their design makes it be difficult to achieve the required level of assurance for a failure condition greater than Minor (FAA AC 2x.1309). As a result portable EFBs are limited to hosting software applications with intended functions limited to a Minor (FAA AC 2x.1309) failure effect condition. EFBs that have been evaluated to have a worst credible failure condition greater than Minor (FAA AC 2x.1309) must have documented evidence demonstrating that the EFB hardware and software has been assured commensurate with the worst credible failure condition classification.
4.10 Portable EFBs are generally COTS-based computers, considered to be PEE with no airworthiness design, production, or installation approval for the device with its internal components and applications limited to designs with a maximum failure condition of Minor (FAA AC 2X.1309).
4.11 Design Requirement (Essential). Portable EFBs that have been evaluated to have a worst credible failure condition equivalent to Minor (FAA AC 2x.1309) must have documented evidence demonstrating that the EFB, operating system and hosted application software can perform the intended functions and do not provide false or misleading information.
4.12 To demonstrate that the EFB and hosted software applications can perform the intended functions, the high level software requirements for the use of these applications on the EFB must be documented, and a verification program (functional and robustness) conducted. The verification program should assess the accuracy, availability and timeliness of the EFB applications. The verification program should also pay particular attention to the EFB operating system and hosted applications to demonstrate that they meet their intended function and do not provide confusing or misleading information. The above design requirement can be satisfied by complying with requirements detailed in the following documents:
EASA Decision (ED) 2014/001/R – Airworthiness and Operational Considerations for Electronic Flight Bags, Annex II – AMC 20-25, or
FAA Advisory Circular (AC) 120-76D – Authorization for Use of Electronic Flight Bags.
4.13 Depending on the intended use and concept of operation, portable EFBs used in aircraft may be secured on flight crew or in/to an existing aircraft part or have permanent arrangements to restrain the EFB and/or physically interface with the aircraft.
4.14 Design Requirement (Essential). Mounting and interfaces (if any) to aircraft shall form part of the aircraft type design and satisfy the applicable airworthiness requirements prescribed in the aircraft type certification basis.
4.15 Where there is a need to have permanent arrangements for securing EFBs, or physically interface with the aircraft, any hardware associated with the interface is subject to aircraft type certification approval. The above design requirement can be satisfied by complying with requirements detailed in the following documents:
EASA Decision 2014/001/R – Airworthiness and Operational Considerations for Electronic Flight Bags, Annex II – AMC 20-25, or
FAA AC 20-173 – Installation of Electronic Flight Bag Components.
4.16 Installed EFBs with either a Minor (FAA AC 2X.1309) or greater than Minor (FAA AC 2X.1309) failure condition are integrated into the aircraft and will need to demonstrate compliance with the aircraft type certification basis.
4.17 Design Requirement (Essential). Installed EFB hardware, operating system and applications must be designed to meet the safety objectives associated with EFB failure conditions and satisfy the applicable airworthiness requirements prescribed in the aircraft type certification basis.
4.18 Guidance for installing EFBs and complying with the above requirement is detailed in the following documents:
EASA Decision (ED) 2014/001/R – Airworthiness and Operational Considerations for Electronic Flight Bags, Annex II – AMC 20-25, or
FAA Advisory Circular (AC) 120-76D – Authorization for Use of Electronic Flight Bags.
4.19 Further guidance on EFBs is available through contacting the Chapter sponsor.