OPERATIONAL SUITABILITY REPORT

 

 

TELEDYNE CONTROLS

 

Onboard Performance System (OPS)

Electronic Flight Bag (EFB)

 

Application Software

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

DATE: 

 

James M. Eitel

EFB Flight Standardization Board

Seattle Aircraft Evaluation Group

 

 

Federal Aviation Administration

Seattle Aircraft Evaluation Group (SEA AEG)

1601 Lind Ave NW

Renton , Washington 98057

Telephone:  (425) 917-6600

FAX:  (425) 917-6638


MANAGEMENT COORDINATION SHEET

 

 

 

 

 

 

 

Steve Cummins                                                                                               Date

Assistant Manager, Operations

Seattle Aircraft Evaluation Group

 

 

 

 

 

Keeton Zachary                                                                                               Date

Manager

Seattle Aircraft Evaluation Group

 

 

 

 

 

Tom Toula (AFS-200)          /s/                                                             Date   07/03/2007

Manager

Air Transportation Division

 


Table of Contents

 

span style='color:windowtext'

span style='color:windowtext'

span style='color:windowtext'

span style='color:windowtext'

span style='color:windowtext'

span style='color:windowtext'

span style='color:windowtext'

span style='color:windowtext'

span style='color:windowtext'

span style='color:windowtext'

span style='color:windowtext'

span style='color:windowtext'

span style='color:windowtext'

span style='color:windowtext'

span style='color:windowtext'

span style='color:windowtext'

span style='color:windowtext'

span style='color:windowtext'

Appendix 2............................................................................................................................. 10


1

This Flight Standardization Board (FSB) report specifies FAA requirements resulting from the Seattle Aircraft Evaluation Group’s evaluation for operational suitability of the Teledyne Controls Onboard Performance System (OPS) with software (Type “B”), that is applicable to operators seeking operations approval for its use under applicable 14 CFR.  The applications of this report are applicable to B-727, B737, B-737NG, B-747, B-747-400, B-757/767, E190, DC-8, MD-11, A-300 and A-320/321 aircraft.  Provisions of this report are consistent with the guidance defined in FAA Advisory Circular 120-76A and assume that appropriate airworthiness certification for installation of the EFB hardware is accomplished.

The Seattle AEG has determined that the Teledyne Controls Onboard Performance System (OPS) with Type “B” software as evaluated and reported herein, satisfy the requirements of FAA AC120-76A for approval.  This report does not constitute operational approval; therefore, individual operators will need to obtain approval from their Principal Inspector prior to use of these applications.  Approval to use the EFB and these applications will be contained in paragraph A025 of the Operations Specifications (OpsSpecs) for Part 121 and Part 135 operators, or in the Management Specifications (MSpecs) for Part 91K operators.

The following information related to obtaining operational approval for this device is included:

·                A general description of the EFB application approved under this report, including:

·                The applicable operating system and version

·                A list of the applications reviewed under this report.

·                Typical acceptable procedures for EFB use during all phases of flight

·                A revision process procedure/method that ensures appropriate database accuracy and currency

·                FSB specifications for training and typical acceptable training course description

·                FSB specifications for Checking including specification of those checks that must be administered by FAA or operators

·                FSB specifications for Currency

·                Changes to the Operating System

·                Configuration Control – including procedures governing the distribution of updates to the EFB configuration Compliance Checklist

·                FSB Specifications for Devices and Simulators

·                Alternate Means of Compliance

·                List of documents or their airline equivalents needed to meet the requirements of AC120-76A for operational approval and continued airworthiness. (Appendix 1)

·                List regulatory compliance status (compliance checklist) for pertinent parts of the FARs (Appendix 2)

 

 

2                Application Description

 

The Onboard Performance System (OPS) software application provides real-time Takeoff and Landing data, along with Weight and Balance calculations (optional module) under all combinations of environmental, airport, and aircraft systems conditions.  The primary source document for the takeoff and landing modules is the FAA Approved Airplane Flight Manual (AFM).

 

·                The OPS Takeoff module determines the maximum allowable takeoff weight, considering the requirements of FAR 121.189 as well as to provide related operational data such as takeoff speeds, flap setting and engine thrust settings.

 

·                The OPS Dispatch Landing module determines the maximum allowable landing weight at the destination airport, considering the requirements of FAR 121.195, and at the alternate airport, considering the requirements of FAR 121.197.

 

·                The OPS Operational Landing module determines operational landing data, including required landing distances, approach and landing speeds and go-around engine thrust settings.

 

The optional Weight and Balance module is designed for and meets the following objectives (in accordance with the Airplane Weight and Balance Manual):

 

·                Assurance that the design weight limitations are observed, and

 

·                Assurance that the design center-of-gravity limits are not exceeded, and

 

·                In combination with the Takeoff Performance Module of OPS, the proper stabilizer setting for takeoff.

 

FAR 121.141 permits a certificate holder to carry a manual that meets the requirements of FAR 121.133 on board a transport category aircraft in lieu of the approved Airplane Flight Manual (AFM). As part of the substitute manual, a certificate holder is allowed to modify the presentation of the performance data from the AFM if the modified presentation is approved and clearly identified as AFM requirements. OPS is intended to supplement the Operator’s manual and provide the performance data from the AFM.

 

Three Operations Aviation Safety Inspectors from the Seattle Aircraft Evaluation Group (AEG) performed the Operational Suitability Evaluation in accordance with AC 120-76A of Teledyne Controls performance software  The Electronic Flight Bag (EFB) application provides enhanced electronic performance and weight and balance data traditionally provided in paper form. 

span style='font-size:11.0pt;font-weight:normal; font-style:normal'

This performance software is developed by Teledyne Controls. 

span style='font-size:11.0pt;font-weight:normal;font-style:normal'

The performance software was demonstrated on a Hammerhead Computer (HH3 or XRT); however, the application is acceptable for use on all models of electronic flight bag hardware running under MicroSoft™ Windows 98®, Windows 2000® or Windows XP® software.

2.3                OPS Substantiation Reports

 

Each version of OPS software used to show compliance with Federal Aviation Administration (FAA), or other operating regulations is verified for accuracy prior to release for general use. A unique version number is assigned to each version.

 

A Substantiation Report is prepared by Teledyne Controls for each airframe/engine combination. The report contains the following information:

 

· Specific airframe/engine configuration AFM applicability

· Software Identification including specific operating system and compilers

· Data table cross-reference list

· Printed plots of all digitized source document data

· Definition of a matrix of test cases

· Written comparison of the manually obtained results to OPS results for the matrix of test cases

· Printed trace output for the matrix of test cases

 

The following OPS substantiation reports were presented and found operationally suitable for this FSB report:

 

Takeoff and Landing   A-300-622                   PW4158

Takeoff and Landing   A-320-212                   CFM56-5-A3

Takeoff and Landing   A-320-214                   CFM56-5-B4

Takeoff and Landing   A-320-232                   V2527-A5

Takeoff and Landing   A-321-231                   V2533-A5

Takeoff and Landing   B-727-100QF              TAY651-54

Takeoff and Landing   B-727-200R                JT8D-9

Takeoff and Landing   B-727-200R                JT8D-15

Takeoff and Landing   B-737-400                   CFM56-3C1

Takeoff and Landing   B-737-500                   CFM56-3B1

Takeoff and Landing   B-737-700                   CFM56—20-24

Takeoff and Landing   B-737-700                   CFM56-7B27A

Takeoff and Landing   B-737-800                   CFM56-7B27

Takeoff and Landing   B-747-100                   JT9D-7A

Takeoff and Landing   B-747-200                   JT9D-7Q

Takeoff and Landing   B-747-200                   JT9D-7F/J

Takeoff and Landing   B-747-200                   JT9D-7R4G2

Takeoff and Landing   B-747-200/300            CF6-50E2

Takeoff and Landing   B-747-400                   CF6-80C2B5F

Takeoff and Landing   B-757-200                   RB211-535E4

Takeoff and Landing   B-757-200                   PW2037/2040

Takeoff and Landing   B-767-300                   CF6-80C2B6F

Takeoff and Landing   DC-8-71/73                 CFM56-2-C1

Takeoff and Landing   DC-10-10                    CF6-6D/D1/D1A

Takeoff and Landing   DC-10-10                    CF6-6K/K2

Takeoff and Landing   DC-10-30                    CF6-50C2/C2B

Takeoff and Landing   E-190-100                   CF34-10E6

Takeoff and Landing   MD-11                         PW4460/4462

Takeoff and Landing   MD-11                         CF6-80C2D1F

 

A weight and Balance Substantiation Report is prepared by Teledyne Controls for those operators using the optional weight and balance module.  It describes and substantiates the methods used by the Weight and Balance module of OPS for each specific airplane layout. 

span style='font-size:11.0pt;font-weight:normal; font-style:normal'

This EFB has been demonstrated and has been approved for use with MicroSoft™ Windows 98®, Windows XP® or Windows 2000® software.

2.5                Applications

The following software applications supplied by Teledyne Controls have been demonstrated and evaluated for operational suitability.  Airplane specific information used in these applications is applicable to B-727, B737, B-737NG, B-747, B-747-400, B-757/767, E190, DC-8, MD-11, A-300 and A-320/321 aircraft

2.5.1          “Type A” Applications

 

2.5.1.1            No “Type A” applications were presented for this evaluation.

2.5.2           “Type B” Applications

2.5.2.1            “Type B” applications (and version for each application) were evaluated and have been determined to be operational suitable for the following functions:

 

§                            Performance calculations (Takeoff and Landing)

§                            Runway limiting performance calculations

§                            Weight and Balance calculations

2.5.3          “Type C” Applications

2.5.3.1            No “Type C” applications were presented for this evaluation.

 

3                 EFB Mounting System

3.1                Not applicable to this report.

4                 EFB Display Lighting and Reflectivity

4.1                Not applicable to this report.

5                 Operations Manual Procedures for Use of EFB

5.1    Normal operating procedures should be included in the applicable operator’s airplane Flight Crew Operations Manual and Flight Crew Training Manual, or equivalent.  Descriptions of specific applications are contained in a “user guide” supplied by Teledyne Controls.

5.2              There are no Non-Normal procedures associated with the EFB.

6 EFB Data Revision Process

6.1                An airport database, containing airport-specific information such as runway lengths, slopes, obstacle heights/distances is required by the OPS application.  The operator is responsible for providing the airport database and should have procedures in place to ensure its currency.

6.2                An acceptable data revision process is to use an established secure data distribution network.  EFB Data will be loaded to hardware using procedures specified by the hardware manufacturer.  The data distribution system must include the procedures to protect the Teledyne performance software from virus infection and other threats to the operating system. It must also include the process by which the operator assures that the data distribution system assures delivery and installation of the updates.

7

7.1                Programs Crediting Previous Performance Software Experience.   Training programs for the performance software may take credit for previous performance experience. For example, previous experience using a Type B performance software application using similar software may be credited toward training.  Principal Inspectors for operators initially introducing a new performance software system may approve programs consistent with programs previously approved.  For information regarding previously approved programs or programs crediting previous performance software experience, FAA Principal Inspectors for other operators may be consulted.

7.2                Initial Training.   Pilots should be trained to proficiency using Level C training (i.e. classroom instruction, pictures, videotape, ground training devices, interactive computer-based instruction and static aircraft training) as reviewed and evaluated for operational suitability by the SEA AEG.

7.3                Areas of Emphasis Operators must emphasize during initial line operating experience, the need to avoid fixation on the display during critical phases of flight, including taxi operations.

7.4                Recurrent Training.   Recurrent training is not required for EFB operation provided the functions are used regularly in line operations.  Operators should include EFB as a component of simulator recurrent training.

8

8.1                Checking.   Pertinent knowledge and procedures for EFB use should be checked following initial and recurrent training.  This checking may be accomplished as an automated component of EFB computer-based training.

8.2                Areas of emphasis.   The following areas of emphasis should be addressed during checks:

§                Proficiency with use of EFB application,

§                Proper cross-check of data entered into the performance application.

9

9.1                If an operator’s flight personnel use their EFB System regularly, no specific currency requirements will apply to the EFB.

10     Electromagnetic Interference (E.M.I.)

10.1        Not applicable to this report.

11     Rapid Depressurization Testing

Not applicable to this report

12     Operating System

12.1        Changes to the Windows operating system that involve .exe, .dll files or Java scripts will require that the operator notify the FAA Principal Inspector that the operation of all approved applications continue to meet their intended functions.

13     Configuration Control

13.1        The operator shall ensure, to the satisfaction of the assigned FAA Principal Operations Inspector that procedures are in place to manage the software configuration of any Class 1 EFBs that will be in operational use.

14     Instructions for Continued Airworthiness

14.1        Not applicable to this report.

15     Compliance Checklist

15.1        Compliance Checklist (see Appendix 2). Compliance checklists if required are provided as an aid to identify those specific rules or policies for which compliance has already been demonstrated to FAA.  The checklist also notes rules or policies which must be demonstrated to CHDOs by the operator.  Not all rules or policies or variants are necessarily listed or addressed.

16     FSB Specifications for Devices And Simulators

16.1        Training Device. The EFB must be taught on a commercial over the shelf (COTS) computer or the actual hardware planned for use by flight crews.

16.2        Simulator.  For “paperless” cockpit operations, th e EFB must be available in simulators used for training unless aircraft training or supervised flight segments are included in the operator’s training program.

17

17.1        Approval Level and Approval Criteria.   FAA will generally not consider relief through alternate compliance means, unless sufficient lead time has been planned by an operator to allow for any necessary testing and evaluation.  Alternate means of compliance to the provisions of this report must be approved by AFS-200.  If alternate compliance is sought, operators will be required to establish that any proposed alternate means provides an equivalent level of safety to the provisions of AC 120-76A and this FSB report.  Analysis, demonstrations, proof of concept testing, differences documentation, or other evidence may be required.

17.2        Requires Equivalent Safet y.  In the event alternate compliance is sought, reductions in training program hours and approvals of simulators or devices may be significantly limited and reporting requirements may be increased to assure equivalent levels of safety. 

17.3        Unforeseen Circumstances.  In the event of clearly unforeseen circumstances in which it is not possible for an operator to comply with report provisions, the operators may seek an interim equivalent program rather than a permanent alternate compliance method.  Financial arrangements, schedule adjustment, and other such reasons are not considered “unforeseen circumstances” for the purposes of this provision.


Appendix 1

 

The following documents have been reviewed and evaluated by the SEA AEG during the determination of this report.

 

Teledyne Controls, OPS Substantiation Report Takeoff and Landing, A300-622/PW4158

Teledyne Controls, OPS Substantiation Report Takeoff and Landing, A320-212/CFM56-5-A3

Teledyne Controls, OPS Substantiation Report Takeoff and Landing, A320-214/CFM56-5-B4

Teledyne Controls, OPS Substantiation Report Takeoff and Landing, A320-232/ V2527-A5

Teledyne Controls, OPS Substantiation Report Takeoff and Landing, A321-231/V2533-A5

Teledyne Controls, OPS Substantiation Report Takeoff and Landing, B727-100QF/TAY651-54

Teledyne Controls, OPS Substantiation Report Takeoff and Landing, B727-200R/JT8D-9

Teledyne Controls, OPS Substantiation Report Takeoff and Landing, B727-200R/JT8D-15

Teledyne Controls, OPS Substantiation Report Takeoff and Landing, B737-400/ CFM56-3C1

Teledyne Controls, OPS Substantiation Report Takeoff and Landing, B737-500/ CFM56-3B1

Teledyne Controls, OPS Substantiation Report Takeoff and Landing, B737-700/CFM56-20-24

Teledyne Controls, OPS Substantiation Report Takeoff and Landing, B737-700/CFM56-7B27A

Teledyne Controls, OPS Substantiation Report Takeoff and Landing, B737-800/CFM56-7B27

Teledyne Controls, OPS Substantiation Report Takeoff and Landing, B747-100/JT9D-7A

Teledyne Controls, OPS Substantiation Report Takeoff and Landing, B747-200/JT9D-7F

Teledyne Controls, OPS Substantiation Report Takeoff and Landing, B747-200/JT9D-7J

Teledyne Controls, OPS Substantiation Report Takeoff and Landing, B747-200/JT9D-7Q

Teledyne Controls, OPS Substantiation Report Takeoff and Landing, B747-200/JT9D-7R4G2

Teledyne Controls, OPS Substantiation Report Takeoff and Landing, B747-200/300/CF6-50E2

Teledyne Controls, OPS Substantiation Report Takeoff and Landing, B747-400/CF6-80C2B5F

Teledyne Controls, OPS Substantiation Report Takeoff and Landing, B757-200/RB211-535E4

Teledyne Controls, OPS Substantiation Report Takeoff and Landing, B757-200/PW2037/2040

Teledyne Controls, OPS Substantiation Report Takeoff and Landing, B767-300/CF6-80C2B6F

Teledyne Controls, OPS Substantiation Report Takeoff and Landing, DC-8-71/CFM56-2-C1

Teledyne Controls, OPS Substantiation Report Takeoff and Landing, DC-8-73/CFM56-2-C1

Teledyne Controls, OPS Substantiation Report Takeoff and Landing, DC-10-10/CF6-6D/D1/D1A

Teledyne Controls, OPS Substantiation Report Takeoff and Landing, DC-10-10/CF6-6K/K2

Teledyne Controls, OPS Substantiation Report Takeoff and Landing, DC-10-30/CF6-50C2/C2B

Teledyne Controls, OPS Substantiation Report Takeoff and Landing, EMB190-100/ CF34-10E6

Teledyne Controls, OPS Substantiation Report Takeoff and Landing, MD-11/PW4460/4462

Teledyne Controls, OPS Substantiation Report Takeoff and Landing, MD-11/CF6-80C2D1F

 


Appendix 2

Compliance Checklist

 

1. TITLE 14 OF THE CODE OF FEDERAL REGULATIONS (14 CFR).

 

The following regulations apply:

 

(1) Title 14 CFR §§ 91.103(b), 91.175(a), 91.503(a)(4).

 

(2) Title 14 CFR § 121 – 121.97(b), 121.97(c), 121.117(b), 121.117(c), 121.135(a), 121.135(b)(8)(i) / (iv) / (v).

 

(3) Title 14 CFR §§ 125 – 125.215(a)(4).

 

(4) Title 14 CFR §§ 135.23(r), 135.83(a)(4).

 

 

2. FEDERAL AVIATION ADMINISTRATION (FAA) ADVISORY CIRCULARS (AC), ORDERS, POLICY STATEMENTS, AND TECHNICAL STANDARD ORDERS (TSO).

        a. ACs (current version)

 

AC-120-76A

 

        b. FAA Orders, Policy Statements, and TSOs (current version).

 

Order 8400.10     CHDO

Order 8300.10     CHDO