Flow Control

ATC provides IFR aircraft separation services for NAS users. Since the capabilities of IFR operators vary from airlines operating hundreds of complex jet aircraft to private pilots in single engine, piston-powered airplanes, the ATC system must accommodate the least sophisticated user. The lowest common denominator is the individual controller speaking to a single pilot on a VHF voice radio channel. While this commonality is desirable, it has led to a mindset where other opportunities to interact with NAS users have gone undeveloped. The greatest numbers of operations at the 20 busiest air carrier airports are commercial operators (airlines and commuters) operating IFR with some form of ground-based operational control. Since not all IFR operations have ground-based operational control, very little effort has been expended in developing ATC and Airline Operations Control Center (AOC) collaboration techniques, even though ground-based computer-to-computer links can provide great data transfer capacity. Until the relatively recent concept of Air Traffic Control-Traffic Flow Management (ATC-TFM), the primary purpose of ATC was aircraft separation, and the direct pilot-controller interaction was adequate to the task. Effective and efficient traffic flow management now requires a new level of control that includes the interaction of and information transfer among ATC, TFM, AOCs, and the cockpit. [Figure 1-17]

Flow Control Restriction

As the first step in modernizing the traffic flow management infrastructure, the FAA began reengineering traffic flow management software using commercial off-the-shelf products. In FY 1996, the FAA and NASA collaborated on new traffic flow management research and development efforts for the development of collaborative decision making tools that will enable FAA traffic flow managers to work cooperatively with airline personnel in responding to congested conditions. Additionally, the FAA provided a flight scheduling software system to nine airlines.