Doc 10020

Manual of Electronic Flight Bags (EFBs)

First Edition, 2016

Approved by and published under the authority of the Secretary General

INTERNATIONAL CIVIL AVIATION ORGANIZATION

1-4 Manual on Electronic Flight Bags (EFBs)

1.3.6.3 Means to turn off the power source, other than a circuit breaker, should be reachable by the pilot when
strapped in the normal seated position (e g. access to unplug the EFB or a separate hardware or software switch clearly
labelled for the power source, etc.).

1.3.7 Batteries

1.3.7.1 The operator should ensure that the batteries are compliant with the applicable Standards for use in an
aircraft.

1.3.7.2 The operator should consider introducing procedures to handle thermal runaways or similar battery
malfunctions potentially caused by EFB batteries (e.g. lithium-based batteries). At least the following issues should be
addressed:

a) risk of leakage;

b) safe storage of spares including the potential for short circuit; and

c) hazards due to on-board continuous charging of the device, including battery overheat.

1.3.8 Cabling

The operator needs to ensure that any cabling attached to the EFB, whether in the dedicated mounting or when hand-
held, does not present an operational or safety hazard.

1.3.9 Temperature rise

Operating the proposed EFB device may generate heat. The placement of the EFB should allow sufficient airflow around
the unit, if required.

1.3.10 Data connectivity between EFBs

If two or more EFBs on the flight deck are connected to each other, then the operator should demonstrate that this
connection does not negatively affect otherwise independent EFB platforms.

1.3.11 Data connectivity to aircraft systems

See paragraph 1.2.2.

1.3.12 External connectivity

Some EFBs may have the provision for external ports other than power or data connectivity with aircraft systems (e.g.
an antenna or a data connection to the operator ground network). External connectivity leading to a change to the
aircraft type design should require an airworthiness approval. The extent of this information is dependent on the
complexity of the interface to the aircraft systems.
Appendix B. Specific operational approval checklist App B-3

Part 3

Note.— This part should be completed multiple times to account for the different software applications
being considered.

SOFTWARE

Software application: _____________________ (fill in name of software application)

Is the application considered an EFB function (see Chapter 6)? Yes □

No □
N/A □

Has the software application been evaluated to confirm that the information being provided to the Yes □
pilot is a true and accurate representation of the documents or charts being replaced? No □
N/A □

Has the software application been evaluated to confirm that the computational solution(s) being Yes □
provided to the pilot is a true and accurate solution (e.g. performance, and mass and balance No □
(M&B), etc.)? N/A □

Does the software application have adequate security measures to ensure data integrity (e.g. Yes □
preventing unauthorized manipulation)? No □
N/A □

Does the EFB system provide, in general, a consistent and intuitive user interface, within and across Yes □
the various hosted applications? No □
N/A □

Has the EFB software been evaluated to consider HMI and workload aspects? Yes □
No □
N/A □

Does the software application follow Human Factors guidance? Yes □

No □
N/A □

Can the flight crew easily determine the validity and currency of the software application and Yes □
databases installed on the EFB, if required? No □
N/A □

Power connection / batteries

Is there a means other than a circuit-breaker to turn off the power source (e.g. can the pilot easily Yes □
remove the plug from the installed outlet)? No □
N/A □

Is the power source suitable for the device? Yes □

No □
N/A □

Have guidance/procedures been provided for battery failure or malfunction? Yes □

No □
N/A □
Appendix B. Specific operational approval checklist App B-7

Are there adequate controls to prevent corruption of operating systems, software, and databases? Yes □
No □
N/A □

Are there adequate security measures to prevent system degradation, malware and unauthorized Yes □
access? No □
N/A □

Are procedures defined to track database expiration/updates? Yes □

No □
N/A □

Are there documented procedures for the management of data integrity? Yes □
No □
N/A □

If the hardware is assigned to the flight crew, does a policy on private use exist? Yes □
No □
N/A □

______________________