Minimum Operational Performance Standards (MOPS) for Flight-deck Interval Management (FIM) Change 1
|Publication Date:||17 December 2020|
PURPOSE AND SCOPE
DO-361A / ED-236A Change 1 (hereafter referred to as Change 1) includes updates, corrections, and additional materials to support implementation of the Flight-deck Interval Management (FIM) Minimum Operational Performance Standards (MOPS) DO- 361A / ED-236A. The largest of these is the inclusion of Test Vectors in Appendix G and related supplemental material. The Test Procedures (Chapter 3) from the published MOPS have been included in their entirety, as small edits can be found throughout that chapter to align with the finalized Test Vectors. Any changes from the published MOPS have been highlighted; with the exception of those in Appendix G, which is entirely new. Section numbers presented within this document are identical to those in the published MOPS for ease of comparison.
Ownship Requirements for IM (§22.214.171.124) and Traffic Requirements for IM (§126.96.36.199) have been updated to reflect the inclusion of surveillance validity and quality metric coasting requirements in DO-317C / ED-194B. The change replaces the surveillance validity and quality metric coasting requirements published in DO-361A / ED-236A with a new reference to DO-317C / ED-194B.
The sections concerning Maintain Stage - Time-based, Without an Achieve Stage (§188.8.131.52.2.2.2) and Data-linked Winds and Temperatures (§184.108.40.206.1) include edits to language in the published MOPS for clarity and correctness.
The sections listed below are included to accommodate changes made in the final version of DO-260C / ED-102B and DO-181F / ED-73F, which occurred after publication of DO-361A / ED-236A.
• §220.127.116.11.1 ASSAP Input from ADS-B
• §18.104.22.168.3 Validation of ADS-B Version 3 Data from IM Traffic
• §22.214.171.124.4 Airspeed Profile
• §126.96.36.199.6 Predicted Wind
• §188.8.131.52 Recalculation of Ownship and Traffic Trajectories
• Appendix C.2.2.5 Updating Wind and Temperature Information and Recalculating Predicated Trajectories