Published 2017-06-28 by SAE International in United States
This document establishes techniques for validating that an Aircraft Station Interface (ASI) complies with the interface requirements delineated in MIL-STD-1760C. For validation of aircraft designed to MIL-STD-1760A Notice 2 AS4764 Issued 1995-04 applies. For validation of aircraft designed to MIL-STD-1760B Notice 3 AS47641 Issued 1999-08 applies.
Published 2017-06-28 by SAE International in United States
This document establishes techniques for validating that an Aircraft Station Interface (ASI) complies with the interface requirements delineated in MIL-STD-1760B Notice 3. For validation of aircraft designed to MIL-STD-1760A Notice 2 AS4764 Issued 1995-04 applies.
Published 2017-06-27 by SAE International in United States
The information presented in this AIR is intended to provide designers of armed unmanned systems with guidelines that may be applied to ensure safe integration and operation of weapons on unmanned platforms. The guidelines have been developed from experiences gained in the design and operation of weapons on manned aircraft that have been accepted by relevant safety authorities in the USA and Europe and proven effective over many years. Whilst the guidelines have been developed from experience with aircraft operations, the concepts are considered equally applicable to non-aircraft systems, such as those used on the surface or undersea environments. This document does not attempt to define or describe a comprehensive safety program for unmanned systems. System Safety is a system characteristic and a non-functional requirement. It has to be addressed at each level of system design, system integration and during each phase of system operation. System safety is achieved when the system operation does not cause inadvertent personnel injuries, destruction of the system or damage to the environment. Section 3 of the document contains an…
Published 2017-01-12 by SAE International in United States
This SAE Aerospace Standard (AS) defines the editorial format and policies necessary for the publication of Interface Control documents. The Common Interface Control Document Format Standard defines a common format for aircraft/store interface documents to foster increased interoperability. It is designed with the versatility to serve differing “ICD” philosophies and organizations. This aerospace standard defines the common technical data sections for the Common Interface Control Document Format down to the third header level for the majority of sub-sections. The Common Interface Control Document Format Aerospace Standard provides a structured document format in appendixes supported by example paragraphs, drawings, etc.
Published 2016-11-18 by SAE International in United States
This Handbook is intended to provide useful information on the application of AS5716A. It is for use by System Program Offices, aircraft prime contractors, avionics and store system designers, system integrators and equipment manufacturers and users. This Handbook was prepared to provide users of the standard of the rationale and principles considered during the development of the standard. It is anticipated that the handbook will serve to assist developers in introducing new technology to achieve compliance with the standard and the underlying principles of the standard. It is intended that the Handbook be used alongside the standard, as it does not contain significant extracts of the standard.
Published 2016-09-16 by SAE International in United States
This document was prepared by the SAE AS-1B1 IMM Task Group to explain and document background information and design decisions made during the development of AS5726. This handbook is published separately to preserve information that is not required or provided in the AS5726 but may be important to system designers to ensure interoperability between the Micro Munition Host and Micro Munition. As a handbook, it cannot be invoked as a requirement in a contract. The structure and numbering of this document mirrors that of AS5726 for the convenience of readers. Headings such as “Requirements” in this handbook should not be interpreted as invoking requirements.
Published 2016-01-02 by SAE International in United States
This Common Interface Control Plan (CICP) establishes the methodology for developing, controlling, and managing the technical interfaces between and within systems. An interface defines the interaction at a defined point between entities to achieve a combined system capability. A common interface defines the shared interaction between multiple systems on either side of the interface. The document is not intended to directly control any other aspects of program management, such as matters of contractual, financial, or those of an intellectual property rights nature. Members in the interface control process include: procurement authorities, design authorities, and other related agencies as defined in the specific System Interface Control Plan (SICP). For the purposes of this plan, only the terms Procuring Organization and Producing Organization will be used. This plan is predicated upon formal agreements between participating organizations that provide: 1 Authority to participate in Interface Control Working Group (ICWG) and decision-making processes. 2 Primary interface control, interface problem resolution, and interface impact assessments through the ICWG. 3 Higher level interface management under the purview of the appellate process…
A list of downloadable items.
Please Wait. Loading Available Formats...
This modal will allow the user to download citation information or export specific fields of data into one of three file formats: Excel, comma-separated values, or text.
Sorry, this document is already one of your favorites.
Share this content via social media.
Share Via Email
Email sent successfully!
Use this modal to save a search.
The current search and criteria have already been saved. Please modify your criteria to save as a new search.
Request Sent successfully!
Search Tips: Search Operators:AND, OR, NOT; Wild Cards; Using Quotes
SAE MOBILUS® Search Tips
Please note: All terms not contained within quotes, will be evaluated using the OR operator. This means that your search results will contain all results that contain ANY of the entered terms.
AND, OR, NOT
SAE MOBILUS supports the use of the AND, OR and NOT BOOLEAN operators ONLY function with the Advanced Search.
Using the asterisk, ( * ) allows you to search for a partial word. For example, entering a keyword search of aero* will search for any word beginning with aero.
Using the question mark, ( ? ) allows you to search for a word with a single character wildcard. For example, searching for t?re would match both tire and tyre
Words in double quotes " " are treated as a phrase. Conducting a search for "heat model" will return all results in which the exact phrase "heat model" is found, while "heat modeling" would NOT be included.
A term combined with a phrase will be joined with an OR operator.
Searching for Standards
When searching for a standard please use the entire Document Number assigned, which includes the abbreviation. A space can be used, or omitted between the abbreviation and number.