Search Results

This guide has been written as an applications manual for writing avionics test specifications that conform to ARINC Specification 616. It provides advice for converting ATLAS test specifications into ATLAS test programs and implementing them on Automatic Test Equipment (ATE).This guide has been written as an applications manual for writing avionics test specifications that conform to ARINC Specification 616. It provides advice for converting ATLAS test specifications into ATLAS test programs and implementing them on Automatic Test Equipment (ATE).

Test equipment practices change over time to better suit the maintenance philosophies of the airlines. This standard is an update of ARINC 602 following the introduction of new digital test equipment standards and the publication of ARINC 608A. This standard includes specific references to On-board Maintenance Systems (OMS) and Automatic test Equipment (ATE) used within the maintenance community.

This standard provides considerations for the procurement and design requirements of TE to be used for maintenance and troubleshooting of air transport components in both the shop and/or flight line environment. Although the term TE is used, this standard can be applied to other types of support equipment utilized in the aviation industry, such as shop data loaders, portable maintenance aids, etc.

This standard establishes guidelines that should be observed during initial design, production and maintenance of avionics LRUs, and to present short-term strategies to minimize costs and impacts associated with decreasing availability of electronic components.

This document provides operators with guidelines for developing maintenance support contracts with suppliers. It identifies common supplier support products, services, and data; why these are important to maintenance organizations; and the impact on airline operating costs if they are not available.

This standard describes the characteristics of a standard firmware loader for avionic shops. It is capable of copying digital information into memory devices installed in circuit card assemblies, Line Replaceable Modules (LRMs) and On-Board Replaceable Modules (OBRMs). It contains the recommendations of the air transport community concerning the design and development of firmware loader equipment.

This standard defines an airline-recommended subset of the Abbreviated Test Language for All Systems (ATLAS)intended to be used in conjunction with test systems that are compliant with ARINC 608A. ATLAS is a standard abbreviated English language used in preparation and documentation of test procedures that can be implemented with automatic or semiautomatic test equipment.

Defines a generalized process by which anomalies in aircraft systems can be detected. This process is intended to improve timely isolation and resolution of those anomalies. The objective is to reduce costs to the airlines, airframe manufacturers and aircraft systems suppliers by removing anomalous behavior from aircraft systems in a timely manner.

This standard provides guidance to ATLAS test programmers for developing, writing and documenting test programs in ARINC 626 ATLAS. This is a companion standard to ARINC 608A, Design Guidance for Avionics Test Equipment. It provides guidance to managers and system integrators for standardizing test programs and their documentation.

ARINC Report 847: Product Development Guidance for Maintainability and Testability (PDMaT) is intended to be used as guidance to enhance the design of avionic equipment, with a focus on maintainability and testability characteristics. It is a separate and parallel standard to ARINC Report 607: Design Guidance for Avionic Equipment. This document does not represent the complete formula for successfully designing and manufacturing avionics equipment or system. It does present the vision of the airline community based on extensive experience gained through the use of such equipment.

The purpose of this document is to establish guidelines that should be observed during initial design, production, and maintenance of aircraft components, and to present short-term and long-term strategies to minimize the costs and impacts associated with decreasing availability of components.

This is a final Report of the Avionics Maintenance Conference (AMC) Task Group 116 which was formed to discover the causes of "No Fault Found" in avionics equipment during test. This standard identifies sources of this problem and provides recommendations for its improvement.

The purpose of this standard is to provide a method for packaging aircraft software parts for distribution using contemporary media or by electronic distribution. This project intends to standardize and provide guidance for the storage of floppy based software, currently packaged in media set parts. This standard format can be then stored or distributed on a single physical media member (CD-ROM), or by electronic crate. The obsolescence of floppy disks drive an urgent need for this guidance.

This document defines the aircraft industry's standards for Loadable Software Parts (LSPs) and Media Set Parts (MSPs). It describes the common principles and rules to be applied to any part of a data load system to ensure compatibility and inter-operability. It includes part numbering, content, labeling, and formatting of an LSP, and a Media Set containing LSPs.

This standard provides guidance to those who develop avionics test programs and the source documentation on which they are based. This includes guidelines for all steps and phases within the TPS life cycle.

This standard provides guidance to those who develop avionics test programs and the source documentation on which they are based. This includes guidelines for all steps and phases within the TPS life cycle.

The goal of this document is to provide the basis for a structured process to identify, analyze and resolve NFF issues. The NFF issues include providing guidance for decision making pertinent to the root causes of NFF, enabling action in an early stage of the component repair cycle, reducing costs involved with units unnecessarily removed from an aircraft (e.g. maintenance practices, operational factors, training, documentation etc.), highlighting the need for addressing the causes of NFF through component and system design, addressing the development/improvement of maintenance processes, and providing a framework for the interaction between the different domains for the users of this document (listed below) to implement their own strategies.

ARINC 668 provides guidelines for the process used to establish the equivalency of TTE and related procedures other than that recommended by the OEM. Primarily, ARINC 668 is concerned with equipment specified or recommended for the purpose of performing specific tasks concerning the airworthiness of an article (e.g., avionics, hydraulics, pneumatics, mechanical devices, etc.).

With the emergence of RFID (Radio Frequency Identification) as a tool to streamline the supply chain, the airline industry determined that a technology standard for both the RFID tag hardware and data needed to be developed. This is required so that industry-wide interoperability can be achieved. Fundamental requirements have been identified and agreed upon by the airline industry. These core requirements build the framework from which this standard was derived. The usage of an open standard UHF-RFID technology will benefit the entire airline industry. While the intent of this document is to address the usage of UHF-RFID tags on aircraft parts, the technology and benefits are applicable to other items that would be in airline inventory. To that extent, the term Product has been used in this standard. This document is specific to the requirements for and installation of UHF-RFID tags and does not address data usage or the tools and systems used to collect the data.

This document provides guidance for the use of international standards for the maintenance of lead-free electronic equipment. The purpose is to assist manufacturers, maintenance facilities, and operators to define lead-free soldering requirements and to minimize the set of lead-free solders, processes, and practices to gain consistency across the industry.