As noted above, all automated communication, sequence generation and clearance granting functions are performed by a local AACV data processing system. All participatory aircraft will be required to be ADS-B equipped, with a 40-mile transmission capability (although preliminary studies suggest that a transmission capability as low as 20 miles may be sufficient). ADS-B will provide the primary means of communication between the aircraft and the AACV system, providing general data transfer and surveillance functions. For our initial implementation, we have attempted to use a minimal message set, assuming substantial cost for all transmitted data.
For Approaching Aircraft: A specific on-condition request report would be designated, containing Aircraft ID, intended airport facility, and request code (landing or transition). This message could be generated by the on-board flight planning and/or navigation avionics at a specified point on the flight path (e.g. 20 NM to destination). “Priority granted” messages will be transmitted to the aircraft through data link and will consist of airport ID, aircraft ID, time, IAF assignment, and a single priority bit. “Priority denied” messages will consist of airport ID, aircraft ID, EFC time, and a single denial-of-priority bit. The denied aircraft would re-request at the EFC time to minimize message traffic. This time is also useful in the event of lost communications. An “operations complete” message could be used to unlock the airspace. Optionally, ADS-B surveillance data transmitted from the priority aircraft indicating the aircraft’s velocity has dropped below a specified threshold for a specified duration could perform this function. State data as described by RTCA DO-2426 (Time, Lat, Long, altitude, ground-referenced velocity vector, ID, category, navigational data quality) will be sufficient input for the ground-based arbitrator to calculate priority.
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址:A METHOD OF SEPARATION ASSURANCE FOR INSTRUMENT FLIGHT PROCE(6)