Belgian Civil Aviation Authority
Operations DirectorateElectronic flight bag (EFB) APPLICATION FORM
This application form must be in possession of the Belgian CAA at least 30 days before the intended date of beginning of the test period.
I.GENERAL INFORMATION
1.Operator Name:2.Operator address:
3.Post holder Flight OPS:
4.Post holder Crew Training:
5.Post holder Continuing airworthiness:
6.EFB Administrator:
7.Contact e-mail
8.Airplane make, type:
9.Registration(s):
10.Additional information:
II.SCOPE
EFB:□ Initial application; or □ Additional requestIntended date of the start of the evaluation/test period:
Hardware class:□ Stowable and Viewable unitsor □ Mounted units
Software type:□ A & B; □ A; or □ B; ☐miscellaneous (non-EFB) software
Power supply:□ Aircraft power used; or □ EFB battery only
Data connectivity:□ No EFB-Aircraft interface; □ Aircraft-EFB unidirectional;
or □ Aircraft-EFB bidirectional
Purpose of the EFB:
The EFB is to be used:□ On ground □ In-flight
phases:□ Non critical phases; or □ All flight phases - EMI docs enclosed
by:□ Flight crew □ Cabin crew
III.AIRWORTHINESS
1. Aircraft modification:□EFB has no impact on airworthiness; □EFB capability by aircraft design; or □Aircraft modification incorporated
Modification reference:
2. Maintenance program:□ Instructions for continued airworthiness incorporated in AMP;
or □ No influence on AMP
3. Remark(s):
IV.HARDWARE APPLICATION
1. Hardware platform:□ Toughbook or □ TabletMake, type:
2. Data storage device installed:□ Hard disk; □ USB Stick; □ CD/DVD;
□ Memory card (SD, CF,…);□ Other*
used for EFB:□ Hard disk; □ USB Stick; □ CD/DVD;
□ Memory card (SD, CF,…); □ Other*
3. Data transfer features installed:□USB; □Bluetooth; □IR; □Firewire; □Serial;
□ Wifi; □ Ethernet; □Other*
used for EFB:□ USB; □ Bluetooth; □ IR; □ Firewire; □ Serial;
□ Wifi; □ Ethernet; □ Other*
4. Cursor navigation:□ Touch screen; □ Trackball; □ Touchpad;
□ Mouse; □ Keyboard; □ Other*
5. Batteries:□Lithium batteries used - Liquid spillage issues addressed in documentation; or
□NO Lithium batteries used
6. Remark(s):
- SOFTWARE APPLICATION(S)
1. Operating system (Windows; Apple OS; MAC OS; Linux; Android; …)
Additional information:
2. Application(s) based on:□Manufacturer application; □MS Office; □Adobe PDF;
□html; or □Other*
Additional information:
3. Program settings:□by administrator only; □by end user; or □by administrator + end user
Additional information:
4. Intensions / tasks:
□Data presentation (Manuals); □Data processing (Calculations)
- OPERATION, TRAINING, QUALIFICATION
Manual reference (Chapter, subchapter):
1. System administration
Data base update:
2. System description:
3. System operation:
4. System failure
Contingency procedure:
5. Staff initial training:
6. Staff recurrent training:
NOTES – references below are to the AMC 20-25
An installed EFB is managed under the aircraft type design configuration. Additional details are contained in AMC5.1.2. An EFB host platform installed in the aircraft and considered as an aircraft part, covered, thus, by the aircraft airworthiness approval.
Portable EFB’s are controlled PED’s. An expanded definition of a portable EFB is found in GM1 CAT.GEN.MPA.140.
Portable EFB’s with Installed Resources are subject to airworthiness approval. Installed Resources constitute those elements that are part of the certified aircraft configuration with the intended function to mount the EFB to the aircraft and/or connect other systems. Refer to AMC 6.1.1.1 for examples of such.
- POLICY & GUIDANCE NOTES
1 / Applicability
Applications from operators to use an EFB system will be considered on a case by case basis.
It will be necessary for the operator to propose the required changes to the Operations Manual and nominate an EFB Administrator. The EFB Administrator will need to receive appropriate training and have a good working knowledge of the proposed system hardware and operating system.
Mounting devices, Installed Resources for Portable EFB’s and Installed EFB’s require the BCAA’s Airworthiness approval. The BCAA Airworthiness Section will evaluate all maintenance/airworthiness factors and advise the BCAA-OPS when Airworthiness approval has been granted.
Type A applications hosted in Portable EFB’s can be used by properly trained pilots when exercising their privileges and without the need for any notification or application for operational approval to the BCAA. In all other cases, before using an application hosted on EFB, operators shall apply to the BCAA for operational acceptance.
The evaluation will be conducted by the BCAA when the system hosts Type B applications or Miscellaneous (non-EFB) software applications.
2 / Application Form and Matrix
The completed matrix below must be submitted together with the application form. The application form and matrix must be completed with the support of AMC 20-25.
All applicants should complete Column 3 of this matrix in full. A separate matrix and application form must be completed for different aircraft types and/or EFB model computing device.
All relevant documentation must be submitted in paper format. These should include:
●Applicable extracts from the Operations Manual Parts A, B, D, Compliance Monitoring Manual and MEL;
Note: Instead, a dedicated ‘EFB Policy and Procedures Manual’ can be created to include all EFB relevant information, policies and procedures. This manual will then be considered as part of the Operations Manual suite of documentation. The manual must be first approved by the Respective PH and Compliance Monitoring Manager.
●EMI demonstration report;
●Environment testing;
●Details of Operational Risk Analysis conducted;
●Validation result for Type B software applications;
●AFM supplement and/or STC as applicable for mounting device and installed EFB
●Amendments to maintenance programme where applicable.
The forms must be signed by the responsible Post Holder and when stated by the Compliance Monitoring Manager.
Failure to complete the matrix may result in a delay in processing your application.
3 / EFB Administrator (EFBA)
The name and surname of nominated EFB Administrator is to be stated in the Operations Manual and shown in the company’s organisation structure. He should report to the nominated post holder for flight operations.
Please remember that the EFBA has to be suitably qualified and have received appropriate training to discharge his EFB duties.
4 / Documents to be included with the application
Copies of all documents referred to in Column “Reference evidence documents” of the matrixes below should be included when returning the completed application form to the BCAA. Original documents should not be sent, photocopies are sufficient. Do not send complete manuals, only the relevant sections/pages will be required.
Failure to include all relevant documentation may result in a delay in processing your application.
5 / Operational Evaluation Test (7.14)
The operator is required to conduct an operational evaluation test only after the evaluation of the application and receipt of authorisation from BCAA. The operator shall inform BCAA of the intention to commence the operational evaluation test. Sufficient time should be given to BCAA to review the submitted information.
The notification of the test should at least include:
- Starting date of the operational evaluation test;
- Duration;
- Aircraft Involved;
Applications replacing paper products with an initial retention of paper backup
The paper backup shall initially be retained as a backup. The operational evaluation test should consist of an in-service proving period no longer than six months. Operators wishing to reduce this proving period shall justify this by submitting further information. The information should at least cover elements in 7.14.1.
6 / Final Operational report (7.15)
At the end of the Operational Evaluation Test, the operator should produce and retain a final operational report, which summaries all the activities conducted and the means of compliance used, supporting the operational use of the EFB system. An example of typical items that the operator should include in this report in AMC 20-25 Appendix I
7 / Submissions and Enquiries
The digital version of this form 1163 and supporting documents shall be forwarded to:
Belgian Civil Aviation Authority
Operations Directorate
Rue du Progrès 56
1210 Brussels - Belgium
Note: Please read carefully Glossary of Terms (AMC 20-25 Section 4) and System Description and Classification of EFB systems (AMC 20-25 Section 5)
Matrixes :
Airworthiness Approval (AMC Section 6.1)
1 / Airworthiness Approval / Reference evidence documents / BCAA RemarkInstalled EFB
■Approval of Installation and Hardware
Aircraft Type Definition, Major/Minor Modification, Supplemental Type Certificate, Service Bulletin). Refer to 6.1.1.2
2 / Installed Resources
■Installed resources such as an installed remote display, a control device or docking station. Refer to 6.1.1.1 and subsequent sections.
3 / Certification documentation
■AFM Supplement for the installed EFB and/or Installed Resources. Refer to 6.1.2.1
4 / ■Instructions for Continued Airworthiness
■Aircraft Maintenance Programme
■Installed EFB
Operational Assessment (AMC Section 6.2)
The operator should conduct an operational evaluation test, which should allow verification that the below elements have been satisfied before final decision on the operational use of the EFB.
The matrix below follows the AMC 20-25 sequence for ease of reference.
1 / Hardware Operational Assessment(Applicable to Portable EFB and certain Installed Resources) / Reference evidence documents / BCAA Remark
Electronic Interference (EMI) demonstrations. Refer to 6.2.1.1.
For PED device intended to operate during all phases of flight, the operator is responsible for ensuring that the PED will not interfere with aircraft equipment.
■Advise which Method of compliance is used.Refer to 6.2.1.1.1.
For operators intending to activate transmitting capability of the EFB during flight other than in those certified at aircraft level (documented in AFM or equivalent document) the operator is responsible to ensure that the T-PED will not interfere with the operation of aircraft equipment.
■Advise which Test Requirement is met and how. Refer to 6.2.1.1.2.
2 / Batteries. Refer to 6.2.1.2
When EFB are used with rechargeable lithium batteries operators should collect evidence of testing standards.
■Advise to which standards the batteries are compliant.
3 / Power source. Refer to 6.2.1.3
If a power source is used, advise how considerations in 6.2.1.3 are certified and evidenced.
4 / Environmental Testing. Refer to 6.2.1.4
■Provide test results for the hardware unit intended for use.
NOTE - New tests / results may be required when EFB model or battery type is changed.
5 / Display characteristics. Refer to 6.2.1.5
■Provide criteria for selection of placement of EFB and display characteristics.
NOTE - Additional information is found in 6.1.1.1.2 (a) and (b).
6 / Viewable Stowage. Refer to 6.2.1.6.
■Document how the provisions of the location, procedures and other factors such as holding capacity are recorded.
NOTE – this may be performed through vibration tests available from third parties.
7 / Software Operational Assessment
(Applicable to all types of EFB) / Reference evidence documents / BCAA Remark
Fill in only if you ticked Type A software applications.
■Advise how HMI and human factors guidance material are followed. (Refer to Appendix D)
■This software shall only be used by trained pilots. (Applicable only to Portable EFB)
8 / Fill in only if you ticked Type B software applications.
■This software should be assessed in accordance with 7.2 (Risk Assessment of EFB systems)
■If Airport Moving Map Display (AMMD) is used, provide operational procedures. (Refer to Appendix H)
9 / Fill in only if you ticked Miscellaneous (non-EFB) software applications.
■Provide details of how these applications are managed by the EFB administrator and how they do not adversely impact the operation of the EFB. Refer to 6.2.2.3.
Additional Requirements
These details may be included in the Policy and Procedures Manual or in any other controlled document which may be referenced during application phase.
10 / Risk assessment for EFB systems (7.2)(Applicable to all types of EFB) / Reference evidence documents / BCAA Remark
The operator should carry out a risk assessment as part of its hazard identification and risk management process required by ORO.GEN.200.
■Provide a copy of the risk assessment, detailing how items in 7.2.1 and 7.2.2 are discussed.
11 / Changes to EFB (7.3)
(Applicable to all types of EFB) / Reference evidence documents / BCAA Remark
Provide documentation of how changes that require prior assessment and approval of BCAA and those which do not require approval are managed.
12 / Dispatch Considerations (7.4)
(Applicable to all types of EFB) / Reference evidence documents / BCAA Remark
Dispatch considerations for EFB systems may either be included in the Operations Manual or MEL. Refer to 7.4.1 for details.
13 / Human Factors Assessment (7.5)
(Applicable to all types of EFB) / Reference evidence documents / BCAA Remark
Provide an assessment of the human machine interface, installation and aspects governing CRM when using EFB. Further elements to be assessed are found in Appendix D.
14 / Specific considerations for mass and balance and performance applications (7.6)
(Applicable to all types of EFB) / Reference evidence documents / BCAA Remark
If aircraft mass and balance and performance application will be managed through EFB usage, these must form part of the evaluation. Further considerations are found in Appendix F.
15 / Flight crew operating procedures (7.7)
(Applicable to all types of EFB) / Reference evidence documents / BCAA Remark
Detail the below aspects:
■Procedures for using EFB systems with other flight crew compartment systems.
■Flight crew awareness of EFB software/database revisions.
■Procedures to mitigate and/or control workload.
■Define flight crew responsibilities for performance calculations.
16 / Compliance Monitoring (7.8)
(Applicable to all types of EFB) / Reference evidence documents / BCAA Remark
The EFB should be included in the compliance monitoring system as required by ORO.GEN.200.
■Provide evidence of compliance manuals/sections and audit plans specific to EFB use.
17 / EFB system security (7.9)
(Applicable to all types of EFB) / Reference evidence documents / BCAA Remark
The EFB system should be secure from unauthorised intervention.
■Provide details of procedures and measures taken by the EFB administrator ensure system security.
18 / Electronic signatures (7.10)
(Applicable to all types of EFB) / Reference evidence documents / BCAA Remark
If operator intends to use electronic signatures to signify acceptance or authority in EFB applications, these need to fulfil the same degree of security requirement as a handwritten one or any other form of signature it intends to replace.
19 / Role of EFB administrator (7.11) and EFB policy and procedures manual (7.11.1)
(Applicable to all types of EFB) / Reference evidence documents / BCAA Remark
The role of the EFB administrator (EFBA) is a key factor in the management of EFB systems. Provide details of the roles/duties and responsibilities of the administrator. These should also include minimum training requirements.
Procedures for continuity of the management in case of absence are also required.
The policy and procedures manual should be controlled and be under the responsibility of the EFBA. Document how the procedures and layout of the manual contain those elements in Appendix G (this is a non exhaustive list).
20 / EFB system maintenance (7.12)
(Applicable to all types of EFB) / Reference evidence documents / BCAA Remark
Procedures should be established for the routine maintenance of the EFB system. These shall also include actions in case of failures or unserviceability.
21 / Flight crew training (7.13)
(Applicable to all types of EFB) / Reference evidence documents / BCAA Remark
Flight crew should be given specific training on the use of EFB before it is operationally used. Training procedures should be included in OMD.
■Provide extracts of ground training programme and syllabus to be followed.
■Provide elements that shall be assessed during LOFT and line training sessions.
NOTE – Further guidance is found in Appendix E.
22 / Operational evaluation test (7.14)
(Applicable to all types of EFB) / Reference evidence documents / BCAA Remark
The operator should conduct an Operational evaluation test (trial period) and submit a plan to the authority
End of document
OPS Procedures Form 1163 issued 03/11/2015Page 1/9