Annex B: Description and Examples of "Type B" Software Applications

1. Type B Software Applications:
   1. do not substitute for, or replace, any system functionality required by airspace requirements, technical airworthiness or operational regulations;
   2. may substitute for, or replace, paper products;
   3. do not require compliance with RTCA DO-178 – Software Considerations in Airborne Systems and Equipment Certification;
   4. may include dynamic, interactive applications that can manipulate data and the presentation of that data;
   5. may display own-ship position for situational awareness purposes;
   6. are to be evaluated in accordance with the guidance provided in Annex C of this advisory, Section 3 – Software Application Evaluation; and
   7. require an OAC
2. Below is a non-exhaustive list of examples of Type B EFB applications:
   1. Approved Flight Manuals (AFM), Supplements, Temporary Revisions;
   2. Aircraft Operating Instructions (AOI), Flight Crew Operating Manuals (FCOM);
   3. Standard Manoeuvre Manuals (SMM), Standard Operating Procedures (SOP);
   4. Aircraft performance data (fixed, non-interactive material for planning purposes);
   5. Airport performance restrictions manual (such as a reference for take-off and landing performance calculations);
   6. Other aircraft performance data, including specialized performance data for use in conjunction with advanced wake vortex modeling techniques, LAHSO predictions, etc. (fixed, non-interactive material for planning purposes);
   7. Aircraft performance calculation application that uses algorithmic data or calculates using software algorithms to provide:
      1. take-off, enroute, approach and landing, missed approach, etc. performance calculations providing limiting masses, distances, times and/or speeds (e.g., runway limiting performance calculations);
      2. power settings, including reduced take-off thrust settings;
      3. mass and balance calculation application used to establish the mass and centre of gravity of the aircraft, and to determine that the load and its distribution is such that the mass and balance limits of the aircraft are not exceeded;
   8. (Master) Minimum Equipment Lists ((M)MEL);
   9. Master flight plan/updating;
   10. Interactive Plotting for Class II navigation;
   11. Weight and balance calculations;
   12. Non-interactive electronic approach charts in a pre-composed format from accepted sources;
   13. Panning, zooming, scrolling and rotation for approach charts;
   14. Pre-composed or dynamic interactive electronic aeronautical charts (e.g., en route, area, approach, and airport surface maps) including, but not limited to, centering and page turning; and own-ship position for situational awareness purposes;
   15. Interactive electronic checklists, including normal, abnormal, and emergency (see the current version of FAA AC 120-64 – Operational Use and Modification of Electronic Checklists – for additional guidance. EFB electronic checklists cannot be interactive with other aircraft systems;
   16. Weather and aeronautical data;
   17. Airport moving map display (AMMD);
   18. Applications that make use of the Internet and/or other Aircraft Operational Communications (AOC).

Back to TAA Advisory 2012-01

Top of page