Latest revision as of 16:28, 3 February 2021

Abstract

The corridors-in-the-sky concept imitates the highway system in ground transportation. The benefit expected from a corridor relies on its capability of handling high density traffic with negligible controller workload, the acceptance of extra fuel or distance, and the complexity reduction in underlying sectors. This work evaluates a selected corridor from these perspectives through simulations. To examine traffic inside the corridor, a corridor traffic simulation tool that can resolve conflicts is developed using C language. Prescribed conflict resolution maneuvers mimic corridor users’ behaviors and conflict resolution counts measure complexity. Different lane options and operational policies are proposed to examine their impacts on complexity. Fuel consumption is calculated and compared for corridor traffic. On the other hand, to investigate the complexity of non-corridor traffic in underlying sectors, the existing Airspace Concept Evaluation System tool is utilized along with the Automated Airspace Concept tool. The number of conflict resolutions is examined and treated as the complexity measurement. The results show heavy traffic can be managed with low complexity for a historical traffic schedule simulated with appropriate operational policies and lane options. For instance, with 608 flights and peak aircraft count of 100, only 84 actions need to be taken in a 24-hour period to resolve the conflicts for an 8-lane corridor. Compared with the fuel consumptions with great circle trajectories, the simulation of corridor traffic shows that the total extra fuel for corridor flights is 26,373 gallons, or 2.76%, which is 0.38% less than flying filed flight plans. Without taking climb and descent portions of corridor traffic, the complexity of underlying sectors is reduced by 17.71%. However the climb and descent portions will eliminate the reduction and the overall complexity of sectors is actually increased by 9.14%.

Original document

The different versions of the original document can be found in:

• http://www.aviationsystemsdivision.arc.nasa.gov/publications/2010/Xue_ATIO2010_Final.pdf

• http://arc.aiaa.org/doi/pdf/10.2514/6.2010-9112,

http://dx.doi.org/10.2514/6.2010-9112

• https://ntrs.nasa.gov/search.jsp?R=20110008339,

https://www.aviationsystems.arc.nasa.gov/publications/2010/Xue_ATIO2010_Final.pdf,

https://arc.aiaa.org/doi/10.2514/6.2010-9112,

https://trid.trb.org/view.aspx?id=1122890,

https://repository.exst.jaxa.jp/dspace/handle/a-is/248041,

https://academic.microsoft.com/#/detail/2046790253