曝光台 注意防骗
网曝天猫店富美金盛家居专营店坑蒙拐骗欺诈消费者
1 8 FLIGHT SAFETY FOUNDATION • FLIGHT SAFETY DIGEST • JUNE 2005
A P P E N D I X
JAA Administrative & Guidance Material
Section Four: Operations, Part Three: Temporary Guidance Leaflets (JAR-OPS)
Section 4/Part 3 (JAR-OPS) 36-8 01.10.04
approved, and then against a particular program revision and a particular host e.g., Personal
Computer. With performance Type B software applications the operations authority (JOEB or
National Authority) requires assurance that the resulting data, through software derivation,
customisation or optimisation, provides performance figures that are consistent with the approved
computerised aircraft flight manual information. If there is any concern, the operations authority may
wish to seek advice from airworthiness performance specialists to assist in the validation of these
types of software application. In general, this involves checking that the EFB derived performance
calculations provides consistent results when compared with calculations from the approved AFM
modules.
With electronic checklists, there is already regulatory guidance material published on the subject e.g.,
FAA AC 120-64. The concern here is where the EFB software application is customised or changed
through the user-modifiable partition such that the electronic checklist differs from the approved
procedures contained within the AFM. Of particular concern are changes affecting the approved
Abnormal and Emergency Procedures. Again, where there are concerns, the operations authority
should consult with the respective airworthiness authority team.
7 OPERATIONAL APPROVAL
The Authority will consider applications from operators to use an EFB system on a case-by-case
basis using the process described hereafter. Operators planning to implement the use of EFB
systems will need to demonstrate to the Authority that the EFB system is robust and will not provide
inaccurate or misleading information to crews.
The operator may demonstrate the fidelity and reliability of the system in a number of ways. Where it
is the intention to start EFB operations with no paper back up a full Operational Risk Assessment and
suitable means of mitigation against failure or malfunction will be required. Alternatively, the operator
may choose to keep the paper back up, as a cross check against the EFB information and as a
means of mitigation against failure or malfunction. A combination of the above methods where some
risk assessment and limited paper back up is carried may also be used at the discretion of the
authority. The final Operational Evaluation Test (see section 7.7) will depend on the method used.
Note: Where the term Authority is used in this Section, it applies to either the JOEB or the National
Authority depending on who has primary responsibility for conducting the assessment. Ultimately an
individual operator would expect to receive an operational approval from their National Authority.
7.1 Operational Risk Analysis
The Authority will need to be satisfied that the operator has considered the failure of the complete
EFB system as well as individual applications including corruption or loss of data and erroneously
displayed information.
The objective of this process is to demonstrate that the software application achieves at least the
same level of integrity and availability as the “traditional” means that it is intended to replace
7.1.1 Scope
The analysis will be specific to the operator concerned but will need to address at least the following
points:
• Minimisation of undetected erroneous application output
• Ease or otherwise to detect erroneous outputs from the software application
o Description of corruption scenarios
o Description of mitigation means (crew monitoring)
• Upstream development quality process
o Reliability of root data used in applications (qualified/verified input data)
o Application verification and validation checks
FLIGHT SAFETY FOUNDATION • FLIGHT SAFETY DIGEST • JUNE 2005 19
A P P E N D I X
JAA Administrative & Guidance Material
Section Four: Operations, Part Three: Temporary Guidance Leaflets (JAR-OPS)
Section 4/Part 3 (JAR-OPS) 36-9 01.10.04
o Partitioning of application software having safety effect from application software
without safety effect e.g., partitioning of Type A, B from other application.
• Description of the mitigation means following detected loss of application, or detected
erroneous output due to internal EFB error e.g., availability of back up data, procedures etc.
This may be in the form of an alternative EFB possibly supplied from a different power source
or some form of paper back up system e.g., Quick Reference Handbook (QRH).
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：
航空资料31(91)
