U.S. DEPARTMENT OF TRANSPORTATION FEDERAL AVIATION ADMINISTRATION National Policy

Transcription

1 U.S. DEPARTMENT OF TRANSPORTATION FEDERAL AVIATION ADMINISTRATION National Policy NOTICE N SUBJ: Revised Guidance for Authorizing the Use of Electronic Flight Bags, Issuance of A061, Electronic Flight Bag, and Revision to A025 Effective Date: 2/15/07 Cancellation Date: 2/15/08 1. PURPOSE. This notice provides revised guidance to principal inspectors (PI) and Aircraft Evaluation Groups (AEG) for authorizing the use of Electronic Flight Bag (EFB) hardware and software for operations conducted under Title 14 of the Code of Federal Regulations (14 CFR) parts 91 subpart K, 121, 125 (including the part 125M operators), and 135. This notice also issues OpSpec/MSpec/letter of authorization (LOA) A061 and revises A DISTRIBUTION. We will distribute this notice to the division level in the Flight Standards Service in Washington headquarters, including the Regulatory Standards Division at the Mike Monroney Aeronautical Center; to the branch level in the regional Flight Standards divisions; and to all Flight Standards District Offices. Inspectors can access this notice through the Flight Standards Information Management System (FSIMS) at Operators may find this information on the Federal Aviation Administration s (FAA) Web site at: 3. BACKGROUND. a. Advisory Circular (AC) A, Guidelines for the Certification, Airworthiness, and Operational Approval of Electronic Flight Bag Computing Devices and Notice N , Electronic Flight Bag Job Aid, reference several instances of FAA inspector and AEG approval requirements for Class 1 and 2 EFB hardware and associated Type A and B software whether sold separately or embedded in an EFB system. This guidance replaces procedures and advisory material in FAA orders and ACs requiring an FAA inspector or the AEG to approve Class 1 and 2 EFB hardware and associated Type A and B software. This guidance is not intended to stop or restrict the operational use of these devices and software. b. With recent enhancements in computer technology and software, some classes of EFB systems have evolved to have functions and configurations beyond inspectors authority. The proliferation of hardware and multiple variants of software, resulted in a significant increase in the number and complexity of EFB systems available to industry. Consequently, current guidance and advisory material has become inadequate to assess applications and performance assurance of many EFB systems. 4. GUIDANCE. PIs and AEGs will no longer approve Class 1 and Class 2 EFB hardware and associated Type A and B software. The PIs will only authorize the use of the Class 1 or Class 2 EFB. Installation requirements and airworthiness approval remain unchanged. Class 3 devices and Type C software will be FAA-approved by the normal Type certification processes (Type certificate (TC)/Supplemental Type Certificate (STC)), and all EFBs will be authorized Distribution: A-W(FS)-2; A-X(FS)-3; A-FFs-7 (LTD); AMA-200 (12 cys) (Electronically: A-W(FS)-2; A-X(FS)-2; A-FFS-7) Initiated By: AFS-260

2 2/15/072 N for use by OpSpec/MSpec/LOA. AEGs may be required to evaluate the EFB system installations using the present advisory guidance and practices, and provide a report of adverse findings to the aircraft certification or airworthiness entity responsible for approving the initial installation. 5. ACTION. PIs will review guidance in Appendix 1 and provide this notice to the affected operators. A sample of the OpSpec/MSpec/LOA A025 nonmandatory revision for operators conducting operations under parts 91 subpart K, 121, 125, 125M, and 135, and a sample of the new OpSpec/MSpec/LOA A061 can be found in Appendix 2 and are available in the automated Operations Safety System (OPSS). a. PIs will provide technical advice and guidance to operators when requested to assist them in evaluating their selected EFB systems using the technical guidance found in AC A and N but will no longer issue FAA approvals for the hardware and software. b. If the operator s OpSpec/MSpec/LOA A025 already contains an authorization for the use of an EFB, the operator s existing OpSpec/MSpec/LOA A025 must be re-issued and the new A061 must be issued to authorize the use of the appropriate EFB within 120 days of the publication of this notice. No subsequent evaluation of previously authorized EFB system(s) is necessary. If the operator has A025 issued without the use of an EFB authorized, it is not necessary to re-issue that operator s A025 at this time. c. PIs will use the new OpSpec/MSpec/LOA paragraph A061, EFB (for part 125M operators, LOA A061) to authorize the use of Class 1, Class 2, or Class 3 EFBs in accordance with the guidance in Appendix 1 of this notice. Compliance with the requirements of OpSpec/MSpec/LOA A061 should be validated prior to the initial authorization to use an EFB and during routine inspections of the operator. 6. DISPOSITION. We will permanently incorporate the information in this notice in FSIMS before this notice expires. Questions regarding this notice should be directed to the Air Transportation Division, AFS-260, at (202) ORIGINAL SIGNED by Roger C. Forshee Jr. for, James J. Ballough Director, Flight Standards Service Page 2 Par 4

3 2/15/07 N Appendix 1 APPENDIX 1. ORDER , VOLUME 3, CHAPTER 1, SECTION 3, OPSPEC/MSPEC/LOA A061, ELECTRONIC FLIGHT BAG A. The authorization to use an Electronic Flight Bag (EFB) is optional and applicable to operators conducting operations under Title 14 of the Code of Federal Regulations (14 CFR) parts 91 subpart K, 121, 125 (including part 125M), and 135. Principal inspectors (PI) will authorize the use of Class 1, 2, and 3 EFBs. For authorizing the use of a Class 1 or Class 2 EFBs, the PI must issue the appropriate selectable statement in operations specification/management specification (OpSpec/Mspec) and letter of authorization (LOA) A061, Electronic Flight Bag. Table 1 of OpSpec/MSpec/LOA A061 will be used to document the aircraft M/M/S, the Class 3 device, and the Type C software revision control for Class 3 EFB systems. OpSpec/MSpec/LOA A025 is no longer used for the EFB authorization. Compliance with the requirements of OpSpec/MSpec/LOA A061 should be validated during routine inspections of the operator before it is issued. B. PIs and Aircraft Evaluation Groups (AEG) are not responsible for approving Class 1 and Class 2 EFB hardware and associated Type A and B software. (1) Installation requirements and airworthiness approval remain unchanged as specified in Advisory Circular (AC) A, Guidelines for the Certification, Airworthiness, and Operational Approval of Electronic Flight Bag Computing Devices and Notice N , Electronic Flight Bag Job Aid for EFB systems and associated software types. (2) The appropriate AEG may be required to evaluate the EFB system installations using the present advisory guidance and practices and provide a report of operational suitability and/or adverse findings to the responsible aircraft certification or airworthiness entity having approval authority for the initial installation. C. Class 1 and Class 2 EFB Devices. The following is applicable for authorizing the use of Classes 1 and 2 EFB devices: (1) Only Class 1 and/or Class 2 devices with Type A and/or B software may be authorized using the technical guidance specified in AC A and N (2) The aircraft must have the proper airworthiness approvals for any power, data, or mounting. (3) Training for the use and/or maintenance of the EFB by certificate holder/program manager must be documented and included in the operator s approved training program. (4) The certificate holder/program manager will specify the procedures for updating and maintaining any databases necessary to perform the intended functions of the EFB in its manual. D. Class 3 EFB Devices. The Aircraft Certification Service (AIR) must provide design, installation, and airworthiness approval for Class 3 EFB hardware which is built in on an aircraft. This will be accomplished by incorporating the Type design or Supplemental Type Certificate (STC), not by field approvals. Page 1

4 N /15/072 Appendix 1 (1) The Type C software associated with Class 3 EFBs is also certified by AIR in accordance with RTCA DO-178, Considerations in Airborne Systems and Equipment Certification. Type A and B software may be installed on these devices but require no approval by the PI as they are protected from the Type C software in the DO-178 standard. (2) Operators should have procedures to control revisions to the Type A and B software in their manuals. Type C software revision control is accomplished by using Table 1 in OpSpec/MSpec/LOA A061. (3) If Type A or Type B software is used in conjunction with Type C software in the Class 3 EFB, the name of the software must be documented in Table 1 of OpSpec/MSpec/LOA A061. E. Validation Flights. Simulator and/or in-flight validation tests may be needed to fully determine the suitability of the use of an EFB (see AC A, paragraph 12(j), pp ). Each operator s proposed EFB functionality and software will vary, and scenarios should be customized for the particular situation by the inspector and applicant. (1) The validation flight scenarios should be used to ensure that EFB use has adequately transitioned into the operator s overall training and operations programs. In some cases, the task will be completed entirely with an EFB, while in other cases, the EFB may be used together with other sources of information such as paper charts or documents, depending on the capabilities of the EFB and its operational implementation. (2) The required EFB validation-flight scenario differences could be affected by other factors, such as: : Type A, B, or C application Hardware: Class 1, 2, or 3, which includes factors such as location in the flight deck, and connectivity to other aircraft systems Aircraft/Operations: Single pilot vs. dual pilot, single EFB vs. dual EFB Type Weather conditions: Visual vs. instrument, or very low visibility Page 2

5 2/15/07 N Appendix 2 APPENDIX 2. SAMPLE OPSPEC/MSPEC/LOA A061, USE OF ELECTRONIC FLIGHT BAG a. The certificate holder/program Manager/operator is authorized to conduct operations using an Electronic Flight Bag (EFB) in accordance with the limitations and provisions of this operations specification. b. Class 3 Devices. The certificate holder/program manager is authorized to use the Class 3 EFB devices with the Type C software revision number and, if applicable, the name of the associated Type A or Type B software as listed in Table 1 below. TABLE 1 AUTHORIZED USE OF CLASS 3 EFB AND APPLICABLE SOFTWARE REVISION M/M/S Class 3 Type C Revision Number Class 3 Type B Name TABL01 TABL03 TABL04 Enter Name or N/A Class 3 Type A Name TABL05 Enter Name or N//A Restrictions and Limitations TABL06 c. The certificate holder/program manager/operator s approved training program must include appropriate training for the flightcrews on the use of any Class 3 EFB device listed in Table 1 above. The following is a selectable statement for authorizing the USE of a Class 1 and/or a Class 2 EFB: d. Class 1 and/or Class 2 EFBs. The certificate holder is authorized to use a Class 1 and/or Class 2 EFB using Type A and/or Type B software only and the following limitations and conditions shall apply: (1) The aircraft must have the proper airworthiness approvals for any power, data, or mounting in the aircraft. (2) The certificate holder/program manager must specify in its manual the procedures for updating and maintaining any databases necessary to perform the intended functions. (3) The certificate holder/program manager is responsible to ensure the EFB and associated software will provide the necessary data, information, functionality and solutions to perform the intended flight functions, and if not, provide substitute information in non-electronic form. (4) The certificate holder/program manager s approved training program must include and document the use of and/or maintenance of the EFB by certificate holder/program manager employees. ********************************************************************************************* SAMPLE OPSPEC/MSPEC/LOA A025. ELECTRONIC RECORDKEEPING SYSTEM The certificate holder/program manager/operator is authorized to use an approved electronic recordkeeping system, described and/or referenced in this paragraph: Enter reference or description here. TEXT99 Page 1 (and 2)