Showing posts sorted by relevance for query air traffic control traffic flow management. Sort by date Show all posts
Showing posts sorted by relevance for query air traffic control traffic flow management. Sort by date Show all posts

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.

Air Traffic Control System Command Center

The task of managing the flow of air traffic within the NAS is assigned to the Air Traffic Control System Command Center (ATCSCC). Headquartered in Herndon, Virginia, the ATCSCC has been operational since 1994 and is located in one of the largest and most sophisticated facilities of its kind. The ATCSCC regulates air traffic at a national level when weather, equipment, runway closures, or other conditions place stress on the NAS. In these instances, traffic management specialists at the ATCSCC take action to modify traffic demands in order to remain within system capacity.
They accomplish this in cooperation with:
  • Airline personnel.
  • Traffic management specialists at affected facilities.
  • Air traffic controllers at affected facilities.
Efforts of the ATCSCC help minimize delays and congestion and maximize the overall use of the NAS, thereby ensuring safe and efficient air travel within the U.S. For example, if severe weather, military operations, runway closures, special events, or other factors affect air traffic for a particular region or airport, the ATCSCC mobilizes its resources and various agency personnel to analyze, coordinate, and reroute (if necessary) traffic to foster maximum efficiency and utilization of the NAS.
The ATCSCC directs the operation of the traffic management (TM) system to provide a safe, orderly, and expeditious flow of traffic while minimizing delays. TM is apportioned into traffic management units (TMUs), which monitor and balance traffic flows within their areas of responsibility in accordance with TM directives. TMUs help to ensure system efficiency and effectiveness without compromising safety, by providing the ATCSCC with advance notice of planned outages and runway closures that will impact the air traffic system, such as NAVAID and radar shutdowns, runway closures, equipment and computer malfunctions, and procedural changes. [Figure 1-7]