LATVIJAS REPUBLIKA
CIVILĀS AVIĀCIJAS AĢENTŪRA
REPUBLIC of LATVIA
CIVIL AVIATION AGENCY
AIRPORT “RĪGA” 10/1, MĀRUPES NOVADS, LV-1053, LATVIA, PHONE (371)67830936, FAX (371)67830967
OPERATORS EFB CHECKLIST
Item
Notes
1
System Description
Content
• Purpose
• Aircraft type(s)
• Hardware specification
• Operating system specification
• Software specification and
configuration control
• Administrator and user selectable
options
• Manufacturer/supplier
2
3
4
5
Aircraft Certification Documentation
1
• Supplemental type certificate
Equipment Safety Compliance Statements
EFB Administrator (EFBA)(OM Part A)
2
• EMI
• Battery specification
• Power supply
• Rapid depressurisation test results
3
• Nominated person reporting to post
holder
• Training and Qualifications
• Responsibilities
AFM and/or Flight Crew Operating Manuals,
MEL and Checklists (OM Part B)
3
• Limitations
• Operating philosophy
100-12-ATT9.21
7. izdevums
• Normal and abnormal procedures
including EFB failures
• Hardware/software systems
description
6
7
Human Machine Interface Assessment and Human
Factors Considerations
• AMC 20-25 (Appendix D)
Detailed safety case submission
• Detailing all risks, with appropriate
mitigations.
8
Training Programme (OM Part D and Ground Staff
Training Programmes)
9
10
11
12
• Training methods/media
• Timetable
• Recurrent training and checking
Hardware Management Procedures
Software Management Procedures
4, 5
• Repair, maintenance and stock
control
• Stowage and security
• Hardware modification and upgrade
4, 5
• Application and operating system
4, 5
Data Management Procedures
Quality Management System (Quality Manual
3
• Compliance with EU-OPS 1.035
Amendment)
• Subcontractor audits
13
14
3
Evaluation Plan
6
Implementation Plan
• Post-approval implementation
100-12-ATT9.21
7. izdevums
NOTES:
1 Airworthiness Approval required for Class 2 and 3 Hardware only.
2 Required for Class 1 and 2 Hardware only.
3 Submit Amendments with the Notice of Proposed Amendment (NPA) and MEL compliance document. Submit controlled local procedures manuals (LPMs) where
applicable.
4 Submit controlled LPMs.
5 Submit amendments to maintenance programme where applicable.
6 Operator’s plan for regulatory compliance shall be established containing safe operating procedures, a logical sequence, and other areas (e.g. flight crew and
dispatcher qualifications, acceptable procedures, and schedules for accomplishment).
100-12-ATT9.21
7. izdevums
Detailed guidance
Part 1 of this checklist may be used to review an operator’s EFB submission documentation. Part 2 provides guidance for the assessment of EFB
operation in practice during the Phase 3 system evaluation. Part 3 lists additional items to be considered with specific EFB applications.
Item
Part 1 – Operator’s Submission
1
System Description
• Is the description complete?
• Which hardware class and software type are used? If unable to determine software
type, refer to FOPD.
• Are the administrator and user selectable software options suitable to preserve system
integrity?
2
Aircraft Certification Documentation
Reviewed by Airworthiness Division.
Equipment Safety Compliance Statements
Reviewed by Airworthiness Division.
EFB Administrator (EFBA)(OM Part A)
• Does the EFBA report to a nominated post holder?
• Is the nominated EFB Administrator suitably qualified and trained?
• Do the listed responsibilities match the requirements of the system?
• Are there adequate resources assigned to the EFBA function?
3
4
5
AFM and/or Flight Crew Operating Manuals, MEL and Checklists (OM Part B)
• Are there appropriate procedures for all phases of flight?
• Are the procedures clearly presented, suitably illustrated and readily understood?
• Is there a clear description of the system, its operating philosophy and operational
limitations?
• Do crew procedures for EFB operation integrate with existing SOPs?
• Are there suitable crew cross-checks for verifying safety-critical data?
• Is any additional workload mitigated/controlled?
• Are there contingency procedures for total or partial EFB failure?
• Do the procedures cover system re-boots, lock-ups and recovery from incorrect crew
actions?
• Do crew procedures include a requirement to verify the revision status of software and
data?
• Do crew procedures include verification of EFB serviceability through pre-flight checks?
• Are there restrictions on EFB use according to phase of flight?
100-12-ATT9.21
7. izdevums
• Do crew procedures include restrictions on power connection/battery charging of Class
1 and 2 EFBs?
• Do crew procedures include safe stowage and security of Class 1 and 2 EFBs?
6
Human Machine Interface Assessment and Human Factors Considerations
• Are there a comprehensive Human Machine Interface Assessment and Human Factors
Considerations in accordance with AMC 20-25 (Appendix D)?
• How have the findings of the assessment been addressed and embedded within the
operations manuals? Are mitigating procedures or restrictions required?
7
Safety Case/risk mitigations
Should include, but is not limited to:
• Partial/total failures of the EFB
• Loss of data and corrupt/erroneous outputs;
•Sudden loss of cabin pressure (decompression);
∙Distraction of pilots during ground manoeuvring or in fight
∙Use of incorrect performance data
∙Failure of EFB resulting in smoke/fumes
∙EMI interference from charging or operational use
∙EFB becomes dismounted
∙Breakdown of cockpit power supply
∙Viruses and security
Notes:
Are means of mitigation described?
Have they been incorporated into procedures?
Are software and data subject to validation/verification?
Are software modules partitioned to prevent cross-application effects which may affect
safety or is the hardware locked down to prevent pilot installing corrupted software?
Has the impact of the EFB on the MEL been assessed?
100-12-ATT9.21
7. izdevums
8
Training Programme (OM Part D and Ground Staff Training Programmes)
• Are flight crew and (where applicable) ground staff training programmes fully
documented?
• How does the operator train the personnel conducting EFB training? How is this
certified?
• Is the training methodology matched to the participants’ level of experience and
knowledge?
• Has the operator assigned adequate resources (time/personnel/facilities) for training?
• Is there access to actual or simulated EFB equipment for interactive training?
• Does the training material match the EFB equipment status and published procedures?
• Does the training programme include human factors/CRM in relation to EFB use?
• Is there a published recurrent training and checking programme? Does EFB use
integrate with the OPC?
• Does the training programme incorporate training for system changes and upgrades?
9
Hardware Management Procedures
• Are there controlled documented procedures for the control of hardware and component
stocks?
• Do the procedures include repair, replacement and maintenance of EFB equipment and
peripherals?
• Can the operator track the revision status of software and data installed in each
hardware unit?
• How does the operator verify whether changes to equipment affect the original system
specification?
• How does the operator achieve physical security of hardware?
• If the original system specification is modified, are there adequate procedures to
prevent operational use prior to CAA re-approval?
Software Management Procedures
• Are there controlled documented procedures for the control of installed software?
• Are the access rights for personnel to install or modify software components clearly
defined?
• Are the access rights to install or modify software limited to an appropriate number of
personnel?
• Are there adequate controls and limitations on user access to modifiable system
settings?
• Are there adequate controls to prevent user corruption of operating systems and
software applications?
• Are there adequate security measures to prevent system degradation, viruses, and
10
100-12-ATT9.21
7. izdevums
unauthorised access?
• How does the operator verify whether software changes/upgrades affect the original
system specification?
• If the original system specification is modified, are there adequate procedures to
prevent operational use prior to CAA re-approval?
11
Data Management Procedures
• Are there controlled documented procedures for the control and management of data?
• How do the procedures interface with procedures used by external data providers?
• Are the access rights for users and administrators to manage data clearly defined?
• Are there adequate controls to prevent user corruption of data?
• How does the operator ensure that EFB use is stopped or restricted, if alerted to the
presence of erroneous data? Are the associated communication channels prompt and
reliable?
12
Quality System (Quality Manual Amendment)
• Are there controlled documented procedures for EFB quality assurance?
• Are the procedures integrated into the operator’s existing quality system?
• How is the quality of out-sourced services and data assured? Has the external provider
been audited?
• Do the procedures include periodic verification of data validity?
• Is there a reporting/feedback system for system faults and errors? Is there a robust
response procedure?
• Are feedback reports integrated with air safety reporting/SMS?
• Does EFB operation interface with Flight Data Monitoring (FDM) systems?
13
Evaluation Plan
• Is the evaluation plan documented?
• Is the timetable realistic?
• Will adequate EFB training be completed prior to the evaluation?
• Is there provision to suspend or modify the evaluation in the event of safety-critical
deficiencies?
14
Implementation Plan
• Is the implementation plan realistic? Is it sufficiently flexible to accommodate the
outcomes of Phase 3?
100-12-ATT9.21
7. izdevums
15
Part 2 – System Evaluation
General
• Can flights be conducted as safely with an EFB as with the methods/products it is
intended to replace?
• Does the EFB add an unacceptable level of complexity for any critical activity or phase
of flight?
• Are there any noticeable conflicts between EFB and flight system interfaces, or between
multiple EFBs?
• In the event of an output discrepancy, how does the crew know which output is
primary?
16
Workload
• How does the workload with EFB use compare with equivalent tasks without EFB?
• Does the EFB distract pilots during critical phases of flight?
• Are there policies/procedures in place to mitigate workload/distraction problems?
17
Equipment Location and Stowage
• Does the positioning of the EFB affect its use, or the use of other flight deck systems?
• Is there an acceptable place to put a Class 1 EFB when in use (and not in use)/knee
boards?
• Is there a requirement to lock/stow a Class 2 EFB during critical phases of flight?
• Is stowage for EFB and peripherals accessible and secure?
• Are power cables routed to avoid entanglement and damage?
18
Training
• Is the training adequate in practice? Does it suit the experience and knowledge of the
user?
• Is the training supported by suitable documentation?
• Do the users gain ‘hands-on’ practice with a real or simulated EFB?
• Does recurrent training accommodate changes/upgrades to the EFB system?
• Does recurrent training maintain crew proficiency in non-EFB (back-up) procedures?
• Does the training programme include user feedback to facilitate improvement?
100-12-ATT9.21
7. izdevums
19
Software and Data
• How are modifications and updates achieved and recorded in practice?
• Are revisions/updates achievable in a timely manner? At all airfield locations including
remote bases?
• How are crews and other users notified of updates?
• Does practice match the published procedures?
• Does the EFB present a usable layout, legibility, symbology and colours in all
operational conditions?
• Can the users easily find the information they need?
• If processing is delayed, are ‘busy’ indicators and/or progress indicators displayed?
• Are audio features enabled? If so, what is their impact on crew distraction and aircraft
audio alerts?
• Is it easy to move between items/applications?
• If data is obtained from flight deck systems, what is the back-up procedure if
communication is lost?
• If data is obtained from external systems, what is the back-up procedure if data-link is
lost?
20
Hardware
• Are all hardware controls clearly labelled and easy to use? Are any ‘idiot-proof’ features
required?
• Are there instances of lock-up/freeze, inadvertent crew action (e.g. incorrect shutdown
sequence)?
• Are there instances of data transmission/reception failure? (Data-linked systems.)
• Are failures and anomalies obvious to the user? Are there practical response
procedures?
• Are power connection and battery charging procedures safe and workable in practice?
• Is the hardware fully functional in all flight conditions (temperature, vibration, ambient
light etc.)?
21
Operator Evaluation
• Is the operator’s evaluation conducted according to its published plan?
• How does the operator make use of user feedback?
• Are the operator’s audits objective?
• How does the operator respond to audit findings?
100-12-ATT9.21
7. izdevums
Part 3 – Additional Considerations for Specific Systems
22
Aircraft Performance Calculations
• Can the operator verify that aircraft performance data outputs match AFM performance
data? Is this software certified by EASA?
• Is the entry and manipulation of data easy and unambiguous?
• Does the system provide suitable error messages for inappropriate input/output?
• Is there potential to select an incorrect runway, flap setting, bleed state etc? How is this
mitigated?
• Are restrictions on EFB use clear to the users (e.g. temporary restrictions due to reduce
runway length)?
• Do system data fields retain historical or default values after use? Are users aware of
the implications?
• Does the system allow adequate cross-checks between crew members in practice?
23
Electronic Manuals and Documents
• Are text, tables and diagrams easy to read?
• Are indexing, linking, search and zoom/pan features easy to use?
24
Electronic Navigation Charts
• Does crew training involve use of electronic charts in a realistic flight environment (e.g.
simulator /fixed based training scenario)?
• Can crews use electronic charts as well as they use paper charts?
• Can crews easily identify errors in chart selection?
• Can crews pre-select charts for easy access?
• Can the system easily accommodate short notice changes (e.g. re-clearance, change of
runway)?
• What are the implications, in practice, of the following features?
o Zoom and pan features. Can critical items be lost from view? Do scale and orientation
indications remain visible? Does the scale indication remain accurate?
o Display orientation (north/heading/track ‘up’). Can crews become confused about
display orientation?
o Externally-sensed inputs (e.g. overlay of current aircraft position). Does the system
automatically select relevant charts? Can the selection be manually overridden? Is
displayed position accurate within the displayed scale?
o De-cluttering. Can critical items be lost from view in ‘de-cluttered’ mode? Is there a
clear indication that the de-cluttering feature is active?
100-12-ATT9.21
7. izdevums
o Print features. Are printed charts as accurate and usable as conventional paper charts?
25
Electronic Checklists
• Does crew training involve use of electronic checklists in a realistic flight environment
(e.g. simulator scenario)?
• Can crews use electronic checklists as well as they use paper charts? How does crew
co-ordination of checklist actions work in practice?
• Is progress through the checklist and the status of items (complete/deferred/open) clear
to the crew?
• Can the crew easily change the status of an action item?
• Can the crew remove completed actions in order to recommence the checklist from the
beginning?
• Is there potential to skip checklist items or assign incorrect actions?
• Can the crew easily navigate through the checklist? Are deferred actions appropriately
displayed?
• Is it clear when a checklist is incomplete?
• Are ‘decision branches’ clearly displayed? Can the selection of an incorrect branch be
reversed?
• Are reminders displayed for delayed actions (e.g. fuel dumping)?
• Where the checklist interacts with sensed aircraft data, are all crew actions
automatically monitored and fed back to the checklist?
• Are there links to related data? Is it easy to navigate back to the checklist?
26
Electronic Technical Log
• Does the ETL system work as well in practice as the paper technical log system?
• Does the system allow co-ordinated EFB use between flight crews and engineers?
• Is the entry and review of data easy and unambiguous?
• Do system data fields retain historical or default values after use?
• Does the system transmit data? Is the transmission system reliable?
• Does the system provide suitable error messages for inappropriate input/output or failed
transmissions?
• How do back-up procedures work in practice if transmission is not achieved?
100-12-ATT9.21
7. izdevums
OPERATOR:
Verification performed by operator’s Documentation office
OPERATOR’ S SPECIALIST NAME/SIGNATURE
DATE
OI REPORT
OI NAME/SIGNATURE
DATE
POI COMMENTS
POI NAME/SIGNATURE
DATE
INFORMATION TO THE OPERATOR
POI NAME/SIGNATURE
DATE
100-12-ATT9.21
7. izdevums