1 / 35

NextGen Technologies

NextGen Technologies. Electronic Flight Bag (EFB). 135 Air Operators. George Holtman, Principal Avionics Inspector. Thursday April 19, 2012. Overview. Hardware and Software Guidance Materials Authorization Process. Class 1 EFB. Portable COTS-based computers

alaric
Download Presentation

NextGen Technologies

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. NextGen Technologies Electronic Flight Bag (EFB) 135 Air Operators George Holtman, Principal Avionics Inspector Thursday April 19, 2012

  2. Overview • Hardware and Software • Guidance Materials • Authorization Process

  3. 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

  4. 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

  5. Class 2 EFB Aircraft Display

  6. EFB Securing Solutions

  7. 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

  8. 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

  9. EFB MAIN MENU CHARTS DOCUMENTS VIDEO TAXI MAPS LOGBOOK PERFORMANCE SYSTEM PAGE INITIALIZE FLT Boeing Class 3 “Installed” EFB Type “A” Type “B” Type “B” Type “C” Type “A” Type “B”

  10. EFB Classes and Authorized Uses Portable Equipment Installed Equipment 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-76A Class 3 • Installed by TC • Ships power • All flight phases • Datalink • Interactive Apps • Video interface • Increased Functionality 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-76A Certified Type C Applications Type A & B Applications Authorization for Use

  11. 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 A, Appendix A

  12. 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 A, Appendix B Type B Applications

  13. 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

  14. Where We Are in the Presentation • Hardware and Software • Guidance Materials • Authorization Process  

  15. Pertinent EFB Guidance History Guidelines For The Certification, Airworthiness, and Operational Approval of EFB Computing Devices (In revision) FAA AC 120-76A (3/17/03) FAA AC 91-21.1B (08/25/06) FAA Notice 8200.98 (10/13/06) FAA AC 20-159 (04/30/07) FAA AC 91-78 (7/20/07) A061 OpSpecs Guidance (03/14/11) 8900.1 EFB Guidance (03/16/12) Use of Portable Electronic Devices Aboard Aircraft (Used in conjunction with 8900.1 for authorizing use of EFB) Electronic Flight Bag “Job Aid” (Expired) Obtaining Design And Production Approval Of Airport Moving Map Display (AMMD) Applications Intended For Electronic Flight Bag Systems Use of Class 1 or Class 2 Electronic Flight Bag (EFB) Part 91 guidance Clarified AEG and POI role Inspector Handbook

  16. Advisory Circular 20-159 AMM (Airport Moving Map) with own-ship position for Class 2 & 3 EFB Systems

  17. Moving Maps with Own-Ship Position • 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

  18. How AC 20-159 Relates to Current EFB AC • AC 20-159 is consistent with EFB AC 120-76A which states in part: “EFB Type C applications that receive a TSOA may be approved for use on EFB Class 2 systems provided they meet the following conditions: • Hosted applications must be classified as a minor failure effect or no safety effect. No major safety effect or higher classifications are acceptable. • Type A and B EFB software applications may reside in a TSOA system provided they “do not” interfere with the Type C applications.”

  19. 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

  20. 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

  21. 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

  22. 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

  23. 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

  24. 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

  25. EFB Data Connectivity

  26. Where We Are in the Presentation • Hardware and Software • Guidance Materials • Authorization Process   

  27. 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

  28. 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

  29. Phase Two: Application Submission • Required Application Information. 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.

  30. Phase Two: Application Package • EFB hardware and application specifications • EFB operator procedures/manual revisions • EFB cockpit procedures checklists • EFB training program • EFB evaluation report • Rapid decompression test data • Completed non-interference test results • Airworthiness documents for Class 2 equipment

  31. 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

  32. 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-81)

  33. 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

  34. New Electronic Flight Bags… New Questions iPad II and Beyond

  35. QuestionsComments

More Related