AMC3 CAT.GEN.MPA.141(b) Use of electronic flight bags (EFBs)

CAA ORS9 Decision No. 1

TYPICAL TYPE B EFB APPLICATIONS

The following EFB applications should be considered type B EFB applications, provided that they do not feature design or functional novelties that introduce new forms of crew interaction or unusual procedures:

(a) Document browsers that display the manuals and additional information and forms required to be carried by regulations and that are necessary for the safe operation of the aircraft, such as:

(1) the operations manual (including the minimum equipment list (MEL) and configuration deviation list (CDL));

(2) the aircraft flight manual, or equivalent document;

(3) the operational flight plan;

(4) meteorological information with graphical interpretation;

(5) air traffic services (ATS) flight plan;

(6) notices to airmen (NOTAMs) and aeronautical information service (AIS) briefing documentation.

(b) Electronic aeronautical chart applications including en-route, area, approach, and airport surface maps.

(d) Applications that make use of the aeronautical operational control (AOC) communications to collect, process and then disseminate operational data.

(e) Aircraft performance calculation applications that use algorithmic data or that perform calculations using software algorithms to provide aircraft performance data such as:

(1) take-off, en-route, approach and landing, missed approach and other phases of flight, performance calculations providing limiting masses, distances, times and/or speeds, etc.;

(2) power settings, including reduced take-off thrust settings, etc.

(f) Mass and balance calculation applications used to establish the mass and centre of gravity of the aircraft and to determine that the load and its distribution are such that the mass and balance limits of the aircraft are not exceeded.

(g) Applications providing in-flight weather information.