NextGen Technologies

Presented to:

By:

Date:

Federal AviationAdministrationNextGen

Technologies

Electronic Flight Bag (EFB)

135 Air Operators

George Holtman, Principal Avionics Inspector

Thursday August 22, 2013

Federal AviationAdministration

2Safety Summit – 14 CFR Part 135 Air OperatorsThursday, August 22, 2013

Overview

• Hardware and Software

• Guidance Materials

• Authorization Process



Class 1 EFB• Portable COTS-based computers

• Not attached or connected to an aircraft mount

• May be attached to pilot’s leg (kneeboard)

• Considered Portable Electronic Devices (PEDs)

• Must be stowed during critical phases of flight

• May not be subject to an administrative control process for aircraft equipment



Class 2 EFB• Portable COTS-based computers is

considered PEDs• Tools must not be required to remove EFB• Must be connected or attached to an aircraft

mount• May only use aircraft power, have data

connectivity, and use installed antennas• May be authorized to transmit non-essential

AAC-type data• May be authorized for use for all phases of

flight and ground ops• May require RF/Decompression/Altitude

testing• Consist of devices/modules located on the

flight deck that are accessible by the flightcrew

• Must be subject to an administrative control process for aircraft equipment



Class 2 EFB Aircraft Display



EFB Securing Solutions



Yoke-Mounted

• Yoke-Mounted EFBs must be certificated by a design approval by AIR under TC, amended TC, or STC

• All structural and dynamic, as well as wiring protection and security requirements affecting the flight controls, (including autopilot (AP), stall warning, stick pusher, crashworthiness, human factors, etc.), must be addressed prior to installation



Class 3 EFB• Portable modules/components must still fulfill intended function to

qualify as EFB Class 2 PED• If any of the functional EFB system hardware (CPU/Display/Interface) is

“certified,” then EFB system is considered Class 3 regardless of OS



Class 1 • *Portable device• *RD for Type B• *Secured during

critical phases of flight

• *No TC’d A/C data, power, or mount for use

• *Limited by AC 120-76B

Type A & B ApplicationsType A & B Applications

Certified Type C ApplicationsCertified Type C Applications

Class 2 • *Portable device• *Crashworthy-mounted• *EMI/Rapid Decomp/Alt

testing required• *All phases of flight• *Ships power• *Read only airplane

data• *Video interface• *Limited by AC 120-76B

Class 3 • *Installed by TC• *Ships power• *All flight

phases• *Datalink • *Interactive

Apps• *Video interface• *Increased

Functionality

EFB Classes and Authorized UsesPortable Equipment Installed Equipment

Authorization for UseAuthorization for Use



Type A Applications

• May be hosted on any class of hardware

• Must be evaluated and found suitable for intended function

• Do not require an AIR design approval

• Only for use during non-critical phases of flight when pilot workload is reduced

• Examples of Type A software applications are provided in AC 120-76 B, Appendix 1



Type B Applications

• May be hosted on any class of hardware

• Must be evaluated and suitable for intended function

• Do not require an AIR design approval

• May require AEG evaluation• May be used during all phases of

flight• Examples of Type B software

applications are provided in AC 120-76 B, Appendix 2



Type C Applications

• Any certified software applications with AIR design approval

• Includes AIR approved software for Weight and Balance (W&B) and/or aircraft performance

• Includes any software application that displays Own Ship Position



• Hardware and Software• Guidance Materials• Authorization Process

Where We Are in the Presentation



Pertinent EFB Guidance History

FAA AC 120-76B (6/1/12)

FAA AC 91-21.1B (08/25/06)

FAA AC 20-159 (04/30/07)

FAA AC 91-78 (7/20/07)

A061 OpSpecs Guidance (03/14/11)

FAA Order 8900.1 EFB Guidance (04/23/13)

Guidelines For The Certification, Airworthiness, and Operational Approval of EFB Computing Devices

Use of Portable Electronic Devices Aboard Aircraft (Used in conjunction with 8900.1 for authorizing use of EFB)

Obtaining Design And Production Approval Of Airport Moving Map Display (AMMD) Applications Intended For Electronic Flight Bag Systems

Clarified AEG and POI role

Inspector Handbook Volume 4 / Chapter 15 / Section 1EFB Operational Authorization Process

Use of Class 1 or Class 2 Electronic Flight Bag (EFB) Part 91 guidance



Advisory Circular 20-159

AMM (Airport Moving Map) with own-ship position for Class 2 & 3 EFB Systems



Technical Standard Order (TSO)-C165, “Electronic Map Display Equipment for Graphical Depiction of Aircraft Position,” published October, 2003

EFB Class 2 Systems are limited to display of Own-ship for surface operations provided manufacturers comply with AC 20-159

Moving Maps with Own-Ship Position



FAA Order 8900.1 Volume 3

• FAA evaluation process for an EFB follows the same general process for approval and acceptance as described in FAA Order 8900.1, Volume 3, Chapter 1, Section 1



Basic EFB Requirements

• The screen must be large enough to show an entire instrument approach procedure chart at once, with the equivalent degree of legibility and clarity as a paper chart

• The display must also be demonstrated to be readable on the flight deck in direct sunlight



Basic EFB Requirements

• GPS data may be used for map centering when en route charts are displayed

• Map centering may be used as an en route chart feature only and may not be used when an approach chart is displayed

• No own-ship position displayed on a Class 1 or Class 2 EFB in Flight



Rapid Decompression Testing

• RD testing is required to determine an EFB’s functional capability when Type B software applications are used in pressurized aircraft where no alternate procedures or paper backup are available

• Uses RTCA/DO-160 Section 4.6.2 Decompression Test

• Decompression testing may not be required for Class 1 or Class 2 EFBs used in an unpressurized aircraft



Altitude Testing

• Class 1 or Class 2 EFBs may require availability up to the maximum operating altitude of the aircraft

• Compliance to RTCA/DO-160 Section 4.6.1 Altitude Test to at least Category D1 or to the maximum operating altitude of the aircraft, whichever is lower



Electromagnetic Interference/Non-Interference Testing

• Class 1 or Class 2 EFB used in flight ops must have no adverse impact on other aircraft systems (non-interference)

• If used during take-off and landing, Class 1 & 2 EFBs must be tested for non-interference

• Possible interference when portable EFBs are moved about in the cockpit should be addressed



EFB Data Connectivity

Type CapabilityClass 1 • No data connectivity

Class 2 • May have data connectivity (wired or wireless)• Use installed antennas• Read data from aircraft systems • May be authorized to transmit and receive non-essential AAC data• Can be connected to non-essential data buses, file servers, printers, etc.

Class 3 • May have data connectivity (wired or wireless)• Use installed antennas• Read data from aircraft systems • Can be authorized to an essential data bus• Can be authorized to a critical aircraft data bus• Can transmit AOC data



• Hardware and Software• Guidance Materials• Authorization Process

Where We Are in the Presentation



Authorization Process

• FAA Order 8900.1– Volume 3, Chapter 1, Section 1 “The general

process for approval and acceptance”– Volume 4, Chapter 15, Section 1 “ Electronic Flight

Bag Authorization For Use”• Phase 1 - Initiation• Phase 2 - Required Application Information• Phase 3 - POI Review• Phase 4 - Temporary Authorization to use an EFB• Phase 5 - Authorization to Use an EFB



Phase One: Authorization Request

• Begins when the operator requests authorization to use the EFB from the FAA

• During this phase, the FAA and the operator reach a common understanding of the role of the FAA and what documents and actions the operator is responsible for during each phase of the authorization process



Phase Two: Application Submission

• Phase two begins when the operator submits a formal EFB plan to the POI for evaluation.

• The plan is reviewed for completeness and the POI facilitates coordination with other inspectors and FAA offices, as necessary.



Phase Two: Application Package

• EFB hardware and application specifications– Complete provided Checklist (Figure 4-76 & 4-81, Evaluation

Report Information Template)

• EFB operator procedures/manual revisions– As a stand alone Standard Operating Procedures or

Incorporated into the GOM• Identifies EFB Hardware & Software / Maintenance Procedures /

Operational Procedures / Appendices for user guides and forms

EFB cockpit procedures checklists– Validation of flight testing

• A means of documenting anomalies or non-events• Log flight hours, marking time (6 months)



Phase Two continued

• EFB Training Program– Incorporated into company training program

• EFB Evaluation Report– Complete provided checklist (Figures 4-79 & 4-80)

• Rapid Decompression Test Data



Phase Two continued

• Completed non-interference test results– Previously CHDO accepted ground testing

procedure.

• Airworthiness documents for Class 2 equipment



Phase Three: POI Review

• POI must use the checklist found in Figure 4-78, to conduct a review of the application submitted by an operator

• All PI specialties should coordinate the review of an operator’s EFB program



Phase Four: Interim Authorization

• An interim EFB authorization is granted to allow the user/operator to proceed with EFB validation testing. During this validation phase, the operator must maintain a paper backup of all electronic information.

• Evaluation report is the end of phase 4 (8900 fig. 4-82)



Phase Five: Final Authorization

• Authorization to Use an EFB. An operator subject to regulations under 14 CFR parts 91K, 121, 125 (including part 125M), and 135 is granted authorization to use an EFB through OpSpecs A061 only after acceptable completion of validation testing (see Volume 3, Chapter 18).

• Use Fig. 4-82 EFB Line Evaluation Checklist



New Electronic Flight Bags… New Questions

iPad II

and Beyond



Questions

Comments

Documents

NextGen Technologies