FLIGHT STANDARDIZATION BOARD REPORT
ARINC Messenger (NavAero)
Class 2 Electronic Flight Bag (EFB)
DATE: January 07, 2005
Chairman, B-727 Flight Standardization Board
Seattle Aircraft Evaluation Group
Federal Aviation Administration
Aircraft Evaluation Group (SEAAEG)
1601 Lind Avenue S.W.
, Washington 98055-4056
Telephone: (425) 917-6600
FAX (425) 917-6638
MANAGEMENT COORDINATION SHEET
Assistant Manager, Operations
Seattle Aircraft Evaluation Group
Seattle Aircraft Evaluation Group
Thomas Toula (AFS-200)
Air Transportation Division
1. Purpose and Applicability
This FSB report specifies FAA requirements
applicable to operators seeking operations approval to use the ARINC
Electronic Flight Bag (EFB) Class 2 device, under FAR 121. 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 is/will be accomplished.
2. EFB Description
This installation consists of one ARINC
Messenger NavAero electronic flight bag (EFB) at the Second Officer’s (S/O)
station located directly behind (outboard of) the S/O’s instrument panel
just aft of the area currently utilized for the First Officer’s (F/O) flight
bag. A thermal printer is installed on the aft structural support of
the S/O’s instrument panel, directly to the right of the panel. The
EFB control panel will be secured to the forward edge (left side) of the
S/O’s panel. In addition to the cockpit equipment, an aircraft
communication unit (ACU) ACARS unit will be installed in the E&E bay and a
VHF antenna will be installed externally on the aft belly of the aircraft.
NOTE: As part of the installation,
the F/O’s oxygen mask location and ICS jack-box will be slightly altered.
There are no changes to existing operational procedures.
This EFB has
been manufactured by NavAero.
The model of
this EFB is: t*Bag C2 System.
major components are included with this make/model of EFB
t*Bag CPU Module (EFB)
t*Bag CPU Battery Pack
Control Display Unit
EFB Control Panel
NavAero tPAD 800 Surface Mount
System and Version
This EFB has
been demonstrated and approved to run on the MS Windows XP Professional OS.
following applications have been demonstrated and approved for use on this
specific EFB. Airplane specific information used in these applications is
applicable to B-727-100/200 airplanes.
“Type A” Applications
All typical functions associated with ACARS operations: e.g.
recording/sending OOOI times, sending/receiving routine company messages,
receiving terminal and enroute weather information, entering preflight data,
and position reporting.
“Type B” Applications
“Type C” Applications
3. EFB Mounting System
The mounting system has been Part
25 certified as part of the ARINC Messenger EFB Supplemental Type
Certificate ST3064DE-T installation.
There are no operating limitations associated with this
EFB mounting system.
4. EFB Display Lighting
This EFB has been evaluated in both low-light and full
sunlight conditions. The display is readable under the full range of
lighting conditions without distraction.
The display has been evaluated during approach under
night lighting conditions. There is no distracting reflectivity observed
from the display under these conditions.
Typical Acceptable Operations Manual Procedures for Use of EFB
Normal operating procedures are included in the applicable airplane
Flight Crew Operations Manual and Flight Crew Training Manual. Descriptions
of specific applications may be contained in a “User Guide” supplied by the
If the 28VDC “S/O EFB” or “ARINC MSGR” circuit breakers should open during
flight, the S/O is to leave the circuit breaker open (ARINC Messenger system
will be repaired by ground personnel). Make a logbook entry.
There are no Airworthiness Limitations associated with this installation.
6 Acceptable EFB Data
7 FSB Specifications for
Training and Typical Acceptable Training Course Description
As this installation currently encompasses ACARS type functionality only,
initial training is set at Level B.
Crediting Previous EFB Experience. NA
Initial, Transition and Upgrade Ground Training
Pilots: Initial Training.
training is accomplished as specified by this FSB report or included in an
approved AQP or airplane transition training program. No unique
provisions or requirements are specified.
Areas of Emphasis.
Recurrent training is not normally required for EFB operation
provided the functions are used regularly in line operations.
Operators are encouraged to include EFB as a component of simulator
recurrent training to the extent practical.
As part of an approved training program, an operator may use many
methods when conducting recurrent training, including classroom instruction,
pictures, videotape, ground training devices, computer-based instruction,
and static aircraft training.
Recurrent Training Simulator Requirements (reserved)
8 FSB Specifications for
Items. No specific checking requirements have been identified at
Operators are encouraged to include EFB use as a part of recurrent checking
where practical. Proper EFB use should be included in line checks.
The following areas of emphasis should be addressed during line checks as
Proper cross-check of data entered into the performance application
discretion of the evaluator, and if the EFB is installed in the operator’s
training device or simulator, EFB may be included in the practical testing
and annual proficiency checks.
9 FSB Specifications for
EFB is used regularly
, no unique currency provisions apply to the EFB.
The ARINC Messenger EFB (including the power supply) has been
tested by ground and flight testing in accordance with procedures contained
in ARINC Document No. 23-06-0001-20, Revision: 1R. The ARINC Messenger
EFB has been found not exhibit any unacceptable levels of electromagnetic
Changes of any of the components listed in paragraph
2.3 will require that the EFB is checked again for acceptable levels of EMI.
Rapid Depressurization Testing
The effects of rapid
depressurization have been evaluated for this EFB installation in accordance
Advisory Circular 25-10.
Operating System Change Requirements
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
continues to meet intended function.
The certificate holder or the operator will need to
satisfy the Principal Inspector that they have procedures in place to manage
the hardware and software configuration of any Class 2 EFBs that will be in
Instructions for Continued Airworthiness
The certificate holder or the operator is responsible
to demonstrate that they have procedures in place to track repairs to EFB
units and to ensure each EFB remains in compliance with the approved
Checklist (see Appendix 2).
Compliance checklists 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.
of Specific Compliance Checklist Items (reserved)
FSB Specifications for Devices and Simulators-(Reserved)
Application of FSB Report
Relevant parts of this report are
effective for the specific combination of Class 2 EFB and mounting system
when the report is approved by FAA.
Alternate Means of Compliance
Level and Approval Criteria. 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.
Equivalent Safety. In the event alternate compliance is sought,
training program hour reductions, simulator approvals, and device approvals,
may be significantly limited and reporting requirements may be increased to
assure equivalent safety. 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.
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
Miscellaneous - (Reserved)
List of Required
Documents and Artifacts for Operational Approval and Continued Airworthiness
Flight Crew Operations Manual
Flight Bag Pilot’s Guide
Data Delivery and Management Description
Configuration Control Description and Procedures
These acceptable means of
compliance refer to the applicable sections of
(1) Title 14 CFR §§
(2) Title 14 CFR §§
(3) Title 14 CFR §§
125.383, 125. 403,
(4) Title 14 CFR §§