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 interface standard applies to fuzes used in airborne weapons that use a 3-in fuze well. It defines: - Physical envelope of the fuze well at the interface with the fuze. - Load bearing surfaces of the fuze well. - Physical envelope of the fuze and its connector. - Mechanical features (e.g., clocking feature). - Connector type, size, location and orientation. - Retaining ring and its mechanical features (e.g., thread, tool interface). - Physical envelope of the retaining ring at the interface with the fuze. - Physical space available for installation tools. - Torque that the installation tool shall be capable of providing. This standard does not address: - Materials used or their properties. - Protective finish. - Physical environment of the weapon. - Explosive interface or features (e.g., insensitive munitions (IM) mitigation). - Charging tube. - Torque on the retaining ring or loads on the load bearing surfaces.
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.
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.
Loran or Enhanced Loran (e)Loran Position, Navigation, and Timing (PNT) Interface Specification for the Embedded Global Positioning System and Inertial Navigation System (EGI)
This interface control document defines the (e)Loran based alternate PNT interface for the EGI. It provides technical descriptions of definitions, specifications, and explanations for general distribution to providers, manufacturers, and consumers.
This information report provides an overview of the eLoran PNT system.
A Guideline for Using the Transmitted Enhanced Loran (eLoran) Signal for Timing, Phase, and Frequency
This recommended practice provides guidance for using the eLoran signal for timing, phase, and frequency.
This eLoran transmitted signal interface control document describes the technical descriptions of definitions, specifications, and explanations for general distribution to providers, manufacturers, and consumers.
The Loran-C Radionavigation System, managed by the U.S. Coast Guard, is the federally provided radionavigation system for civil marine use in the U.S. coastal waters. It is also designated by the Federal Aviation Administration (FAA) as a supplementary system in the National Airspace System (NAS). This system provides accurate radionavigation and timing services to users in the United States of America and Canada. Loran-C is also being used and developed by several other countries in Europe and Asia. Estimates of Loran-C system accuracy must take into consideration the transmitted signal, signal propagation, signal reception, interference or errors from outside sources such as natural and man-made electromagnetic noise, skywave contamination, geometric dilution of precision, other Loran-C signals, communication information superimposed on the navigation signal, and coordinate conversion.
SAE J1362 presents graphical symbols for use on operator controls and other displays on off-road work machines as defined in SAE J1116 plus mobile cranes but excluding agricultural tractors. Symbols for agricultural tractors are covered by ASABE S304, ISO 3767-1, and ISO 3767-2.
This document defines the requirements for developing a DMSMS Management Plan, hereinafter also called the Plan, to assure customers that the Plan owner is using a proactive DMSMS process for minimizing the cost and impact that part and material obsolescence will have on equipment delivered by the Plan owner. The technical requirements detailed in clause 5 ensure that the Plan owner can meet the requirement of having a process to address obsolescence as required by Industry Standards such as EIA-4899 "Standard for Preparing an Electronic Components Management Plan" and DoD Programs as required by MIL-STD-3018 "Parts Management". Owners of DMSMS Management Plans include System Integrators, Original Equipment Manufacturers (OEM), and logistics support providers.
This SAE Aerospace Information Report (AIR) outlines comprehensive aircraft flight control system fault isolation methodology that has proven to be effective. The methodology presented in this Information Report has been used in several successful fault isolation efforts on military aircraft.
Validation and Verification Process Steps for Monitors Development in Complex Flight Control Systems
This SAE Aerospace Recommended Practice (ARP) provides a process for the verification and validation of monitors used in flight control, utility control, and related components and systems. It is intended to serve as a system specific companion document to SAE ARP 4754.
ARP4754 Process Frameowrk with Checlists and templates for flight control and vehicle management systems
This AIR is for use by OEM's and Suppliers developing process gate checklists for highly integrated, complex flight control and vehicle management systems to support the life cycle development validation and verification activities prescribed by ARP4754.
This SAE Aerospace Recommended Practice (ARP) covers the general requirements and test procedures recommended for use with white incandescent integrally lighted instruments. Its use should provide uniformity of illumination from instrument to instrument and legibility under daylight operation. An appendix is provided to familiarize the designer with some of the techniques used to obtain uniformity of color and illumination in various types of instruments.
This document establishes techniques for validating that an Aircraft Station Interface (ASI) complies with the interface requirements delineated in MIL-STD-1760 Revision E.
Failure Modes and Effects Analysis Process for Flight Critical Actuation Electronic Systems and Software
This ARP provides guidelines for improving the Failure Mode and Effect Analysis process, including alternative or additional methods, for flight critical actuation equipment electronics and software.
This SAE Aerospace Standard (AS) contains requirements for a digital time division command/response multiplex data bus, for use in systems integration, that is functionally equivalent to MIL-STD-1553B with Notice 2. Even with the use of this document, differences may exist between multiplex data buses in different system applications due to particular application requirements and the options allowed in this document. The system designer must recognize this fact and design the multiplex bus controller (BC) hardware and software to accommodate such differences. These designer selected options must exist to allow the necessary flexibility in the design of specific multiplex systems in order to provide for the control mechanism, architectural redundancy, degradation concept, and traffic patterns peculiar to the specific application requirements.
The information presented in this AIR is intended to provide information about current remote identification methods and practical considerations for remotely identifying UAS. Depending on rigor and adherence requirements, Aerospace Standard (AS) and Aerospace Recommended Practice (ARP) documents may be developed. For example, ARPs may provide methods to remotely identify UAS using existing hardware technologies typically available to most consumers. ARPs may also specify the information exchange and message format between unmanned aerial systems and remote interrogation instruments. An AS, however, may highlight the wireless frequency band, message type, message encoding bits, and message contents.
This recommended practice is intended to recommend the basic shapes and dimensions for knobs used in aircraft. Two basic types of knobs, the bar shape and the round shape, are described, as well as several widely used variations of these two basic shapes.
This SAE Aerospace Recommended Practice (ARP) provides guidance and interpretation on how to apply the objectives and activities in ARP4754A, “Guidelines for Development of Civil Aircraft and Systems”, to propulsion systems with electronic engine control. As the ARP4754A was developed and written more generally at the aircraft level, guidance will be provided to allocate ARP4754A objectives and activities to each side of the aircraft/engine interface. Using this guidance, certification applicants (aircraft and engine manufacturers) will be able to make proposals to coordinate their activities with their respective authority based on this allocation with the objective of distributing efficiently the compliance demonstration efforts between engine and aircraft certification and of avoiding unnecessary duplication of work.
Aerospace Fluid Power – Materials and Characteristics of Flight Control Servoactuators of Various Aircraft
This SAE Aerospace Information Report (AIR) defines the materials, strength and finishes utilized in current linear hydraulic flight control actuators. To keep the information at a relevant minimum, only cylinders (barrels), glands and pistons are listed. Also identified are the reasons for the material selection and any pertinent comments. All data were collected from the respective suppliers.
This standard specifies the characteristics of the SAE Linear Token Passing Bus (LTPB) Interface Unit. The LTPB provides a high reliability, high bandwidth, low latency serial interconnection network suitable for utilization in real time military and commercial applications. Multiple redundant data paths can be implemented to enhance reliability and survivability in those applications which require these attributes. The token passing and data exchange protocols are optimized to provide low latency and fast failure detection and correction. Physical configurations with bus lengths up to 1000 m can be accommodated. This specification defines the following: General Description (3.1): An overview of the LTPB protocol. Physical Media Interface (3.2): This portion of the standard defines the physical interface to both optical and electrical bus media.
(1) The Behavior Annex document provides a standard sublanguage extension to allow behavior specifications to be attached to AADL components. The aim of the Behavior Annex is to refine the implicit behavior specifications that are specified by the core of the language. The Behavior Annex targets the following goals: • Describe the internal behavior of component implementations as a state transition system with guards and actions. However, the aim is not to replace software programming languages or to express complex subprogram computations. • Extend the default run-time execution semantics that is specified by the core of the standard, such as thread dispatch protocols. • Provide more precise subprogram calls synchronization protocols for client-server architectures.
This SAE Aerospace Information Report (AIR) contains Lessons Learned from aerospace actuation, control and fluid power systems technologies. The lessons were prepared by engineers from the aerospace industry and government services as part of SAE Committee A-6, Aerospace Fluid Power, Actuation, and Control Technologies, and were presented to the A-6 during meetings held from 1989 through 1999. The document is organized into five sections covering systems, actuation, hydromechanical components, electrical components and miscellaneous, each further divided into subsections. The lessons are presented in a concise format of Problem, Issue, Solution and Lesson Learned, often with accompanying descriptive diagrams and illustrations for clarity and understanding.
This document recommends design criteria for the Flight Deck Alerting System. The FAS shall enhance safety of flight by providing early crew recognition of aircraft system or component status or malfunction as well as of crew operational error. The FAS, therefore, relates to aircraft configuration and flight phase as well as the aircraft systems. To fulfill this objective, the FAS must attract the attention of the crew, must state with clarity the nature and location of the problem, and must be highly reliable and thoroughly responsive to the operational requirements and environment. Wherever possible, it should provide guidance as to the corrective action.
This document recommends criteria and requirements for a Final Approach Spacing System (FASS) for transport aircraft. This is an Aerospace Recommended Practice to support the development of a Final Approach Spacing System (FASS) for Approach Spacing for Instrument Approaches (ASIA) operations.
ARP6283/1 In-Service Fiber Optic Inspection, Evaluation and Cleaning, Best Practices, Expanded Beam Termini
Provide user information on best practice methods and processes for the in-service inspection, evaluation and cleaning of expanded beam fiber optic interconnect components, test equipment, and test leads based on the information provided in AIR6031. This document provides the user with a decision making tool to be able to determine if the fiber optic components are acceptable for operation with expanded beam fiber optic termini.
ARP6283/2 In-Service Fiber Optic Inspection, Evaluation and Cleaning, Best Practices, Multi-Fiber Termini
Provide user information on best practice methods and processes for the in-service inspection, evaluation and cleaning of expanded beam fiber optic interconnect components, test equipment, and test leads based on the information provided in AIR6031. This document provides the user with a decision making tool to be able to determine if the fiber optic components are acceptable for operation with multi-fiber fiber optic termini.
AADL specifications may be processed manually or by tools for analysis and generation. This section documents additional requirements and permissions for determining compliance. Providers of processing method implementations must document a list of those capabilities they support and those they do not support. NOTE: Notes emphasize consequences of the rules described in the (sub)clause or elsewhere. This material is informative.