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
RTCA DO-328
New product
RTCA DO-328 Revision A, September 22, 2015 Safety, Performance and Interoperability Requirements Document for Airborne Spacing –Flight Deck Interval Management (ASPA-FIM)
More info
Description / Abstract:
This document includes the definition of the services and the
Environmental Conditions relevant to the implementation of the
ASPA-FIM application and the operational, safety, performance and
interoperability requirements for using the application.
Note: Requirements that provide protection against intentional behavior causing harm or sabotage are beyond the scope of this document.
Note: Requirements related to the recording of ADS-B data for accident or incident investigation purposes are beyond the scope of this document.
Purpose of the document
This document defines and allocates the set of minimum requirements for the end-to-end operational, safety, performance, and interoperability aspects for implementations of an initial set of IM Operations. The requirements and their initial application are also expected to form the basis for all future ASPA-FIM implementations. Allocation of these requirements is done by this SPR/INTEROP to the necessary domains of the CNS/ATM system, i.e., at aircraft and ground domain level.
Note: Requirements allocated to the ground domain are limited to operational and interoperability requirements. Safety and performance requirements on how the ground domain determines when to issue IM Clearances to help schedule and manage the traffic flow are out of scope of the ASPA-FIM application.
These requirements can be used as a component for approval processes including aircraft type design approval, aircraft operator operational approval and Air Traffic Services (ATS) provider operational approval. This document examines a set of IM Operations in expected near-term environments, yet does not define any singular Operational Application. Therefore, this document can not be a sole means for such approval processes. Rather, the minimum requirements specified and the methodologies defined within provide a path to those approvals for given Operational Applications. This SPR/INTEROP document is also written to support system specific standards (e.g., Minimum Aviation System Performance Standard [MASPS], Minimum Operational Performance Standard [MOPS], and Technical Standard Orders [TSOs]) that will define specific Operational Applications and may be required for many airspace regulators.
Note: Requirements that provide protection against intentional behavior causing harm or sabotage are beyond the scope of this document.
Note: Requirements related to the recording of ADS-B data for accident or incident investigation purposes are beyond the scope of this document.
Purpose of the document
This document defines and allocates the set of minimum requirements for the end-to-end operational, safety, performance, and interoperability aspects for implementations of an initial set of IM Operations. The requirements and their initial application are also expected to form the basis for all future ASPA-FIM implementations. Allocation of these requirements is done by this SPR/INTEROP to the necessary domains of the CNS/ATM system, i.e., at aircraft and ground domain level.
Note: Requirements allocated to the ground domain are limited to operational and interoperability requirements. Safety and performance requirements on how the ground domain determines when to issue IM Clearances to help schedule and manage the traffic flow are out of scope of the ASPA-FIM application.
These requirements can be used as a component for approval processes including aircraft type design approval, aircraft operator operational approval and Air Traffic Services (ATS) provider operational approval. This document examines a set of IM Operations in expected near-term environments, yet does not define any singular Operational Application. Therefore, this document can not be a sole means for such approval processes. Rather, the minimum requirements specified and the methodologies defined within provide a path to those approvals for given Operational Applications. This SPR/INTEROP document is also written to support system specific standards (e.g., Minimum Aviation System Performance Standard [MASPS], Minimum Operational Performance Standard [MOPS], and Technical Standard Orders [TSOs]) that will define specific Operational Applications and may be required for many airspace regulators.