Meet James Murray our Product Analyst
Updated 7th September 2026
The task of choosing an Electronic Flight Bag can be complicated for some operators. There are many factors to consider including which classification is best for individual requirements.
This article explains the differences between these classifications in order to simplify the diverse world of EFB solutions and help to highlight precisely what type of Electronic Flight Bag might be the right one for you.
EFB hardware
EFB software applications

Portable
This host platform can be removed from the aircraft and operated both inside and outside of the aircraft.
If mounted, a portable EFB must be easy to remove from its mounting device by the flight crew without the use of tools. This type of hardware may only be used in all phases of flight if it is secured to a mount or securely attached to a viewable stowage device.
Installed
This platform is fixed into the aircraft and considered an aircraft part therefore it cannot be removed from the flight deck.
The software application for Electronic Flight Bags are classified as Type A, Type B or
Applications that fall outside the EFB classification.
Type A EFB applications
Type A applications are EFB functions where a malfunction or misuse has no safety effect, based on EASA's current definition.
Typical examples include electronic storage and retrieval of operational documents and other information that can be accessed by the flight crew.
Type A applications generally have a lower safety impact than Type B applications and are subject to the operator's EFB procedures and regulatory requirements.
Type B EFB applications
Type B applications support operational functions where a malfunction or misuse could have a safety effect limited to a minor failure condition.
Examples can include:
EASA's current guidance specifically lists operational flight plans, meteorological information, NOTAMs/AIS briefing documentation and electronic aeronautical chart applications among typical Type B applications.
Because Type B applications can have an operational safety effect, operators need to complete the appropriate EFB assessment, risk management and regulatory approval processes before using them operationally.
| Classification | What it describes | Typical examples |
|---|---|---|
| Portable EFB | Hardware that can be removed from the aircraft | iPad or other portable device |
| Installed EFB | Hardware/equipment permanently installed in the aircraft | Installed flight-deck equipment |
| Type A | EFB software with no safety effect if it malfunctions | Document viewing and retrieval |
| Type B | EFB software where the potential effect of failure is limited to minor | Charts, OFPs, weather, NOTAMs, briefing applications |
Portable/Installed refers to the hardware, while Type A/Type B refers to the EFB application. They are not alternative levels of the same classification system.
skybook is a Type B EFB solution, supporting operational applications such as digital flight briefing, NOTAM information, electronic charts, journey log functionality and other flight operations workflows.
The EFB is supported by the skybook Ground Portal, allowing flight operations and dispatch teams to manage information and workflows while keeping data synchronised with the flight crew.
Portable EFBs
A portable EFB uses a device that can be removed from the aircraft and operated outside the aircraft.
This can include tablets such as iPads. A portable EFB may be used throughout flight when appropriately secured using a suitable mount or stowage arrangement. EASA specifically states that portable EFBs can host Type A and/or Type B applications.
Installed EFBs
An installed EFB forms part of the aircraft's installed equipment and cannot simply be removed by the flight crew.
Installed systems can provide greater integration with aircraft systems, but typically involve a different certification and aircraft modification environment.
Which is better?
Neither is universally better. The right approach depends on the aircraft, operation, existing avionics, regulatory environment and the EFB functions the operator needs.
EFB classification is only one part of choosing an EFB.
Airlines should also consider the operational workflows they want to digitise, integration with existing systems, regulatory requirements, crew usability, connectivity, administration customisation and how the EFB will be supported across the operation.
For operators looking to move beyond document replacement, an integrated Type B EFB can bring flight briefing, operational information, journey logging and flight crew workflows together in a single platform.
See how skybook can support your flight operations