Annex A: Descriptions and Examples of "Type A" Software Applications

1. Type A Software Applications:
   1. do not substitute for, or replace, any paper, system functionality or equipment required by the technical or operational airworthiness regulations;
   2. do not require compliance with RTCA DO-178 – Software Considerations in Airborne Systems and Equipment Certification;
   3. are to be evaluated in accordance with the guidance provided in Annex C of this advisory, Section 3 – Software Application Evaluation; and
   4. require an OAC or OA prior to use.
2. Below is a non-exhaustive list of examples of Type A EFB applications:
   1. Aircraft Maintenance Manuals;
   2. Aircraft flight log and servicing records;
   3. Service bulletins/published Airworthiness Directives, etc.;
   4. Airport-specific rules and regulations;
   5. Airport/Facility Directory (A/FD) data (e.g., fuel availability, land-and-hold-short operations (LAHSO), distances for specific runway combinations, etc.); Canada Flight Supplement (CFS) in Canada;
   6. Airport diversion policy guidance, including a list of Special Designated Airports and/or approved airports with emergency medical service (EMS) support facilities;
   7. Flight Management System/Flight Management and Guidance System problem report forms;
   8. Aircraft parts manuals;
   9. Required VHF Omni-directional Range (VOR) check records;
   10. Noise abatement procedures for arriving and departing aircraft;
   11. Published (graphical) pilot Notices to Airmen (NOTAM);
   12. International Operations Manuals, including regional supplementary information and International Civil Aviation Organization (ICAO) differences;
   13. Aeronautical Information Publications (AIP);
   14. Aeronautical Information Manual (AIM); and
   15. Flight crew qualification logs.

Back to TAA Advisory 2012-01

Top pf page