Search Results

The purpose of this standard is to provide a source of definitions of terms and acronyms commonly used in the air transport maintenance community for test and evaluation with an emphasis on terms applicable to BITE.

ARINC Report 663 focuses on the many aspects related to component technical data and documentation including a common understanding of levels one - three maintenance (test, repair, re-certification). This includes defining the extent and format of OEM documentation to be delivered to the airline customers to support both the decision and technical requirements to accomplish level three maintenance; establishing minimum data requirements to support the airlines' decision relative to the accomplishment of level three maintenance (test solution, type of repair process, projected MTBF, modification potential, unit cost, alternative repairs, etc.); and identifying the minimum technical data requirements to support level three maintenance in airline shops for future avionics components (test, documentation).

This standard is a top-level guidance standard intended for the design of Automatic Test Equipment (ATE). It includes the definition of hardware and software needed for analog and digital signal testing using a Test Unit Adapter common interface. This standard describes the overall ATE system concept as well as the definition of the specific elements of those systems.

Avionics maintenance practices continue to improve through On-Board Maintenance System (OMS) recording. This standard defines the OMS which incorporates fault monitoring fault detection, BITE, and airplane condition monitoring system.

This document describes a secure internet facility for sending all types of aviation software using the world wide web (www). Software suppliers may use this document as a starting point for the construction of a secure web server utility. It provides sufficient flexibility and is compatible with numerous software distribution models. The file management structure is consistent with other ARINC standards for loadable software, and references ARINC 665 and ARINC 667 in particular.

This standard describes the format for electronic distribution of aircraft software parts and other contents between aerospace business partners using a digital container referred to as an EDS crate. This EDS standard is intended to promote consistent, secure distribution of EDS content to any appropriate destination.

This standard describes the format for electronic distribution of aircraft software parts and other contents between aerospace business partners using a digital container referred to as an EDS crate. This EDS standard is intended to promote consistent, secure distribution of EDS content to any appropriate destination.

This document provides industry guidance to supplement ATA standards and airframe requirements, addressing gaps and vague areas to move suppliers/vendors and airframers toward a common standard for format and wording in Vendor Service Bulletins (VSB) for Air Transport components. This document supplements the VSB guidance of iSpec 2200, providing clarity of requirements and resulting in a common standard wording and format of VSBs from all suppliers on all aircraft types. The guidance in this document is intended to be applied to VSBs created and released subsequent to the release of the guidance document and will not require the retroactive update of VSBs released prior to the creation and release of the guidance.

The purpose of this document is to provide guidance for the assignment, accomplishment, and reporting of investigations which exceed the regular workshop analysis and repair process for components. The operator, repair shop, and the component manufacturer should use this guideline to support a special investigation for aircraft components where additional attention is needed to fulfill reliability and authority requirements. This includes the process of assignment, the scope of accomplishment, and the content/style of the final report.

This standard is a top-level design guide for managing the development and maintenance of avionics software. It provides guidance for the design and development of avionics software for traditional ARINC 700-series equipment and IMA. This standard emphasizes the airline desire for user-modifiable software.

The purpose of this document is to establish guidance for Aircraft Support Data Management (ASDM). This guidance is intended for operators (e.g., pilot-in-command, maintenance activities, renter-pilot, or air carrier certificate holder) of transport aircraft.

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.

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.).

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 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.

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.

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.

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.

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.

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.