Cart
0
Product
Products
(empty)
No products
To be determined
Shipping
$0.00
Total
Product successfully added to your shopping cart
Quantity
Total
There are 0 items in your cart.
There is 1 item in your cart.
Total products
Total shipping
To be determined
Total
Reduced price!
View larger
View larger
ARINC 702A
New product
ARINC 702A 2018 Edition, August 28, 2018 ADVANCED FLIGHT MANAGEMENT COMPUTER SYSTEM
More info
Description / Abstract:
Purpose and Scope
This document sets forth the characteristics of an advanced Flight Management Computer System (FMS) specifically designed for installation in new generation aircraft. The system is also intended for retrofit in aircraft that presently use ARINC 700 series equipment. The advanced FMS is expected to provide expanded functional capability beyond that defined in ARINC Characteristic 702 and support the necessary requirements for operation in the future Communication, Navigation, and Surveillance/Air Traffic Management (CNS/ATM) operational environment.
The attributes of this environment include extensive use of Global Navigation Satellite System (GNSS), Required Navigation Performance (RNP) based navigation, air to ground data link for communications and surveillance, and the associated crew interface control/display capabilities. A comprehensive description of the attributes of the future CNS/ATM environment and its impact to various avionics architectures can be found in ARINC Report 660B: CNS/ATM Avionics Architectures Supporting NextGen/SESAR Concepts. Those NextGen/SESAR concepts and their relative effects on the FMS are addressed in this document. The functional requirements defined herein also apply to a Flight Management Function (FMF) in an Integrated Modular Avionics (IMA) architecture with software partitions.
The ICAO Future Air Navigation System (FANS) Standards and Recommended Practices (SARPs) for CNS/ATM are currently evolving and are expected to continue to evolve. The requirements included in this document are intended to support Performance Based Navigation (PBN) and Trajectory-Based Operations (TBO) and be consistent with the latest versions of the following documents:
• ICAO Doc 9613: Performance-Based Navigation Manual (PBN Manual)
• RTCA DO-236: Minimum Aviation System Performance Standards: Required Navigation Performance for Area Navigation (RNP MASP)
• RTCA DO-283: Minimum Operational Performance Standards for Required Navigation Performance for Area Navigation (RNP MOPS)
This document does not specify the requirements for a Control Display Unit (CDU). While the CDU is included in the original version of ARINC Characteristic 702, the capabilities of the Multi-Purpose Control Display Unit (MCDU) are separately defined in ARINC Characteristic 739A. This document defines the functional and interface characteristics of the FMS and assumes that the appropriate MCDU characteristics are defined separately in ARINC Characteristic 739A or elsewhere.
The vast majority of military and government specifications for equipment design and construction usually employ specification language; that is, terms such as thou shalt and thou shalt not. However, that type of language makes it difficult to describe preferences which have grown out of airline experience which designers might weigh differently. For this reason, this standard, like other ARINC Standards, represents guidance material which attempts to acquaint the manufacturer with the need for specific design practices rather than to tell them that they must meet certain requirements under all circumstances.
ARINC originated with the airlines and the ARINC Standards are created as airline requirements for system implementers. Therefore, the use of the word “should” in this document carries with it the expectation of incorporation. This is especially true in the context of fit, form, interface requirements, and crew indication requirements. In allowing for the various architectures described in this document it is expected that the functions will operate, at a system level, as described in this document.
COMMENTARY
End users should be aware that there can be possible differences in hardware and/or tailored implementation of certain functions from ARINC 702A so that the FMC may meet fit, form, and intended functional requirements for the particular airframe. Differences may be due to the various airplane architectures, system limitations, and/or specific end user needs which take precedence over complete compliance with ARINC 702A.
This document sets forth the characteristics of an advanced Flight Management Computer System (FMS) specifically designed for installation in new generation aircraft. The system is also intended for retrofit in aircraft that presently use ARINC 700 series equipment. The advanced FMS is expected to provide expanded functional capability beyond that defined in ARINC Characteristic 702 and support the necessary requirements for operation in the future Communication, Navigation, and Surveillance/Air Traffic Management (CNS/ATM) operational environment.
The attributes of this environment include extensive use of Global Navigation Satellite System (GNSS), Required Navigation Performance (RNP) based navigation, air to ground data link for communications and surveillance, and the associated crew interface control/display capabilities. A comprehensive description of the attributes of the future CNS/ATM environment and its impact to various avionics architectures can be found in ARINC Report 660B: CNS/ATM Avionics Architectures Supporting NextGen/SESAR Concepts. Those NextGen/SESAR concepts and their relative effects on the FMS are addressed in this document. The functional requirements defined herein also apply to a Flight Management Function (FMF) in an Integrated Modular Avionics (IMA) architecture with software partitions.
The ICAO Future Air Navigation System (FANS) Standards and Recommended Practices (SARPs) for CNS/ATM are currently evolving and are expected to continue to evolve. The requirements included in this document are intended to support Performance Based Navigation (PBN) and Trajectory-Based Operations (TBO) and be consistent with the latest versions of the following documents:
• ICAO Doc 9613: Performance-Based Navigation Manual (PBN Manual)
• RTCA DO-236: Minimum Aviation System Performance Standards: Required Navigation Performance for Area Navigation (RNP MASP)
• RTCA DO-283: Minimum Operational Performance Standards for Required Navigation Performance for Area Navigation (RNP MOPS)
This document does not specify the requirements for a Control Display Unit (CDU). While the CDU is included in the original version of ARINC Characteristic 702, the capabilities of the Multi-Purpose Control Display Unit (MCDU) are separately defined in ARINC Characteristic 739A. This document defines the functional and interface characteristics of the FMS and assumes that the appropriate MCDU characteristics are defined separately in ARINC Characteristic 739A or elsewhere.
The vast majority of military and government specifications for equipment design and construction usually employ specification language; that is, terms such as thou shalt and thou shalt not. However, that type of language makes it difficult to describe preferences which have grown out of airline experience which designers might weigh differently. For this reason, this standard, like other ARINC Standards, represents guidance material which attempts to acquaint the manufacturer with the need for specific design practices rather than to tell them that they must meet certain requirements under all circumstances.
ARINC originated with the airlines and the ARINC Standards are created as airline requirements for system implementers. Therefore, the use of the word “should” in this document carries with it the expectation of incorporation. This is especially true in the context of fit, form, interface requirements, and crew indication requirements. In allowing for the various architectures described in this document it is expected that the functions will operate, at a system level, as described in this document.
COMMENTARY
End users should be aware that there can be possible differences in hardware and/or tailored implementation of certain functions from ARINC 702A so that the FMC may meet fit, form, and intended functional requirements for the particular airframe. Differences may be due to the various airplane architectures, system limitations, and/or specific end user needs which take precedence over complete compliance with ARINC 702A.