Search Results

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.

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 primary purpose of BITE is to assist maintenance personnel in the proper maintenance of avionics systems in a cost-effective manner. A description of a Centralized Fault Display System (CFDS) is included in this standard. The CFDS accumulates fault data, presents this data to a maintenance operator, and assists troubleshooting by performing diagnostic tests and performing verification testing after installation of a replacement unit.

This document provides guidance for using industry standards for developing an ESD control program tailored to meet specific user requirements. In addition, it provides uniform guidance for maintenance facilities based on industry ESD standards, and therefore should be accepted throughout the air transport industry. This document is not a stand-alone document - it is intended to be used with the referenced international industry standards.

The primary goal of this standard is to describe the nature of Electrostatic Discharge (ESD) and its effects on digital avionics equipment. It provides information concerning methods to protect against ESD damage which could originate in many different ways.

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.

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.

This guidance standard was prepared in response to a need stated by air transport operators for uniformity in further subdividing the ATA Spec. 100 number system to better accommodate avionics systems. The ATA numbers are widely used in the maintenance community for inventory control, instruction manuals and equipment modification Service Bulletins.

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.

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.

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