AMC2 SPA.EFB.100(b) Use of electronic flight bags (EFBs) – Operational approval    

CAA ORS9 Decision No. 1

CHANGES

Modifications to an EFB system may have to be introduced either by the EFB system supplier, the EFB applications developer, or by the operator itself.

Those modifications that:

(a) do not result in a hardware change that would require a re-evaluation of the HMI and human factors aspects in accordance with AMC1 SPA.EFB.100(b)(2);

(b) do not bring any change to the calculation algorithms of a type B EFB application;

(c) do not bring any change to the HMI of a type B EFB application that requires a change to the flight crew training programme or operational procedures;

(d) introduce a new type A EFB application or modify an existing one (provided its software classification remains type A);

(e) do not introduce any additional functionality to an existing type B EFB application; or

(f) update an existing database necessary to use an existing type B EFB application, may be introduced by the operator without the need to be approved by its CAA.

These changes should, nevertheless, be controlled and properly tested prior to use during flights.

The modifications in the following non-exhaustive list are considered to meet these criteria:

(a) operating system updates;

(b) chart or airport database updates;

(c) updates to introduce fixes (i.e. patches); and

(d) installation and modification of a type A EFB application.

For all other types of modification, the operator should apply the change management procedure approved by the CAA in accordance with ARO.GEN.310(c). This includes the extension of the use of an EFB system, for which the operator already holds an approval, to another aircraft type of the operator’s fleet.

In the specific case of a complete change of the hardware hosting the EFB application, the operator should demonstrate to the CAA that the new hardware is suitable for the intended use of the EFB application as per AMC1 SPA.EFB.100(b).