Android Tablets as Electronic Flight Bags (EFBs) – Part 1

Introduction

Electronic Flight Bags (EFB’s) are any combination of hardware and software used to replace or augment the information we normally use in flight, such as Pilot’s Operating Handbook (POH), Checklists, and printed navigation information (Sectionals, WAC Charts, Approach Plates, TAC Charts, etc.).

Over the years we have had some excellent guest speakers come to EAA Chapter 14 to extol the virtues of the Apple i-Pad Tablet and its well-populated eco-system of aviation applications such as ForeFlight and Wing-X, but there are those of us out there who prefer the Android Operating System from Google to the IOS Operating System from Apple. For some time the Apple eco-system was significantly better represented with respect to aviation applications but over the past 5 years that imbalance has largely disappeared, especially with the focus on Android by Garmin with their excellent Pilot application.

I am one of the people who prefer Android to IOS, so, this will be a 5-part series covering the use of Android Tablets as EFB’s and will be divided as follows:
• Part 1 (this article) will be an introduction to the EFB, the Regulatory environment and Terminology
• Part 2 will discuss Software/Applications
• Part 3 will discuss Hardware
• Part 4 will discuss Accessories
• Part 5 will discuss Training and Simulation

Brief Overview of my Background/Interest in the Subject

I became interested in the Electronic Flight Bag concept while working as Manager of Service and Support Engineering for Eclipse Aviation in Albuquerque, NM. The Eclipse was originally to have been a very advanced/technologically integrated airplane and among our early concepts was the then new idea of paperless cockpits and Electronic Flight Bags. In late 2001 I travelled to Washington DC to support the final NPRM meeting at FAA Headquarters because we were interested in ensuring that the regulatory environment for EFB’s would support our expected Part 91 (non-commercial), Part 91K (Fractional) and Part 135 (Charter On Demand) operators.

During this meeting AOPA had fought for and gained an exemption for all non-commercial Part 91 operations, but it was clear that the FAA intended to develop an Advisory Circular to address certification and approval requirements for commercial use. At the end of the meeting, FAA asked for volunteers from the Hardware, Software, Operator and OEM community to participate in the development of this proposed AC, and I joined the team that was to write the AC as the sole representative for General Aviation Original Equipment Manufacturers (OEM’s).

Over many meetings this team developed the original EFB AC, AC120-76 and it was released in July of 2002. We developed a follow-on update AC 120-76A which was released in March of 2003 to address some lessons learned early on, and FAA released a further update in June of 2012.

Regulatory Environment

The current regulatory guidance material covering the use and approval (if/as needed) for EFB’s can be found in two AC’s, AC91-78 Use of Class 1 or Class 2 Electronic Flight Bag (EFB) issued 07/20/07, and the aforementioned AC 120-76B Guidelines for the Certification, Airworthiness, and Operational Use of Electronic Flight Bags issued 6/1/12.

For this series, we will quickly review both but I recommend anyone who intends to use an EFB make their own detailed review of these resources and be very familiar with what they do and do not allow.

Most of this series will focus on the use of Portable Electronic Devices (PED’s) specifically Android Tablets, which are classified as Class I EFB’s, combined with Type A and Type B software/applications.

AC91-78 Use of Class 1 or Class 2 Electronic Flight Bag (EFB)

This is the AC that governs the use of EFB’s with respect to paperless operations for most Part 91 pilots and operators.
From the AC itself:

6. REMOVAL OF PAPER FROM THE COCKPIT FOR OPERATIONS UNDER PART 91.
a. EFBs/ECDs can be used during all phases of flight operations in lieu of paper reference material when the information displayed meets the following criteria:
(1) The components or systems onboard the aircraft which display precomposed or interactive information are the functional equivalent of the paper reference material.
(2) The interactive or precomposed information being used for navigation or performance planning is current, up-to-date, and valid.
NOTE: Supporting reference material such as legends, glossaries, abbreviations, and other information is available to the pilot but is not required in the cockpit during operation.
b. The in-flight use of an EFB/ECD in lieu of paper reference material is the decision of the aircraft operator and the pilot in command. Any Type A or Type B EFB application, as defined in AC 120-76A may be substituted for the paper equivalent. It requires no formal operational approval as long as the guidelines of this AC are followed.
c. It is suggested that a secondary or back up source of aeronautical information necessary for the flight be available to the pilot in the aircraft. The secondary or backup information may be either traditional paper-based material or displayed electronically.
7. GENERAL CONSIDERATIONS. The in-flight use of EFB systems to depict images in lieu of paper reference material is the decision of the aircraft operator and the pilot-in-command. Any Type A or Type B EFB application, as defined in AC 120-76A, may be substituted for the paper equivalent. It is suggested that a secondary or backup source of aeronautical information or paper reference material necessary for the flight be available to the pilot in the aircraft. The secondary or backup information may be either traditional paper-based material or displayed electronically by other means. Class 1 and Class 2 EFB can be used during all phases of flight operations in lieu of paper reference material when the information displayed meets the following criteria:
a. The EFB system does not replace any system or equipment (e.g. navigation, communication, or surveillance system) that is required by 14 CFR part 91.
b. The EFB system on board the aircraft displays only precomposed or interactive information which are functionally equivalent to the paper reference material which the information is replacing or is substituted for.
c. The interactive or precomposed information being used for navigation or performance planning is current, up-to-date, and valid, as verified by the pilot.
d. The operator complies with requirements of 14 CFR part 91, § 91.21 to ensure that the use of the EFB does not interfere with equipment or systems required for flight.

As can be seen above, a pilot who proposes to replace paper manuals and or navigation products in non-commercial Part 91 VFR/IFR flight has options, but also has some responsibility insofar as determining fitness for use, non-interference, and especially with respect to not using an EFB to replace required systems and equipment. We’ll touch on that again throughout this series.

AC 120-76B Guidelines for the Certification, Airworthiness, and Operational Use of Electronic Flight Bags

This is the AC that provides the terminology foundation for this series – the actual guidance found in AC 120-76B really applies to Large and Turbine Powered Aircraft (Part 91 F, e.g., Gulfstreams) and Part 91 K Operators (Fractional) as well as Scheduled Airline and On-Demand Charter Operators (Part 121, 125 and 135). That said, anyone who intends to fly with an EFB should become familiar with this material and specifically the various definitions provided.

From the AC itself:
1. PURPOSE. This joint Flight Standards Service (AFS) and Aircraft Certification Service (AIR) advisory circular (AC) contains guidance on the operational use of Electronic Flight Bags (EFB). It is intended for all operators conducting flight operations under Title 14 of the Code of Federal Regulations (14 CFR) part 121, 125, 135, or 91 subpart F (part 91F) and part 91 subpart K (part 91K) who want to replace required paper information with an EFB. This AC sets forth an acceptable means, but not the only means, to obtain Federal Aviation Administration (FAA) authorization for the operational use of EFBs. Part 91 operators can find additional EFB information in the current edition of AC 91-78, Use of Class 1 or Class 2 Electronic Flight Bag (EFB). For guidance on the installation of EFB components, refer to the current edition of AC 20-173,
Installation of Electronic Flight Bag Components.

Terminology

The following are definitions taken directly from AC 91-78 and AC 120-76B; they form the basic terminology for this series of articles.

AC 91-78 Definitions

Electronic Flight Bag (EFB). An electronic display system intended primarily for cockpit or cabin use. EFB devices can display a variety of aviation data (e.g., checklists, navigation charts, pilot’s operating handbook (POH)) or perform basic calculations (e.g., performance data, fuel calculations). The scope of the EFB system functionality may also include various other hosted databases and applications. Physical EFB displays may be portable (Class 1), attached to a mounting device (Class 2), or built into the aircraft (Class 3).

Electronic Chart Display (ECD). A display device that presents a comprehensive depiction of interactive information and/or precomposed information that is the functional equivalent of a paper aeronautical chart. An ECD may be a device installed in the instrument panel of an aircraft or a portable device. (ICAO, Annex 4, Chapter 20.) An ECD is not a multi-function display (MFD) that is permanently installed into an aircraft that is designed under a technical standard order (TSO). However an MFD may incorporate databases that depict checklists, navigation charts, POH, etc.

Precomposed Information. Information that is previously composed into a static, composed state (non-interactive). The composed displays have consistent, defined, and verifiable content, and formats that are fixed in composition.

Interactive Information. Information presented on the EFB or ECD that, via software applications, can be selected and rendered in a number of dynamic ways. This includes variables in the information presented based on data-oriented software algorithms, concepts of decluttering, and “on-the-fly” composition as opposed to precomposed information.

AC 120-76B Definitions

Administrative Control Process. Operator-administered procedure to record and log the removal or addition of installed EFB components.

Approved Software. Software approved by the FAA using the current edition of RTCA/DO-178, Software Considerations in Airborne Systems and Equipment Certification, compliance, or other acceptable means.

Class 1 Electronic Flight Bag (EFB) Hardware. Portable commercial off-the-shelf (COTS)-based computers, considered to be portable electronic devices (PED) with no FAA design, production, or installation approval for the device and its internal components. Class 1 EFBs are not mounted to the aircraft, connected to aircraft systems for data, or connected to a dedicated aircraft power supply. Class 1 EFBs can be temporarily connected to an existing aircraft power supply for battery recharging. Class 1 EFBs that have Type B applications for aeronautical charts, approach charts, or an electronic checklist must be appropriately secured and viewable during critical phases of flight and must not interfere with flight control movement.

(Portable Class 1 EFB components are not considered to be part of aircraft type design; i.e., not in the aircraft type certificate (TC) or Supplemental Type Certificate (STC).)

Class 2 EFB Hardware. Portable COTS-based computers, considered to be PEDs with no FAA design, production, or installation approval for the device and its internal components. Class 2 EFBs are typically mounted. They must be capable of being easily removed from or attached to their mounts by flightcrew personnel. Class 2 EFBs can be temporarily connected to an existing aircraft power supply for battery recharging. They may connect to aircraft power, data ports (wired or wireless), or installed antennas, provided those connections are installed in accordance with AC 20-173. (Portable Class 2 EFB components are not considered to be part of aircraft type design; i.e., not in the aircraft TC or STC.)

Class 3 EFB Hardware. EFBs installed in accordance with applicable airworthiness regulations. Refer to AC 20-173 for guidance on the installation of EFB components.

Critical Phases of Flight. Includes all ground operations involving taxi, takeoff, and landing, and all other flight operations conducted below 10,000 feet, except cruise flight.

NOTE: For the purpose of this AC, we’ve adopted the critical phases of flight definition in part 121, § 121.542.

Electronic Flight Bag (EFB). An electronic display system intended primarily for flight deck use that includes the hardware and software necessary to support an intended function. EFB devices can display a variety of aviation data or perform basic calculations (e.g., performance data, fuel calculations, etc.). In the past, some of these functions were traditionally accomplished using paper references or were based on data provided to the flightcrew by an airline’s flight dispatch function. The scope of the EFB functionality may include various other hosted databases and applications. Physical EFB displays may use various technologies, formats, and forms of communication. An EFB must be able to host Type A and/or Type B software applications.

Hosted Application. Software running on an EFB that is not installed or considered part of aircraft type design.

Interactive Information. Information presented on the EFB that, via software applications, can be selected and rendered in a number of dynamic ways. This includes variables in the information presented based on data-oriented software algorithms, concepts of decluttering, and selectable composition as opposed to precomposed information.

Mounted. Any portable device that is attached to a permanently installed mounting device.

Mounting Device. These include arm-mounted, cradle, clips, docking stations, etc.

Portable Electronic Device (PED). Section 91.21; § 121.306; part 125, § 125.204; and part 135, § 135.144 refer to PEDs and place restrictions on the in-flight use of PEDs. There are two types of PEDs and two methods of compliance with these regulations.

The non-EFB PED method of compliance with PED regulations is in the current edition of AC 91.21-1, Use of Portable Electronic Devices Aboard Aircraft. Use of these PEDs is prohibited in instrument flight rules (IFR) flight operations, except in cruise flight.

The EFB PED method of compliance with PED regulations is in FAA Order 8900.1, Flight Standards Information Management System (FSIMS), and this AC.

Precomposed Information. Information previously composed into a static, composed state (non-interactive). The composed displays have consistent, defined, and verifiable content, and formats that are fixed in composition.

Stowed. A portable device that is placed in a secure stowage location but is not available for use or view by the pilot in that location.

Transmitting Portable Electronic Devices (T-PED). PEDs that have intended radio frequency (RF) transmission capabilities.

Type A Software Applications. Type A applications are those paper replacement applications primarily intended for use during flight planning, on the ground, or during noncritical phases of flight. Examples of Type A software applications are listed in Appendix 1.

Type B Software Applications. Type B applications are those paper replacement applications that provide the aeronautical information required to be accessible for each flight at the pilot station and are primarily intended for use during flight planning and all phases of flight. Type B applications include miscellaneous, non-required applications (e.g., aircraft cabin and exterior surveillance video displays, maintenance applications). Examples of Type B software applications are listed in Appendix 2.

Type C Software Applications. Software approved by the FAA using RTCA/DO-178B compliance or another acceptable means. These are non-EFB software applications found in avionics and include intended functions for communications, navigation, and surveillance that require FAA design, production, and installation approval. Type C applications are for airborne functions with a failure condition classification considered to be a major hazard or higher.

Viewable Stowage. A portable device that is secured in an existing provision with the intended function to hold charts or acceptable portable device viewable to the pilot (e.g., kneeboards).

Summary

The FAA has put quite a bit of effort into the EFB regulatory environment, most of which is not directly applicable to the type of operations most of us engage in, specifically Part 91 non-commercial Day/Night VFR/IFR flight. This series has been written to provide an overview of the Regulatory Environment, Hardware and Software options in the Android eco-system, Accessories for use with Android EFB’s, and to suggest some Training and Simulation options.

The next article will introduce several Android Applications that can function as Type A and Type B Software as defined by FAA. I will provide reviews of applications I have personally used, along with overviews of other applications I am not personally familiar with, including pricing, installation, and where to go for more information or to download or purchase. We will talk applications first since choice of application and intended use will drive the next article which is hardware selection (which device to buy).

References

These references can all be found on the FAA website (www.faa.gov) and can be downloaded or printed for free.

Part 91

• Section 91.21, Portable electronic devices (Subpart A-General)
• Section 91.103, Preflight action (Subpart B-Flight Rules)
• Section 91.503, Flying equipment and operating information (Subpart F-Large and Turbine-Powered Multiengine Airplanes and Fractional Ownership Program Aircraft)
• Section 91.1033, Operating information required (Subpart K-Fractional Ownership Operations)

ACs

• AC 91-21.1B, Use of Portable Electronic Devices Aboard Aircraft
• AC 120-76B, Guidelines for the Certification, Airworthiness, and Operational Approval of Electronic Flight Bag Computing Devices

Miscellaneous

• FAA Notice N 8200.98, Electronic Flight Bag Job Aid.

About the Author

John Knolla is currently Manager, Product Support Engineering Group for an Engineering Services company in San Diego, CA. He has nearly 20 years of Technical and Management experience in Reliability, Maintainability & Safety Engineering, Integrated Logistics Support, Systems and Project Engineering, and Technical Documentation supporting Aerospace and Defense companies such as Hawker-Beechcraft Corporation, Eclipse Aviation, Dassault FalconJet, ITT, BAE Systems, Mitsubishi Aircraft Corporation, Embraer, and The Spaceship Company.

He has served on Air Transport Association (ATA) Working Groups defining Digital Display and Flight Operations approaches for the airline industry, and the FAA/industry panel that developed Advisory Circular AC120-76/120-76A Guidelines for the Certification, Airworthiness and Operational Use of Electronic Flight Bags.

He currently holds an Instrument Rating and Commercial Pilot’s License and has flight experience in more than 30 different make/model fixed and rotary wing aircraft. John maintains membership in EAA (since 1987), AOPA, the International Aerobatic Club (IAC), the Academy of Model Aeronautics (AMA) and the Redstar Pilot’s Association (RPA).