Search Results

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.

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

This document describes effective methods to manage and distribute operation flight software programs, aeronautical data bases and other forms of software used within an airline organization. Topics include software acquisition, software receiving, software distribution and necessary documentation. The FLS management process described in ARINC 667 is compatible with published FAA/JAA guidance on this subject. Software suppliers, airline users and regulators will find this document to be a practical and effective guide.

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.

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 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 the maintenance community for identifying the modification status of avionics components and for preparing avionics service bulletins. This standard coordinates various methods used by airframe manufacturers and operators, for marking or identifying avionics that has been modified.

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.

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.

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.

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

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.

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.

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.

This standard defines standards for loadable software parts and software transport media. It describes the principles and rules to be applied to any part of a data load system, to ensure compatibility and interoperability. It includes part numbering, content, labeling and formatting of loadable software parts and software transport media.

Industry rules and guidelines support/mandate equivalency, but provide very little guidance on how to realize MPP substitution. Currently, industry guidelines fail to provide adequate direction to maintenance facilities for material, process, and part equivalencies. Suitable substantiation procedures to be able to select alternate materials are demanded by the air transport industry. The purpose of ARINC Report 670 is to provide clear definitions for materials, processes, parts, substantiation requirements, decision boundaries and limitations, and a standard process for equivalency determination. This report is intended as general guidance for avionics maintenance facilities; however, this does not preclude its use for other sectors of aircraft maintenance as appropriate.