曝光臺 注意防騙 網曝天貓店富美金盛家居專營店坑蒙拐騙欺詐消費者

The operator may then propose to the Authority that the EFB system be used as an alternative
system to paper documentation. The proposal to the Authority should specify which paper
documentation need not be carried and/or any operational credit sought. The Authority may require a
trial period during which paper documentation is retained to confirm the robustness of the system.
The impact of the EFB system on the Minimum Equipment List (MEL) should be assessed. The
operator should demonstrate how the availability of the EFB is confirmed by pre-flight checks.
Instructions to flight crew should clearly define actions to be taken in the event of any EFB system
deficiency and whether dispatch is allowed.
7.2 Human Machine Interface Assessment for Type A and B Software Applications
The operator will need to carry out an assessment of the human machine interface and aspects
governing Cockpit Resource Management (CRM), when using the EFB system. This should include a
review of the complete system to include at least the following points.
• Human/machine interface
• Legibility of text
• Approach/departure and navigation chart display
• Responsiveness of application
• Off-screen text and content
• Active regions
• Managing multiple open applications and documents
• Messages and the use of colours
• System error messages
• Data entry screening and error messages
Note: Further guidance and means of compliance are provided in Appendix D.
7.3 Flight Crew Operating Procedures.
7.3.1 Procedures for Using EFB Systems with other Flight Deck Systems
Procedures should be designed to ensure that the flight crew know which aircraft system (e.g., Engine
Indicating and Crew Alerting System (EICAS), Flight Management System (FMS), or EFB system) to
use for a given purpose, especially when both the aircraft and EFB systems provide similar
information. Procedures should also be designed to define the actions to be taken when information
provided by an EFB system does not agree with that from other flight deck sources, or when one EFB
system disagrees with another. If an EFB system generates information similar to that generated by
existing cockpit automation, procedures should clearly identify which information source will be
primary, which source will be used for back up information, and under what conditions to use the back
up source. Whenever possible and without compromising innovation in design/use, EFB/user
interfaces should be consistent (but not necessarily identical) with the flight deck design philosophy.
7.3.2 Flight Crew Awareness of EFB Software/Database Revisions
The operator should have a procedure in place to allow flight crews to confirm prior to flight the
revision number and/or date of EFB application software including where applicable, database
versions. However, flight crews should not be required to confirm the revision dates for other
databases that do not adversely affect flight operations, such as maintenance log forms, a list of
airport codes, or the Captain’s Atlas. An example of a date sensitive revision is an aeronautical chart
2 0 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-10 01.10.04
database on a 28-day AIRAC revision cycle. Procedures should specify what actions to take if the
software applications or databases loaded on the EFB system are out-of-date.
7.3.3 Procedures to Mitigate and/or Control Workload
Procedures should be designed to mitigate and/or control additional workloads created by using an
EFB system. The operator should develop procedures such that both flight crewmembers do not
become preoccupied with the EFB system at the same time. Workload should be apportioned
between flight crewmembers to ensure ease of use and continued monitoring of other flight crew
functions and aircraft equipment. These procedures should be strictly applied in flight and should
specify the times at which the flight crew may not use the EFB system.
7.3.4 Defining Flight Crew Responsibilities for Performance Calculations
Procedures should be developed that define any new roles that the flight crew and dispatch office
may have in creating, reviewing, and using performance calculations supported by EFB systems.
7.4 Quality Assurance
The operator should document procedures for the quality control of the EFB system. This should
detail who will be in overall charge of the EFB system, i.e. the EFB Administrator, and who will have
authority to authorise and activate amendments to the hardware and software.
　
中國航空網 m.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：航空資料31(92)