EFB Manual REV 01 (Downloaded 2023-Feb-15-10 23)

EFB POLICY AND PROCEDURES
MANUAL
Issue 0, Revision 1
EFB POLICY AND PROCEDURES MANUAL
1 Administration and control
1.1 Table of contents
1 Administration and control ....................................................................................................................... 2
1.1 Table of contents ................................................................................................................................................................... 2
1.2 List of revisions ...................................................................................................................................................................... 4
1.3 Glossary of terms and acronyms ........................................................................................................................................... 5
2 ETF EFB system description ....................................................................................................................... 6
2.1 Introduction ........................................................................................................................................................................... 6
2.2 EFB system dataflow .............................................................................................................................................................. 7
2.3 Changes to EFB system .......................................................................................................................................................... 8
3 Limitations of the EFB system .................................................................................................................... 8
3.1 Environment limitations ........................................................................................................................................................ 8
3.2 Compatibility .......................................................................................................................................................................... 8
3.3 Jeppesen FliteDeck Pro limitations ........................................................................................................................................ 8
3.3.1 Jeppesen cycle validity limitation .......................................................................................................................................... 8
3.3.2 AMMD (Airport Moving Map Display) ................................................................................................................................... 8
4 Hardware description, control and configuration ....................................................................................... 8
4.1 iPad devices ........................................................................................................................................................................... 8
4.2 iPad Mount .......................................................................................................................................................................... 10
4.2.1 Mount installed on 9A-ABC and 9A-KOR ............................................................................................................................ 10
4.2.2 Mount installed on 9A-LAB .................................................................................................................................................. 13
5 Operating system.................................................................................................................................... 15
6 EFB TYPE B applications........................................................................................................................... 16
6.1 Jeppesen Flite Deck PRO ...................................................................................................................................................... 16
6.1.1 Overview .............................................................................................................................................................................. 16
6.1.2 Control and configuration .................................................................................................................................................... 16
6.1.3 Data management ............................................................................................................................................................... 16
6.1.4 Electronic signature ............................................................................................................................................................. 16
6.1.5 Sharing flight information between two devices ................................................................................................................. 17
6.1.6 Integration with PPS flight planning system ........................................................................................................................ 17
6.1.7 Weather data ....................................................................................................................................................................... 17
6.2 Jeppesen Aviator.................................................................................................................................................................. 18
6.2.1 Overview .............................................................................................................................................................................. 18
6.2.3 Data management ............................................................................................................................................................... 20
6.3 Boeing OPT........................................................................................................................................................................... 21
6.3.1 Overview .............................................................................................................................................................................. 21
6.3.3 Data management ............................................................................................................................................................... 22
6.3.5 Application failure................................................................................................................................................................ 24
6.4 Crewbriefing ........................................................................................................................................................................ 24
6.4.2 Data Management ............................................................................................................................................................... 25
7 EFB TYPE A applications .......................................................................................................................... 25
7.1 Pan Aero Services ................................................................................................................................................................ 25
7.1.2 Data management ............................................................................................................................................................... 26
7.2 Leon ..................................................................................................................................................................................... 26
7.3 Cisco Meraki System Manager ............................................................................................................................................. 26
7.4 IQSMS Reporting .................................................................................................................................................................. 27
8 EFB Administrator ................................................................................................................................... 27
8.1 Responsibilities .................................................................................................................................................................... 28
8.2 Qualification requirements .................................................................................................................................................. 28
8.3 Training ................................................................................................................................................................................ 28
8.3.1 ETF EFB Administrator ......................................................................................................................................................... 28
19-May-2022 Issue 0, Rev 1 page 2 of 29

9 Flight crew .............................................................................................................................................. 28
9.1 Training ................................................................................................................................................................................ 28
9.1.1 Ground-based training: ........................................................................................................................................................ 28
9.1.2 Flight training: ...................................................................................................................................................................... 29
9.2 Operating procedures .......................................................................................................................................................... 29
10 Maintenance consideration ..................................................................................................................... 29
11 EFB security policy .................................................................................................................................. 29

1.2 List of revisions
Rev. No. Date Chapter
Issue 0, Rev 0 14-Dec-2020 All
Issue 0, Rev 1 19-May-2022 All

1.3 Glossary of terms and acronyms
Term Description
Airport Moving Map Display Software application that displays an airport map on a display device and
uses data from a navigation source to depict the aircraft current position on
this map while the aircraft is on the ground.
type A EFB application EFB application whose malfunction or misuse has no safety
effect
type B EFB application means an EFB application:
a) whose malfunction or misuse is classified as minor failure condition or
below; and
b) which neither replaces nor duplicates any system or functionality
required by airworthiness regulations, airspace requirements, or
operational rules
EFB application software application installed on an EFB host platform that provides one or
more specific operational functions which support flight operations
EFB host platform hardware equipment in which the computing capabilities and basic
software reside, including the operating system and the input/output
software
EFB system hardware equipment (including any battery, connectivity provisions,
input/output components) and software (including databases and the
operating system) needed to support the intended EFB application(s)
electronic flight bag (EFB) electronic information system, comprised of equipment and applications
for flight crew, which allows for the storing, updating, displaying and
processing of EFB functions to support flight operations or duties
human–machine interface (HMI) component of certain devices that is capable of handling human–machine
interactions. The interface consists of hardware and software that allow
user inputs to be interpreted and processed by machines or systems that, in
turn, provide the required results to the user
portable EFB portable EFB host platform, used on the flight deck, which is not part of the
configuration of the certified aircraft
portable electronic device (PED) any kind of electronic device, typically but not limited to consumer
electronics, brought on board the aircraft by crew members, passengers, or
as part of the cargo, that is not included in the configuration of the certified
aircraft. It includes all equipment that is able to consume electrical energy.
The electrical energy can be provided from internal sources such as
batteries (chargeable or non-rechargeable) or the devices may also be
connected to specific aircraft power sources
Controlled portable electronic PED subject to administrative control by the operator that uses it. This
device (C-PED) includes, inter alia, tracking the allocation of the devices to specific aircraft
or persons and ensuring that no unauthorised changes are made to the
hardware, software, or databases. C-PEDs can be assigned to the category
of non-intentional transmitters or T-PEDs.
EFB installed resources certified EFB hardware components external to the EFB host platform itself,
such as input/output components (installed remote displays, keyboards,
pointing devices, switches, etc.) or a docking station
EFB mounting device aircraft certified part that secures a portable or installed EFB, or EFB system
components
EFB system supplier Company responsible for developing, or for having developed, the EFB
system or part of it.
Installed EFB EFB host platform installed in an aircraft, capable of hosting type A and/or
type B EFB applications. It may also host certified applications. It is an
aircraft part, and, is therefore, covered by the aircraft airworthiness
approval

Term Description
Miscellaneous (non-EFB) software non-EFB applications that support function(s) not directly related to the
applications tasks performed by the flight crew in the aircraft
Transmitting PED (T-PED) portable electronic device (PED) that has intentional radio frequency (RF)
transmission capabilities.
iOS or OS ipadOS operating system
2 ETF EFB system description

2.1 Introduction
The purpose of this EFB manual is to provide overview of ETF EFB system and to provide familiarization with
procedures related to EFB system.
ETF EFB system consist of:
1. Hardware
• Various iPad models with ipadOS operating system
• Mounting device with charging capability
2. Software:
• Type B applications
▪ Jeppesen FliteDeck PRO
▪ Jeppesen Aviator
▪ Boeing OPT
▪ Crewbriefing
• Type A applications
▪ OMS from Pan Aero
▪ Cisco Meraki System Manager
▪ Leon software
EFB system is classified as portable.
• A portable EFB can be operated inside and outside the aircraft.

• A portable EFB hosts type A and/or type B EFB software applications. In addition, it may host miscellaneous
(non-EFB) software applications
• iPad is a T-PED. Transmitting function shall be switched off in all phases of flight.
• The power supply for a portable EFB is provided from aircraft source
• Portable EFBs may be used in all phases of the flight if securely attached to a viewable stowage device in a
manner which allows its normal use
• Portable EFBs are controlled PEDs
• A portable EFB device does not require an airworthiness approval.
• EFB devices are monitored via Mobile Device Management
• One iPad device is assigned to each pilot.
• There is one backup iPad device on each aircraft.
• iPad devices are connected to internet by using cellular connection. The amount of data used by each device
is continuously monitored.

2.2 EFB system dataflow
Type of data Description

OFP OFP (Operational flight plan) is prepared by OCC and is uploaded to PPS server (also called
Crewbriefing). From PPS server, OFP is transmitted to Jeppesen server in ARINC 633 format
from where crew can download it to Aviator application.
In addition, OFP can be also downloaded from Crewbriefing application which is installed on
iPad devices.
OFP loaded to Aviator application can be electronically filled with actual figures as flight
progresses. After flight, completed OFP is transmitted to Jeppesen / Boeing server from where
it is transmitted to ETF Airways server for archiving.
OFP loaded to Crewbriefing application is in view only format and is used as backup.
AODB AODB (Aerodrome obstacle database) needs to be downloaded from Aerodata server and then
uploaded to Jeppesen / Boeing server. This is done by EFB Administrator
SCAP SCAP (Standardised Computerised Aircraft Performance) are set of performance data for
combination of aircraft airframe and engines.
Data are loaded to Jeppesen/Boeing server and then in form of OPT update package are
transmitted to OPT application together with AODB data.
Mass and Settings required for mass and balance calculations with OPT application.
balance settings
Navigation Navigation charts in FD Pro are downloaded from Jeppesen server directly. EFB Administrator
charts maintains list of airports that are included in the subscription package.
Documentation Documentation is referred to manuals, documents or forms distributed by EFB Administrator.
Schedule data Before flight, planned schedule which contain planned flight data is loaded from Leon software
into OMS application. This process is done automatically.

Type of data Description
Actual flight After completion of flight, OMS application will send actual journey log data to OMS server
data from where data will be loaded into Leon system. This process is done automatically.
Note: for data transfer from / to iPad device, active internet connection needs to be established.
2.3 Changes to EFB system

The only authorized person authorized to make hardware or software changes to EFB system is EFB Administrator or
another person appointed by EFB Administrator.
Modifications to an EFB system may have to be introduced either by the EFB system supplier, the EFB applications
developer or by ETF AIRWAYS.
The following modifications are allowed without obtaining prior approval from CCAA:
• Modifications that do not result in a hardware change that would require a re-evaluation of the HMI and
human factors aspects.
• Modifications that do not bring any change to the calculation algorithms of a type B EFB application
• Modifications that do not bring any change to the HMI of a type B EFB application that requires a change to
the flight crew training programme or operational procedures.
• Introduction of a new type A EFB application or modification of an existing one (provided its software
classification remains type A)
• Modifications that do not introduce any additional functionality to an existing type B EFB application; or
• Update of an existing database necessary to use of an existing type B EFB application
For all other types of modification, change management procedure shall be applied and CCAA approval shall be
obtained.
3 Limitations of the EFB system

3.1 Environment limitations
• EFB operating ambient temperature: 0° C to 35° C
• Non-operating temperature: -20° C to 45° C
• Relative humidity: 5% to 95% noncondensing
• Operational after rapid decompression (tested at 51000 ft)
3.2 Compatibility
Compatibility is ensured through MERAKI system manager which tracks application version and iOS version on each
device.
3.3 Jeppesen FliteDeck Pro limitations

3.3.1 Jeppesen cycle validity limitation
Jeppesen FD application is able to present needed aeronautical data if aeronautical data (cycles) are up to date.
Paper charts must be used if data is not current.
3.3.2 AMMD (Airport Moving Map Display)

AMM feature is not allowed to use in ETF.
4 Hardware description, control and configuration

4.1 iPad devices
All EFB devices are various Apple iPad models. Pre-flight checks ensure that battery level available will be sufficient
to safely perform the flight.

Illustration below shows basic overview of iPad device controls. For detailed description of each device refer to user
manual which is available on the device.
Before first use, EFB Administrator will configure device, install all applications and enrol device into Cisco Meraki
device management system.
Each crew member is responsible to login into each application with provided login credentials, keep application
data up to date and to comply with compatibility instructions.
All EFB devices are enrolled into Cisco Meraki device management system which is used for remote monitoring. This
system tracks device hardware and software information as well as recent location.

4.2 iPad Mount
4.2.1 Mount installed on 9A-ABC and 9A-KOR
Two mounting devices, each to hold an iPad®, are installed on the flight deck. When the iPad® is in use, the
mounting device can be positioned in different ways to accommodate the flight crew preferences.
For each mounting device an USB Power Outlet provides DC power for charging/powering the iPad®.
4.2.1.1 Main components
1. iPad® Holder can fit 9.7-inch iPad - 10.5-inch iPad®

2. Locking Lever- Locks or unlocks the iPad® by moving the lever to an end stop.
3. Adjustment Knob - Secures the Double Socket Arm position
4. Double Socket Arm - Connection of the iPad® Holder with the Base on the aircraft structure.
5. Ball-shaped Part - Ball-shaped part of the iPad® Holder for connection to the Double Socket Arm.
6. Base - Holds the Double Socket Arm together with the iPad® Holder and is attached on the aircraft structure.
7. USB Power Outlet -

4.2.1.2 iPad setup instructions:
Place the iPad® on the iPad® holder and secure the iPad® in place with the locking lever.
For a preferred position of the iPad® (e.g. portrait or landscape and viewing angle) adjustments can be made by
turning the knob on the double socket arm counter clockwise. The friction between the base and the iPad® holder is
then reduced and adjustments can be made. Double socket arm rotation may be necessary to optimize the
adjustment.
When the iPad® is in the preferred position the knob on the double socket arm must be turned clockwise to tighten
the connection between the base and the iPad® holder.
NOTE: Do not use excessive force. The rotation of the double socket arm has an effect on the freedom of movement.
With the knob at side position, the full up and down movement can be achieved. With the knob facing up or
down, the full side movement is achieved. In intermediate knob position, the full movement is diagonal.
NOTE: In the abuse case of high acceleration in combination with too low friction, the iPad® may get into an
abnormal position. This was evaluated during certification; in those cases, any interference is such that it can
be overcome by the pilot.
After installation of the iPad®, make sure that charging cable (if installed) has sufficient slack to allow the sliding
window to be opened and ensure that the USB cable cannot be trapped in the sliding window rail or mechanism. Use
cable clamps or straps when installed.
During daily operation the iPad® shall be used in a suitable position where the iPad® does not interfere with aircraft
systems and controls. The full and free movement of flight controls must be checked by the pilots in the before take-
off check. Any obstruction caused by the iPad® shall be detected at that point and rectified before take-off.
4.2.1.3 Operation
The iPad® mounting device allows for the installation of an iPad® to be used as EFB and can be adjusted in any
direction as required by the flight crew by following the iPad® setup instructions of this FCOM supplement. The
iPad® is charged using the installed USB Power Outlet. Power to the USB Power Outlet is provided by a DC to DC
converter. A total of two converters are installed, one converter for each side (one behind the LH stowage box and
one behind the RH stowage box). The LH converter is fed by DC Bus 1 while the RH converter is fed by DC Bus 2.
4.2.1.4 Protection
It is recommended to remove the iPad® from the iPad® holder when the aircraft will be parked or not be used and
temperature in the cockpit can rise above 35 degrees Celsius (95 degrees Fahrenheit).
The EFB power supply via the USB Power Outlet is protected against short circuit situations and over temperature
situations (due to a damaged USB cable). When a short circuit or over temperature is sensed, the power will be
automatically interrupted as long as the short circuit or over temperature situation exists. Interruption of the power
supply can be noticed on the iPad® display via de battery indication (RH top corner) or when the iPad® has become
empty while connected to the USB Power Outlet. In these cases, it is recommended to replace the USB cable.
In case of smoke, the iPad® shall be disconnected from the aircraft systems by disconnecting the charging cable from
the USB Power Outlet. Also the circuit breakers EFB PWR CONV LH and EFB PWR CONV RH can be pulled or the USB
Power switch (Optional for EASA, mandatory for FAA) can be switched to OFF to remove the power supply to the
converter, thus making the EFB system powerless.
CAUTION:
To avoid damaging the iPad® charging cable do not make sharp bents or kinks in the cable and do not disconnect the
cable by pulling the wire. A damaged cable may cause a serious overheat of the cable and connector. Therefore,
replace a damaged cable immediately.

Location of the circuit breakers:
When the aircraft is left unattended with external power connected, the USB cable must be unplugged from the USB
Power Outlet.
It is recommended to disconnect the power supply by turning the EFB converter switch to OFF before leaving the
aircraft.
4.2.1.5 Evacuation
The iPad® does not obstruct the pilot and co-pilot escape path.

4.2.2 Mount installed on 9A-LAB
4.2.2.1 Description
FlitePad mount fitted for each EFB are located at each of the Captain and First Officer stations. These are installed on
the side window panel on the window cover in the respective sliding side windows, within 90º line of sight of the
respective member of the flight crew.
4.2.2.2 Specifications
Tray dimensions: 275 mm x 174 mm x 13 mm
Power: Input – 28V DC (min 8 V – max 36 V) aircraft supply
Output – 5V DC charging up to 15 W
4.2.2.3 Limitations
• When one or more of the EFBs are not installed, their respective switches installed in the tray shall be set to OFF.
In case the whole mounting assy is removed then the respective circuit breakers pulled and tagged with the
wording “INOP”
• The system Circuit Breakers shall not be used as switches. Use the ON/OFF switches, should it become necessary
to remove power from the EFB mounting provision equipment.
4.2.2.4 Main components
1 – Turn buckle latch
2 – ON / OFF switch
3 – soft flocking to prevent ipad scratching
4 – LED power indicator
5 – power cable

Location of the circuit breakers

5 Operating system
The operating system of all devices is iOS. The iOS user interface is based upon direct manipulation, using multi-
touch gestures. Interface control elements consist of sliders, switches, and buttons. Interaction with the OS includes
gestures such as swipe, tap, pinch, and reverse pinch.
For detailed description of current OS refer to user manual which is available on the device.
All EFB devices have the same OS configuration which is password protected through the operating system.
DO NOT UPDATE iOS SYSTEM before receiving instructions from EFB Administrator.
Because of possible compatibility issues, update of iOS as well as update of installed EFB applications shall be done
only after compatibility is confirmed by EFB Administrator.

6 EFB TYPE B applications
If an EFB system application generates information similar to that generated by existing certified systems,
information generated from type B application prevails.
6.1 Jeppesen Flite Deck PRO

6.1.1 Overview
Application provider: Jeppesen
55 Inverness Drive East
Englewood, Colorado 80112-5498
Website: Link
Technical support: Phone:+49-6102-507004
Email: navsupport@jeppesen.com
User guide: Available in Dropbox application
Training material CBT is available in training department
Application icon:
Application type Type B application

Description: Jeppesen FliteDeck Pro is a mobile electronic flight bag (EFB)
application designed for commercial pilots.
FliteDeck Pro provides pilots with immediate, direct, and
reliable access to enroute chart data, terminal charts, and
Jeppesen Airway Manual text.
6.1.2 Control and configuration

Configuration of Flight Deck Pro settings is done by EFB Administrator by using ground tool.
The following settings are configured within administration settings:
- Update grace period - after content update becomes available, grace period of 23 hours is allowed until data
expired warning will appear. This is shown on update bar.
- Airport Moving Map is disabled
6.1.3 Data management

FliteDeck Pro X requires a reliable internet connection to:
- Download the app and any subsequent data updates

- Retrieve flight plan routes from a flight planning system
- Retrieve recently cleared ATC routes
- Display OTS (Organized Track Systems) data
- Retrieve state NOTAMs
- Display internet Weather layers overlaid on the enroute mpa
- Display METAR, TAF, and D-ATIS (digital ATIS) information
6.1.4 Electronic signature

Jeppesen Flite Deck Pro doesn’t use electronic signature.

6.1.5 Sharing flight information between two devices
To share flight information between two devices actively running FliteDeck Pro X, both devices needs to be on the
same Bluetooth or Wi-Fi network. Internet connection is not needed for sharing flight information between two
devices.
6.1.6 Integration with PPS flight planning system

Flight Deck Pro is integrated with PPS flight planning system and the following information are imported from PPS:
call sign, routing and origin ETD. Only flight plans with origin ETD no further than six hours can be imported into
Flight Deck Pro.
Flight briefing information are additionally shared with Aviator application.
6.1.7 Weather data

Weather data enables flight crew to access meteorological information. It is designed to increase situational
awareness and to support the flight crew when making strategic decisions.
The use of weather data available in FD Pro should be non-safety-critical and not necessary for the performance of
the flight. In order for it to be non-safety-critical, weather data from FD Pro should not be used to support tactical
decisions and/or as a substitute for certified aircraft systems (e.g. weather radar).
Weather data are updated as per below table provided EFB device is connected to internet connection:
Weather layer Update frequency
Radar - Displays base reflectivity that depicts New weather update is available every 10 minutes
precipitation intensity, and provides the ability to and FliteDeck Pro automatically checks for update
see different precipitation types. (Rain, Mixed, every two minutes.
Snow).
Icing - Displays icing potential forecasts. Icing New weather model output is updated every six
potential combines icing probability with severity hours for forecasts from six hours to 36 hours at six-
using the following categories: Low, Moderate, hour time steps.
High. Icing forecasts are provided for the following
flight levels: FliteDeck Pro automatically checks for updates
every two minutes.
010, 020, 030, 050, 060, 080, 100, 120, 140, 160,
180, 210 and 240.
Turbulence – Displays turbulence intensity New weather model output is updated every six
forecasts using the following categories: Light, Light hours for forecasts from six hours to 36 hours at six-
to Moderate, Moderate, and Moderate to Severe. hour time steps.
Turbulence forecasts are provided for the following FliteDeck Pro automatically checks for updates
flight levels: every two minutes
110, 130, 150, 180, 210, 240, 270, 300, 340, 390 and
430.

Weather layer Update frequency
Winds & Temps Aloft - Displays forecast winds and New weather model output is updated every six
temperatures aloft for the following flight levels: hours, for forecasts from six hours to 36 hours at six-
hour time steps.
030, 060, 090, 120, 150, 180, 210, 240, 270, 300,
330, 360, 390, 420, 450, 480, 480, 510 and 540. FliteDeck Pro automatically checks every 10
minutes.
Wind barbs are colorcoded based on wind speed
using the following increments: 10 knots, 25 knots,
50 knots, 75 knots, 100 and knots, 150 knots.
Surface Conditions -- Displays graphical METAR Updated as METAR reports are updated.
conditions from airport observations and color
codes the airport flight conditions using the FliteDeck Pro automatically checks for update every
following scheme: five minutes.
Green - VFR; Amber - IFR; Red - LIFR.
Cloud cover is also depicted based on the sky

conditions reported in the METAR (OVC, BKN, SCT,
FEW CLR)
Lightning – Displays cloud to ground and within New weather is updated every 5 minutes showing
cloud lightning strikes. the past 15 minutes of lightning strikes.
FliteDeck Pro automatically checks for update every

five minutes.
For detailed instructions on how to update weather data manually, refer to FliteDeck Pro User Guide.
To limit amount of data downloads, Flight Deck PRO is set to download weather data along the route only.
6.2 Jeppesen Aviator

6.2.1 Overview
Application provider: Boeing / Jeppesen
Website: https://support.jeppesen.com/product?pc=In_Flight&pid=Aviator_iOS
Technical support: EFB Administrator
User guide: Available via product website
Application icon:
Jeppesen Aviator digitizes the flight-briefing process. The app also provides a single point of access for other integrated
EFB apps such as FliteDeck Pro and Onboard Performance Tool (OPT).

With Aviator on your iPad, you can download flight packages from your flight-planning system. You can review the
planned values for your flight, and then enter actual values as the flight progresses.
When connected to the internet, the app sends your signatures for your preflight tasks to the flight-planning system.
When you close the flight, Aviator gathers the actual data that you entered and compiles that data into a closeout
report.
Aviator consists of these modules:

Briefing View and update the flight summary, time summary, fuel and weights, journey log, crew list, and
performance data. You can review dispatched weather, NOTAMs, NOTOCs, loadsheets, and other important files or
charts provided by the dispatcher. You can also view current live text weather and weather charts. From this
module, you sign your operational flight plan, NOTOC, loadsheet, and journey log.
NavLog View planned waypoints and waypoint metadata. From this module, you enter actual values as your flight
progresses. You can also view an interactive map that shows live weather updates for your planned route.
Documents Download, review, and annotate documents. You can also bookmark sections of documents for easy
reference.

General features:
Sign in Sign in is required to access flight plans within Aviator application. To sign in to
FliteBrief, tap the Settings button / Sign In and enter your credentials.
Moving between Aviator and The Aviator global navigation button enables you to quickly move between Aviator
other integrated applications and the EFB apps that integrate with Aviator (OPT and FD Pro). The button appears
at the left side of the header bar.
Adjusting weather settings Weather information is provided as a reference on the Aviator Dashboard. You can
set your preferred temperature scale and set the default weather format from
Aviator settings.
To change the default temperature scale, tap the Temperature box and select
Fahrenheit or Celsius.
To change the default format for weather data, tap the Default Weather Format
box, and then tap Raw or Decoded.
To show the terrain legend when you view terrain on the interactive weather map,
switch Terrain Legend to ON.
To change the default format for surface conditions, tap the Surface Conditions
arrow, and then select either Raw of Decoded.
Sending log files If you encounter issues with the performance of Aviator, EFB Administrator or
Jeppesen support representative might ask you to send log files. These files help
the representative resolve any issues.
Make sure that your email account is set up on your device and that you are
connected to the internet.
1. To send log files, tap the Settings button on the Aviator toolbar.
2. In the Account Information section, tap Logging.
The app shows the log file options.
3. To change the logging level, tap Logging Level, and then tap the level that you
want to send.
4. Tap Send on the Send Log Files line. The app creates an email message in your
default email program and attaches the log files. Your company configures the
email address so that the address is automatically entered when the app creates
the email message.
5. In the email message, confirm the address to which the message is being sent
and tap Send.

The following data is available within Aviator application:
- Operational flight plan: OFP is prepared in PPS flight planning system and is uploaded to Aviator application
from Jeppesen Flight Brief ground tool. To access OFP data, pilots needs to login with their login credentials.
- Documentation: ETF documents are uploaded by EFB administrator by using JDM ground tool. Application is
automatically updated when new content is available.

Each pilot is given unique username and password which are used for authentication of operational flight plan.
Once all values are completed, commander shall sign OFP by taping “Sign” option next to FLT PLAN in the Briefing
menu.

Before signing flight plan, Commander needs to acknowledge statements shown on the screen and insert
handwritten signature in the appropriate field.
6.3 Boeing OPT

6.3.1 Overview
Application provider: Boeing
Website: https://www.boeingservices.com/flight-
operations/navigation-solutions/onboard-performance-tool
Technical support: Boeing
User guide: OM-B-4 and OM-B-6
Application icon:

Description: OPT application is used for take-off and landing calculations as
well as for determination of aircraft mass and center of gravity.

Default settings in OPT application are set through Onboard Performance Tool Administrator which is ground tool
provided by Boeing.
Default settings include unit preferences, definition of user groups, email settings, landing and take-off SCAP
configuration, wind limitations for take-off and landing, lineup allowance, weight and balance settings, policy and
baseline values for take-off and landing calculations, airport and AODB database, DDG management.
Settings are set within My Boeing Fleet - EFB Administration section and are set by EFB Administrator.

Before releasing new software version, OPT application needs to be checked and tested in terms of human–machine
interface (HMI), reliability and accuracy.
Responsible for testing is Flight Operations Manager and testing needs to be documented.

The following data are imported by EFB administrator:
- Fleet information
- Aerodrome obstacle database which is issued by Aerodata.
- Mass and balance settings
Before departure, performance and mass and balance calculation results shall be sent by e-mail to OCC.

OPT version and data validity can be checked in application settings
When update is available, red icon is displayed on top of screen. Number within red icon shows number of available
updates.

The following output options require crew to authenticate the output report using the Crew Signature:
• Send to Text File

• Send via Email
• Send to Printer
• Print Load Sheet
The following screen shows up and crew member needs to select name from the list and type password which is
unique for each pilot.

If the crew member does not remember their password, they can enter their name and “1234567” instead of crew
ID. In that case, password field will be disabled, and the report will be generated by selecting OK button.
The report will show: “Signed by ___ (NOT AUTHENTICATED) 1234567 at hh:mm on YYYY-DD-MM”
6.3.5 Application failure

In case for some reason calculations cannot be performed by OPT application, crew shall contact OCC dispatcher on
duty who will perform single case calculation on the OCC device. Calculation results needs to be send to crew
members e-mail address and stored within OCC OneDrive folder.
6.4 Crewbriefing
Application provider: AIR SUPPORT A/S
Nimbusvej 9, DK-7190 Billund, Denmark
Website: https://www.ppsflightplanning.com/
Technical support: Email: support@airsupport.dk
Tel: +45 7060 5530.
User guide: Available in application
Training material: Refer to user guide
Application icon:

Description Crewbriefing is selfbriefing application which is available via
web browser or as iOS / Android application.
Application contain pilot briefing package for dispatched
flight. List of documents contained in briefing package
include:
• Route map
• Flight summary
• Flight messages
• Operational flight plan
• Weather information
• NOTAMs
• ATC flight plan
• Wind and SWC charts
• Cross section wx chart
• Additional documents uploaded by OCC if applicable.
For more detailed description of CrewBriefing application, refer to user guide which is available in Dropbox
application.

Login credentials distributed by OCC department are required for login to application.
AirSupport configuration is not password protected. Every user is trained to adapt the application according to
personal preferences.
The following filter settings can be modified by application users:
- Tail filter – filters briefing packages per selected tail numbers

- Crew filter - filters briefing packages per selected crew members
- Dep / Dest - filters briefing packages per departure or destination
- Flight Num - filters briefing packages per particular flight number
- STD - filters briefing packages per departure time
Briefing packages can be sorted by Flight number, Departure – Destination and STD/CTOT value.
6.4.2 Data Management

Data available in Crewbriefing application are generated from PPS flight planning system by OCC staff. Briefing
package needs to be manually uploaded to AirSupport server from where data needs to be manually downloaded to
Crewbriefing application (requires internet connection).
Data are automatically downloaded to application when iPad device is connected to internet. If necessary, crew can
crosscheck validity of flight plan data with paper version of OFP or by calling OCC.
7 EFB TYPE A applications

7.1 Pan Aero Services
Application provider: Pan Aero Services
Kolodvorska 17
HR-42230 Ludbreg, Croatia, EU
Website: https://pan.aero/#!/oms
Technical support: info@pan.aero
User guide: Refer to Technical Log procedures
Application icon:

Description: Pan Aero application is used for completion of combined
Journey and technical log as well as for reporting as described
in OM-A-11.

For Electronic Flight Log, refer to Technical Log Procedures Manual.
For reporting procedures refer to OM-A-11.

iPad Application is integrated with OMS server which is additionally integrated with Leon system. Before flight, flight
schedule is imported into Pan Aero eTLB and after flight Journey log details are exported from EFB application to
OMS server and then into Leon system.
Data transfer is initiated with signing of Electronic Flight Log and crew receives confirmation that data from iPad
were successfully transmitted to server.
7.2 Leon
Application provider: Leon Software sp. z o.o. sp.k.
Al. Jerozolimskie 151/5U
02-326 Warsaw, POLAND
Website: https://www.leonsoftware.com/
Technical support: E-mail: support@leonsoftware.com
Tel: +48 22 390 54 64
User guide: Available online
Training material Leon Youtube channel
Application icon:
Application type Type A application

Description Leon is an application designed for crew members which offers
mobile access to crew roster, aircraft schedule, flight information,
passengers details etc. It consist of central database accessible
through internet in relation to users privileges.

Leon configuration is not password protected. Every user is trained to adapt the application according to personal
preferences.
The following filter settings can be modified by application users:
• Aircraft filter – filters flight and schedule information per tail number. In order to see whole schedule in the
application, make sure that all fleet is selected in filter.
• Activity filter – offers possibility to additionally filter information per flight duties, maintenance tasks, office
duties, own activities etc.
Application also offers possibility to show schedule information in UTC or local time and to display airport codes in
IATA or ICAO format.
7.3 Cisco Meraki System Manager

Application provider: Meraki, LLC
500 Terry François Blvd
San Francisco, CA 94158
Website: https://meraki.cisco.com/
Technical support: Email: support@meraki.com
Phone: +44 203 808 7003
User guide: Not required
CBT Not required
Application icon:

Description Cisco Meraki Systems Manager provides over-the-air centralized
management, diagnostics, and monitoring for the mobile devices
managed by your organization — from iPads and Androids to
Macs and PCs. Systems Manager monitors each of your
organization’s devices, showing useful metrics such as client
hardware/software information and recent location, and even
lets administrators remotely lock and erase devices.
Application is used to enforce policies across mobile devices
administered by ETF. Protect devices and their data, control their
usage with fine-grained passcode policies, and restrict access to
the app store, gaming, and content.
Application is used by EFB administrator only.
This application is not used by crew members but needs to be installed for tracking and administration purposes.
7.4 IQSMS Reporting

Application provider: ASQS GmbH
Website: https://www.asqs.net/
User guide: For reporting procedures refer to OM-A-11
Application icon:

Description The IQSMS Reporting App provides a way to file reports from
anywhere at any given time on your iPad a/o iPhone.
The IQSMS Reporting App enables you to file reports also in times
of no active internet connection. All data entered while offline will
be automatically uploaded to the online system as soon as Internet
connection is re-established.
8 EFB Administrator
The EFB administrator is the person in overall charge of the EFB system and is responsible for ensuring that any
hardware conforms to the required specification, and that no unauthorised software is installed. He is also
responsible for ensuring that only the current versions of the application software and data packages are installed on
the EFB system.

8.1 Responsibilities
The EFB administrator is responsible:
• For all the EFB applications installed, and for providing support to the EFB users regarding these applications
• For checking potential security issues associated with the applications installed
• For hardware and software configuration management of the EFBs, and, in particular, for ensuring that no
unauthorised software is installed.
• The EFB administrator should ensure that miscellaneous software applications do not adversely impact on
the operation of the EFB and should include miscellaneous software applications in the scope of the
configuration management of the EFB.
• For ensuring that only valid versions of the application software and current data packages are installed on
the EFB system.
• For ensuring the integrity of the data packages used by the applications installed.
The EFB administrator is also responsible for the procedures and systems documented in the EFB policy and
procedures manual that maintain EFB security and integrity. This includes system security, content security, access
security, and protection against malicious software.
8.2 Qualification requirements

EFB Administrator should have the following competences:
− Knowledge about iPad devices and iOS operating system

− Knowledge about installed applications as well as knowledge about ground tools used for applications
administration.
− Knowledge about applicable EFB regulations in Commercial Air Transportation
− Knowledge about ETF documentation system
8.3 Training
The EFB Administrator must be trained about applications and administration of installed EFB applications.
The training can be:
- Self-training by using materials provided by software supplier.

- Conducted by software suppliers.
8.3.1 ETF EFB Administrator

EFB Administrator in ETF Airways is Drazen Gros
9 Flight crew
9.1 Training
The following training is applicable for flight crews:
9.1.1 Ground-based training:

System architecture overview;
• Display unit features and use;

• Limitations of the system;
• Restrictions on the use of the system:
o phases of the flight;
o alternate procedures (e.g. MEL);
• Applications as installed;
• Use of each application;
• Restrictions on the use of each application:
o phases of the flight;

o alternate procedures (e.g. MEL);
• Data input;
• Cross-checking of data inputs and outputs;
• Use of data outputs;
• Alternate procedures (e.g. MEL);
9.1.2 Flight training:

• Practical use of the display unit;
• Display unit controls;
• Data input devices;
• Selection of applications;
• Practical use of applications;
• Human factors considerations, including CRM;
• Situational awareness;
• Avoidance of fixation;
• Cross-checking of data inputs and outputs;
• Practical integration of EFB procedures into SOPs;
• Actions following the failure of component(s) of the EFB, including cases of battery smoke or fire;
• Management of conflicting information
9.2 Operating procedures

Refer to OM-B
10 Maintenance consideration
Any EFB device or application dysfunctionality shall be reported through ETF reporting system and to EFB
Administrator who will perform necessary actions.
Replacement of supporting miscellaneous items related to EFB functioning (eg. cables, chargers, protective cases)
shall be reported to ETF OCC or EFB Administrator.
11 EFB security policy

Access to EFB devices shall only be allowed to authorized persons (ETF crew members, and other persons appointed
by the EFB administrator). Each crew member is responsible to restrict access of unauthorized persons to device
assigned to him.
EFB password prevents unauthorized use of the EFB SYSTEM. Each device is protected by password which is known
to device user.
OS restrictions are configured and managed by EFB administrator through Cisco Meraki device management system.
List of restrictions is available in Meraki system.

EFB Manual REV 01 (Downloaded 2023-Feb-15-10 23)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

EFB Manual REV 01 (Downloaded 2023-Feb-15-10 23)

Uploaded by

Copyright:

Available Formats

EFB POLICY AND PROCEDURES

19-May-2022 Issue 0, Rev 1 page 2 of 29

19-May-2022 Issue 0, Rev 1 page 3 of 29

19-May-2022 Issue 0, Rev 1 page 4 of 29

19-May-2022 Issue 0, Rev 1 page 5 of 29

2 ETF EFB system description

ETF EFB system consist of:

EFB system is classified as portable.

• A portable EFB can be operated inside and outside the aircraft.

19-May-2022 Issue 0, Rev 1 page 6 of 29

Type of data Description

19-May-2022 Issue 0, Rev 1 page 7 of 29

2.3 Changes to EFB system

3 Limitations of the EFB system

3.3 Jeppesen FliteDeck Pro limitations

3.3.2 AMMD (Airport Moving Map Display)

4 Hardware description, control and configuration

19-May-2022 Issue 0, Rev 1 page 8 of 29

19-May-2022 Issue 0, Rev 1 page 9 of 29

4.2.1.1 Main components

1. iPad® Holder can fit 9.7-inch iPad - 10.5-inch iPad®

19-May-2022 Issue 0, Rev 1 page 10 of 29

19-May-2022 Issue 0, Rev 1 page 11 of 29

Location of the circuit breakers:

19-May-2022 Issue 0, Rev 1 page 12 of 29

Power: Input – 28V DC (min 8 V – max 36 V) aircraft supply

4.2.2.4 Main components

1 – Turn buckle latch

3 – soft flocking to prevent ipad scratching

4 – LED power indicator

19-May-2022 Issue 0, Rev 1 page 13 of 29

Location of the circuit breakers

19-May-2022 Issue 0, Rev 1 page 14 of 29

19-May-2022 Issue 0, Rev 1 page 15 of 29

6.1 Jeppesen Flite Deck PRO

Application type Type B application

6.1.2 Control and configuration

The following settings are configured within administration settings:

- Airport Moving Map is disabled

6.1.3 Data management

- Download the app and any subsequent data updates

6.1.4 Electronic signature

19-May-2022 Issue 0, Rev 1 page 16 of 29

6.1.6 Integration with PPS flight planning system

Flight briefing information are additionally shared with Aviator application.

6.1.7 Weather data

Weather layer Update frequency

19-May-2022 Issue 0, Rev 1 page 17 of 29

Weather layer Update frequency

Green - VFR; Amber - IFR; Red - LIFR.

Cloud cover is also depicted based on the sky

FliteDeck Pro automatically checks for update every

6.2 Jeppesen Aviator

Application type Type B application

19-May-2022 Issue 0, Rev 1 page 18 of 29

Aviator consists of these modules:

6.2.2 Control and configuration

6.2.3 Data management

6.2.4 Electronic signature

19-May-2022 Issue 0, Rev 1 page 20 of 29

6.3 Boeing OPT

Application type Type B application

6.3.2 Control and configuration