Joint TAA-OAA Advisory on Obtaining TAC and OAC for Portable Electronic Flight Bags
Effective date: 1 May 2018
Version in effect: 3 (Revised in March 2021)
Reference: TAM Part 2, Chapter 3 and Part 3, Chapter 2
OAM, Chapter 3, Paragraphs 314 and 315
OPI/Telephone: DTAES 6-4, 819-939-4714
SSO OA, 204-833-2500, ext. 6649
Alternate format
4.3. Electronic Flight Bag Implementation Procedures
Annex A – Description and Examples of "Type A" Software Applications
Annex B – Description and Examples of "Type B" Software Applications
Annex C – Portable Electronic Flight Bag Evaluation Process
Annex D – Portable Electronic Flight Bag Evaluation Checklist
Annex E – Electronic Flight Bag Software Applications Evaluation Checklist
Annex F – Operational Evaluation at the Fleet Level
Annex G – Operational Evaluation Checklist – Fleet Level
Annex H – Operational Aircraft Evaluation
Annex I – Aircraft Operational Evaluation Checklist
Annex J – Guidance for the Development of EFB Software Applications
1. Purpose
1.1. The purpose of this joint Technical Airworthiness Authority (TAA) – Operational Airworthiness Authority (OAA) Advisory is to provide guidelines for obtaining initial and follow-on Technical Airworthiness Clearance (TAC) and Operational Airworthiness Clearance (OAC) for Portable Electronic Flight Bags (EFBs).
2. Applicability
2.1. This joint TAA-OAA Advisory is applicable to organizations involved with the TAC and OAC of portable EFBs.
2.2. This joint TAA-OAA Advisory only addresses Portable EFBs. Portable EFBs are those brought on board by the flight crews and are not part of the configuration of the type certified aircraft. Any reference to an EFB in this advisory means a Portable EFBs.
Notes:
1. Installed EFBs are considered permanent and fully integrated within the aircraft flight deck. An example of an Installed EFB would be a modern aircraft with a certified Multi-Function Display (MFD), where that MFD includes the capability to display Aeronautical Charts.
2. Approval of Installed EFBs is covered by existing DND/CAF Design Change policy covering permanent installation of avionic equipment and not included as part of this advisory.
2.3 EFBs should not be used to replace any functions (e.g., navigation, surveillance, etc.) currently provided by certified aircraft systems and will not be granted airworthiness approval for such functions. EFBs should only carry copies of approved airworthiness data/documentation (e.g., AFM/AOI, approach plates, checklists, etc.).
2.4 The Operational Airworthiness Manual (regulatory reference 3.2.c), Chapter 3, Paragraph 314 provides the following regulatory requirements for Portable Electronic Devices (PEDs):
"If a PED is required by aircrew for the conduct of official airborne duties, it is no longer considered a PED, but is now an aeronautical product, and must be cleared for use IAW the airworthiness clearance process. Even if a PED has been recommended for an unrestricted electromagnetic compatibility (EMC) safety of flight (SOF) clearance, a technical and operational clearance is still required – to ensure that the PED does not interfere with fleet-specific aircraft systems (including egress) and that the aircrew are properly trained to use the PED and to store it when not in use."
2.5 A TAC and an OAC or Operational Airworthiness Approval (OA Approval) will be required prior to using EFBs operationally.
3.1 Definitions
- Electronic Flight Bag (EFB). An electronic display system intended primarily for cockpit or cabin use. EFB devices can display a variety of aviation data or perform calculations, such as performance data and fuel calculations. In the past, some of these functions were traditionally accomplished using paper references, or were based on data provided to the flight crew by base operations. The scope of the EFB functionality may also include various other hosted databases and applications. Physical EFB displays may use various technologies, formats and forms of communication. In the context of this TAA- OAA Advisory, an EFB includes both the hardware and software needed to support an intended functionality.
- EFB Administrator. he person appointed by the Operational Commander to be held responsible for the administration of the EFB system within the Fleet or Wing. The EFB Administrator will be the person in overall charge of the EFB system and will be responsible for ensuring that the hardware conforms to the required specification, and that no unauthorized software is installed. This person will also be responsible for ensuring that only the current version of any application and data packages are installed on the EFB system.
- Type A EFB Software Application. Software installed on an EFB providing a specific operational functionality, whose malfunction or misuse would have no adverse effect on the safety of any flight operation, that is a failure condition classification considered to be “no safety effect” (refer to Annex A of this TAA- OAA Advisory).
- Type B EFB Software Application. Software installed on an EFB providing a specific operational functionality, whose malfunction or misuse would have a “minor” or "less than minor" failure condition classification (refer to Annex B of this TAA- OAA Advisory).
- Viewable Stowage Device. A portable device or component used to secure an EFB, viewable to the pilot ( e.g., kneeboards, suction cups, etc.).
3.2. Regulatory References
- C-05-005-001/AG-001 – Technical Airworthiness Manual (TAM)
- C-05-005-001/AG-002 – Airworthiness Design Standards Manual, Part 2, Chapter 6 – Aircraft Cybersecurity
4.1. Background
4.1.1. EFBs perform a variety of functions, traditionally accomplished using paper references, by electronically storing and retrieving documents required for flight operations, such as the AFM, AOI, Standard Manoeuvers Manual (SMM), Checklists, Minimum Equipment Lists (MEL), and Enroute, Terminal and Approach Charts. As such, EFBs may be authorized for use in conjunction with, or as replacement for, some of the hard copy material that aircrew would typically carry in their flight bags. This EFB functionality is derived by hosting either Type A or B software applications on a portable EFB. EFB software applications that cannot be categorized as Type A or Type B (i.e., not listed in Annex A or B, or whose malfunction or misuse would have a “major” or greater failure condition) cannot be authorized under the guidance of this advisory.
4.1.2 EFB applications have also been developed to support functions during all phases of ground and flight operations. Numerous applications are available, with varying degrees of complexity.
4.1.3 While EFBs are not to be authorized for use as a certified navigation system, it is recognized that their use for situational awareness purposes provides improved safety of flight. Therefore, the use of own-ship position for situational awareness purposes may be authorized by the OAA.
4.1.4 The EFB may have wired or wireless aircraft data connectivity, provided it is shown that the EFB does not negatively impact the safe operation of the aircraft. The wired and/or wireless aircraft provisions that support the EFB to aircraft data connectivity are a design change that will require airworthiness approval (see paragraph 4.2.1.2.b.)
4.1.5 The EFB may be powered from an internal battery, or powered/recharged through a certified aircraft power source.
4.2. TAC and OAC Aspects
4.2.1. Technical Airworthiness Clearance (TAC)
4.2.1.1 The TAC process is documented in reference 3.2.b. Aspects associated with granting a TAC for EFBs can be addressed in accordance with existing approved processes. The TAC covers items that require airworthiness approval, and those that do not.
4.2.1.2 The implementation aspects requiring airworthiness approval in support of a TAC (as applicable to the proposed implementation) include the following:
- Electromagnetic Environmental Effects (E3);
- Design changes that require modification(s) to the aircraft in support of the EFB (e.g., mounting provisions, electrical and interface wiring provisions, data connectivity provisions);
- Stowage;
- Human Factors, as they pertain to affecting the already existing certified aspects of the aircraft (e.g., blocking view of required flight instruments, impeding egress and, where applicable, safe ejection, etc.); and
- Aircraft systems and network security for wired or wireless connections to aircraft systems (acceptable guidance is provided in reference 3.2.h)
4.2.1.3 For convenience, the aspects in 4.2.1.2 relating to airworthiness approval are included in the Annex D checklist of this TAA-OAA Advisory and annotated as "[CERT]".
4.2.2 Operational Airworthiness Clearance
4.2.2.1 The OAA is responsible for assessing the operational suitability and functionality requirements associated with the operational use of the EFB and for issuing an associated OAC. The OAC process is documented in reference 3.2.c.
4.2.2.2 The OAA has published an amendment to the RCAF FOM (reference 3.2.i), aimed at providing direction on the use of EFBs in RCAF training and operations.
4.3. Electronic Flight Bag Implementation Procedures
4.3.1. Fleets incorporating EFBs into their operations should carefully review the contents of this TAA-OAA Advisory to determine applicable requirements. For the most part, the level of complexity associated with the operational implementation will depend on whether aircraft design changes will be required to support the EFB, the type of software used and the intended use (e.g., replace all paper approach charts with electronic charts in all phases of flight).
Note: Follow-on changes to the EFB hardware and/or software should be assessed in accordance with the applicable requirements of this advisory.
4.3.2 The operational implementation will require a structured sequence of events to ensure that the aircraft equipped with one or more EFBs can be operated safely. Checklists are provided in the annexes to this TAA-OAA Advisory to assist with the evaluation of the TAC and OAC aspects of EFBs.
4.3.3 Depending on circumstances, the TAC and OAC aircraft evaluations may be carried out separately or as a combined exercise.
Note: On-aircraft evaluations carried out in support of checklist completion (e.g., cockpit compatibility, assessment of operational suitability and effectiveness) are normally carried out by Test and Evaluation (T&E) Agents in accordance with the Flight Test Orders for the Canadian Forces (C-05-020-007/AM-000). The requirement for on-aircraft evaluation is identified by Finding Authorities (for Airworthiness Approval), Technical Authorities and staff holding Operational Airworthiness authority.
4.3.4 From a process perspective, it is envisaged that the Fleet and/or WSM will:
- determine the required EFB capability and mission usage (e.g., CONOPS [1 CAD]);
- decide on the type of EFBs to use, based on a number of factors, including the use of this TAA-OAA Advisory [1 CAD];
- complete all necessary assessments, evaluations, document updates, training, maintenance schedule changes, etc. [WSM/1 CAD];
- process TAC in accordance with the requirements of the TAM, relevant Engineering Process Manual (EPM) and associated procedures (e.g., AF9000 EMT 04.057 – Design Change Certification Process (regulatory reference 3.2.a), AF9000 EMT 04.059 for Non Installed Equipment (regulatory reference 3.2.e), etc.) or applicablerelevant contractual requirements, as applicable [WSM/PMO];
- fulfill the requirements in the RCAF FOM 2.2.8, Part 8 (regulatory reference 3.2.i) [1 CAD]; and
- submit AFM/AFM-AOI amendments, if applicable [WSM/1 CAD].
4.3.5 Technically-oriented evaluations are required as detailed in Annex C, Annex D and Annex E of this TAA-OAA Advisory. Those TAC aspects requiring airworthiness approval are annotated “[CERT]” in Annex D.
4.3.6 Operational evaluations are required as detailed in Annex F, Annex G, Annex H and Annex I of this TAA-OAA Advisory.
4.3.6.1 The first evaluation detailed in Annex F of this TAA-OAA Advisory is to ensure that Fleets have properly addressed the CAF implementation of EFBs from an organizational process perspective. The associated evaluation checklist is provided in Annex G of this TAA-OAA Advisory.
4.3.6.2 The second evaluation detailed in Annex H of this TAA-OAA Advisory is an aircraft-level operational evaluation, which would normally be conducted by the Operational Test and Evaluation community. An associated operational evaluation checklist is provided in Annex I of this TAA-OAA Advisory. Depending on the circumstances, this evaluation may be combined with the evaluation detailed in Annex C of this TAA-OAA Advisory.
4.3.7 Fleets procuring, developing or contracting the development of EFB Software Applications should consult Annex J – Guidance for the Development of EFB Software Applications . Annex J contains best practices associated with the development of certain categories of EFB Type B applications. Since the software applications reside on a portable EFB, and are not part of the aircraft Type Design, the responsibility for the assessment of these software applications resides with the OAA. DTAES would be able to provide assistance with these assessments through an Engineering Support (ES) tasking, if requested to do so. The OAA should direct requests for ES to DTAES 6.
Page details
- Date modified: