https://de.wikipedia.org/w/api.php?action=feedcontributions&feedformat=atom&user=RobbbbWikipedia - Benutzerbeiträge [de]2025-06-03T22:49:29ZBenutzerbeiträgeMediaWiki 1.45.0-wmf.3https://de.wikipedia.org/w/index.php?title=Flugverkehrskontrolle&diff=78114978Flugverkehrskontrolle2006-06-15T16:44:57Z<p>Robbbb: /* Next Generation ATC - Research */</p>
<hr />
<div>[[Image:Towers Schiphol small.jpg|right|thumb|200px|Air Traffic Control Towers (ATCTs) at [[Schiphol Airport]]]]<br />
<br />
'''Air traffic control''' ('''ATC''') is a service provided by ground-based [[Air traffic controller|controllers]] who direct [[aircraft]] on the ground and in the air. A controller's primary task is to ''separate'' certain aircraft &mdash; to prevent them from coming too close to each other horizontally and vertically. Secondary tasks include ensuring orderly and expeditious ''traffic flow'' and providing ''advisories'', such as weather information and navigation directions (''vectors'').<br />
<br />
In many countries, ATC services are provided throughout the majority of airspace, and its services are available to all users (private, military, and commercial). When controllers are responsible for separating some or all aircraft, such airspace is called "[[controlled airspace]]" in contrast to "[[uncontrolled airspace]]." Depending on the type of flight and the class of airspace, ATC may issue ''instructions'' that [[Aviator|pilots]] are required to follow, or merely ''advisories'' to assist pilots operating in the airspace. In all cases, however, the pilot has final responsibility for the safety of the flight, and may deviate from ATC instructions in an emergency.<br />
<br />
Air traffic control services can be divided into two major subspecialties, '''terminal control''' and '''en-route control'''.<br />
<br />
Terminal control includes the control of traffic (aircraft and vehicles) on the [[airport]] surface and airborne aircraft within the immediate airport environment. Generally, this is approximately a 30 to 50 nautical mile (56 to 93 km) radius of the airport, from the surface to about 10,000 ft (about 3,050 m). Terminal controllers work in facilities called [[control tower]]s and terminal area control (called ''Terminal Radar Approach Control'', or [[TRACON]], in the U.S.). At some locations, controllers are shared between tower control and the terminal area control, while at others the tower and the terminal area control are completely separate entities. For example, [[Philadelphia International Airport]] is served by a combined ("up/down") facility, while [[Chicago, Illinois|Chicago's]] [[O'Hare Airport]] is served by a control tower at the airport, and a remote TRACON located at [[Elgin, Illinois]].<br />
<br />
En-route controllers control the traffic between the terminals. They can also control traffic in and out of airports where the traffic volume does not warrant the establishment of a terminal ATC operation. En-route controllers work at facilities called [[Area Control Center|Area Control Centers]] or Air Route Traffic Control Centers.<br />
<br />
==Terminal Control==<br />
[[Image:Misawa Air Base Control Tower.jpg|thumb|right|250px|Controllers survey the field at [[Misawa Air Base]], [[Japan]].]]<br />
The primary method of controlling the immediate airport environment is visual observation from the [[control tower]]. The tower is a tall, windowed structure located on the airport grounds. Tower controllers are responsible for the separation and efficient movement of aircraft and vehicles operating on the taxiways and runways of the airport itself, and aircraft in the air near the airport, generally 2 to 5 nautical miles (4 to 9 km) depending on the airport procedures. <br />
<br />
[[Radar]] displays are also available to controllers at some airports. Controllers may use a radar system called [[Secondary Surveillance Radar]] also known as Airport Surveillance Radar for airborne traffic approaching and departing. These displays include a map of the area, the position of various aircraft, and data tags that include aircraft identification, speed, heading, and other information described in local procedures.<br />
<br />
The areas of responsibility for tower controllers fall into three general operational disciplines; '''Ground Control''' ('''Ground Movement Control''', or '''GMC''' in the U.K.), '''Local Control''' ('''Tower''' in North America), and '''Clearance Delivery''' ('''Planner''' in the U.K.) -- other categories, such as '''Apron Control''', may exist at extremely busy airports. While each tower's procedures will vary and while there may be multiple teams in larger towers that control multiple runways, the following provides a general concept of the delegation of responsibilities within the tower environment.<br />
<br />
===Ground Control===<br />
Ground Control (sometimes known as ''Ground Movement Control'') is responsible for the airport "movement" areas, or areas not released to the airlines or other users. This generally includes all taxiways, holding areas, and some transitional aprons or intersections where aircraft arrive having vacated the runway and departure gates. Exact areas and control responsibilities are clearly defined in local documents and agreements at each airport. Any aircraft, vehicle, or person walking or working in these areas is required to have clearance from the ground controller. This is normally done via VHF radio, but there may be special cases where other processes are used. Most aircraft and airside vehicles have radios. Aircraft or vehicles without radios will communicate with the tower via [[aviation light signals]] or will be led by vehicles with radios. People working on the airport surface normally have a communications link through which they can reach or be reached by ground control, commonly either by handheld radio or even [[cell phone]]. Ground control is vital to the smooth operation of the airport because this position might constrain the order in which the aircraft will be sequenced to depart, which can affect the safety and efficiency of the airport's operation.<br />
<br />
Some busier airports have systems, such as, ASDE-3, AMASS or [[ASDE-X]], designed to display aircraft and vehicles on the ground. These are used by the ground controller as an additional tool to control ground traffic, particularly at night or in poor visibility. There are a wide range of capabilities on these systems as they are being modernized. Older systems will display a map of the airport and the target. Newer systems include the capability to display higher quality mapping, radar target, data blocks, and safety alerts.<br />
<br />
===Local Control===<br />
Local Control (most often referred to as the generic "Tower" control, although Tower control can also refer to a combination of the local, ground and clearance delivery positions) is responsible for the active runway surfaces. Local control clears aircraft for take off or landing and ensures the runway is clear for these aircraft. To accomplish this, local control controllers are normally given 2 to 5 nautical miles (4 to 9 km) of airspace around the airport, allowing them to give the clearances necessary for airport safety. If the local controller detects any unsafe condition, a landing aircraft will be told to "go around" and will be re-sequenced into the landing pattern by the terminal area controller.<br />
<br />
Within the tower, a highly disciplined communications process between local and ground control is an absolute necessity. Ground control must request and gain approval from local control to cross any runway with any aircraft or vehicle. Likewise, local control must ensure ground control is aware of any operations that impact the taxiways and must work with the arrival radar controllers to ensure "holes" in the arrival traffic are created (where necessary) to allow taxiing traffic to cross runways and to allow departures aircraft to take off. [[Crew resource management]] procedures are often used to ensure this communication process is efficient and clear.<br />
<br />
===Clearance Delivery===<br />
Clearance delivery (sometimes known as ''Planner'') is the position that coordinates with the national command center and the en-route center to obtain releases for aircraft. Under normal conditions, this is more or less automatic. When weather or extremely high demand for a certain airport become a factor, there may be ground "stops" (or delays), or re-routes to ensure the system does not get overloaded. The primary responsibility of the clearance delivery position is to ensure that the aircraft have the proper route and release time. This information is also coordinated with the en-route center and the ground controller in order to ensure the aircraft reaches the runway in time to meet the release time provided by the command center.<br />
<br />
===Terminal Area Control===<br />
[[Image:Potomac Consolidated TRACON.jpg|thumb|right|220px|Inside the Potomac TRACON]]<br />
{{main|TRACON}}<br />
Larger airports have a radar control facility that is associated with the control tower. In most countries, this is referred to as ''Terminal Area Control''; in the U.S., it is often still referred to as a TRACON or '''T'''erminal '''R'''adar '''A'''pproach '''CON'''trol facility (sometimes referred to as Approach or Departure control). While every airport varies, terminal controllers usually handle traffic in a 30 to 50 nautical mile (56 to 93 km) radius from the airport and from the surface up to 10,000 feet. The actual airspace boundaries and altitudes assigned to a TRACON are based on factors such as traffic flows and terrain, and vary widely from airport to airport.<br />
<br />
Terminal area controllers are responsible for providing all ATC services within their airspace. Traffic flow is broadly divided into departures, arrivals, overflights, and [[Visual flight rules|VFR]] aircraft. As aircraft move in and out of the terminal airspace, they are handed off to the next appropriate control facility (a control tower, an en-route control facility, or a bordering terminal area control). Terminal is responsible for ensuring that aircraft are at an appropriate altitude when they are handed off, and that aircraft arrive at a slow enough rate to permit safe landing times.<br />
<br />
Not all airports have terminal area control available. In this case, the en-route center will coordinate directly with the tower and provide this type of service where radar coverage permits. Under these circumstances, the separation minimums are usually increased.<br />
<br />
==En-route Control==<br />
[[Image:AirTraffic-8.jpg|thumb|250px|right|Controllers at work at the [[Washington Air Route Traffic Control Center]].]]<br />
{{main|Area Control Center}}<br />
ATC provides services to aircraft in flight between airports as well. The level of service is dependent on the type of flight the aircraft falls under (IFR or VFR), the type of airspace the aircraft is in and the services requested by the pilots.<br />
<br />
En-route Air Traffic Controllers issue clearances and instructions for airborne [[aircraft]], and pilots are required to comply with these instructions. Controllers adhere to a set of separation standards that define the minimum distance allowed between aircraft. These distances vary depending on the equipment and procedures used in providing ATC services.<br />
<br />
Pilots fly under one of two sets of rules for separation; [[Visual flight rules]] (VFR) or [[Instrument flight rules]] (IFR). Air Traffic Controllers have different responsibilities to aircraft operating under the different sets of rules.<br />
<br />
===Visual flight rules (VFR)===<br />
<br />
''For more information see [[Visual Flight Rules]]''<br />
<br />
===Instrument Flight Rules (IFR)===<br />
''For more information, see [[Instrument Flight Rules]]''<br />
<br />
===General characteristics===<br />
En-route air traffic controllers work in facilities called [[Area Control Center|Area Control Centers]], each of which is commonly referred to as a "Center". The United States uses the equivalent term Air Route Traffic Control Center (ARTCC). Each center is responsible for many thousands of square miles of airspace (known as a [[Flight Information Region]]) and for the airports within that airspace. Centers control IFR aircraft from the time the aircraft departs an airport or leaves the terminal area's airspace or until the aircraft approaches the airspace controlled by a terminal area or if the airport does not have terminal area control, until the aircraft lands. Centers may also "pick up" aircraft that are airborne and integrate them into the IFR system. These aircraft must, however, remain VFR until the Center provides a clearance. <br />
<br />
Center controllers are responsible for climbing the aircraft to their requested altitude while, at the same time, ensuring that the aircraft is properly separated from all other aircraft in the immediate area. Additionally, the aircraft must be placed in a flow consistent with the aircraft's route of flight. This effort is complicated by cross traffic, severe weather, special missions that require large airspace allocations, and traffic density. <br />
<br />
As an aircraft reaches the boundary of a Center's control area it is "handed off" to the next Area Control Center. This "hand-off" process is simply a transfer of identification between controllers so that air traffic control services can be provided in a seamless manner. Once the hand-off is complete, the aircraft is given a frequency change and begins talking to the next controller. This process continues until the aircraft is handed off to a terminal area controller ("approach"). <br />
<br />
===Radar Coverage===<br />
Since centers control a large airspace area, they will typically use long range radar that has the capability to see aircraft within 200 nautical miles (370 km) of the radar antenna. They may also use TRACON radar data to control when it provides a better "picture" of the traffic or when it can fill in a portion of the area not covered by the long range radar. <br />
<br />
In the U.S. system, at higher altitudes, over 90% of the U.S. airspace is covered by radar and often by multiple radar systems; however, coverage may be inconsistent at lower altitudes used by unpressurized aircraft due to high terrain or distance from radar facilities. A center may require numerous radar systems to cover the airspace assigned to them, and may also rely on pilot position reports from aircraft flying below the floor of radar coverage. This results in a large amount of data being available to the controller. To address this, automation systems have been designed that consolidate the radar data for the controller. This consolidation includes eliminating duplicate radar returns, ensuring the best radar for each geographical area is providing the data, and displaying the data in an effective format. <br />
<br />
Centers also exercise control over traffic travelling over the world's ocean areas. These areas are also [[Flight Information Region|FIR]]s. Due to the fact that there are no radar systems available for oceanic control, oceanic controllers provide ATC services using "non-radar" procedures. These procedures use aircraft position reports, time, altitude, distance, and speed to ensure separation. Controllers record information on flight progress strips and in specially developed oceanic computer systems as aircraft report positions. This process requires that aircraft be separated by greater distances, which reduces the overall capacity for any given route. <br />
<br />
Some Air Navigation Service Providers (e.g Airservices Australia, Alaska Center, etc.) are implementing Automatic dependent Surveillance - Broadcast (ADS-B) as part of their surveillance capability. This new technology reverses the radar concept. Instead of radar "finding" a target by interrogating the transponder, ADS transmits the aircraft's position several times a second. ADS also has other modes such as the "contract" mode where the aircraft reports a position based on a pre-determined time interval. This is significant because it can be used where it is not possible to locate the infrastructure for a radar system (e.g. over water). Computerised radar displays are now being designed to accept ADS inputs as part of the display. As this technology develops, oceanic ATC procedures will be modernised to take advantage of the benefits this technology provides.<br />
<br />
==Problems==<br />
===Traffic===<br />
The day-to-day problems faced by the air traffic control system are primarily related to the volume of air traffic demand placed on the system, and [[weather]]. Several factors dictate the amount of traffic that can land at an airport in a given amount of time. Each landing aircraft must touch down, slow, and exit the [[runway]] before the next crosses the end of the runway. This process requires between one and up to four minutes for each aircraft. Allowing for departures between arrivals, each runway can thus handle about 30 arrivals per hour. A typical large airport with two arrival runways can thus handle about 60 arrivals per hour in good weather. Problems begin when [[Airline|airlines]] schedule more arrivals into an airport than can be physically handled, or when delays elsewhere cause groups of aircraft that would otherwise be separated in time to arrive simultaneously. Aircraft must then be delayed in the air by [[hold (aviation)|holding]] over specified locations until they may be safely sequenced to the runway. Up until the [[1990s]], holding was a common occurrence at airports. Advances in computers now allow controllers to predict transit times and sequence planes hours in advance. Thus, planes may be delayed before they even take off, or may reduce power in flight and proceed more slowly in order to fit perfectly into a landing sequence without holding.<br />
<br />
===Weather===<br />
Beyond runway capacity issues, weather is a major factor in traffic capacity. [[Rain]] or [[ice]] and [[snow]] on the runway cause landing aircraft to take longer to slow and exit, thus reducing the safe arrival rate and requiring more space between landing aircraft. This, in turn, increases airborne delay for holding aircraft. If more aircraft are scheduled than can be safely and efficiently held in the air, a ground delay program may be established, delaying aircraft on the ground before departure due to conditions at the arrival airport.<br />
<br />
In ACCs, a major weather problem is [[thunderstorms]], which present a variety of hazards to aircraft. Aircraft will deviate around storms, reducing the capacity of the en-route system by requiring more space per aircraft, or causing congestion as many aircraft try to move through a single hole in a line of thunderstorms. Occasionally weather considerations cause delays to aircraft prior to their departure as routes are closed by thunderstorms. <br />
<br />
Much money has been spent on creating [[software]] to streamline this process. However, at some Area Control Centers, air traffic controllers still record data for each flight on strips of paper and personally coordinate their paths. In newer sites, these [[flight progress strip]]s have been replaced by electronic data presented on computer screens. As new equipment is brought in, more and more sites are upgrading away from paper flight strips.<br />
<br />
==Call signs==<br />
A prerequisite to safe air traffic separation is the assignment and use of distinctive [[callsign|call signs]]. By default, the callsign is the registration number (tail number) of the aircraft, such as "N12345" or "CG-ABC".<br />
<br />
For [[scheduled air transport|scheduled flights]], [[military aviation|military flights]], and some other flights, the operators obtain permission to use an [[airline call sign]] followed by a flight number, instead of a registration number. In this arrangement, an identical call sign might well be used for the same scheduled journey each day it is operated, even if the departure time varies a little across different days of the week. The call sign of the return flight often differs only by the final digit, from the outbound flight. Generally, airline flight numbers are even if eastbound, and odd if westbound. In air traffic control terminology, a block of airspace of predetermined size assigned to a radar air traffic controller is called a "[[sector]]". Depending on various factors (traffic density, etc.), a controller may be responsible for one or more sectors at any given time.<br />
<br />
In order to reduce the possibility of two callsigns on one frequency at any time sounding too similar, a number of airlines, particularly in Europe, have started using [[alphanumeric]] callsigns that are not based on flight numbers. For example LH23LG, spoken as [[lufthansa]]-two-three-lima-golf.<br />
<br />
==Technology==<br />
Many technologies are used in air traffic control systems. Primary and secondary [[radar]] are used to enhance a controller's "situational awareness" within his assigned airspace &mdash; all types of aircraft send back primary echoes of varying sizes to controllers' screens as radar energy is bounced off their skins, and [[transponder]]-equipped aircraft reply to secondary radar interrogations by giving an ID (Mode A), an altitude (Mode C) and/or a unique callsign (Mode S). Certain types of weather may also register on the radar screen.<br />
<br />
These inputs, added to data from other radars, are correlated to build the air situation. Some basic processing occurs on the radar tracks, such as calculating ground speed and magnetic headings.<br />
<br />
Other correlations with electronic [[flight plan]]s are also available to controllers on modern [[operational display system]]s.<br />
<br />
Some tools are available in different domains to help the controller further:<br />
* Conflict Alert (CA): a tool that checks possible conflicting trajectories and alerts the controller.<br />
* Minimum Safe Altitude Warning (MSAW): a tool that alerts the controller if an aircraft appears to be flying too low to the ground or will impact terrain based on its current altitude and heading.<br />
* System Coordination (SYSCO) to enable controller to negotiate the release of flights from one sector to another.<br />
* Area Penetration Warning (APW) to inform a controller that a flight will penetrate a restricted area.<br />
* Arrival and Departure manager to help sequence the takeoff and landing of aircraft.<br />
* Converging Runway Display Aid (CRDA) enables Approach controllers to run two final approaches that intersect and make sure that go arounds are minimized<br />
* Final Approach Spacing Tool (FAST) gives aircraft a runway assignment that the Approach Controller will give to the aircraft. FAST can also suggest vectors for downwind and base with the correct timing.<br />
* User Request Evaluation Tool (URET) takes paper strips out of the equation for En Route controllers at ARTCC's. By providing a display that shows all aircraft in or entering the sector. Provides conflict resolution up to 30 minutes in advance.<br />
* Mode S: provides a data downlink of flight parameters via Secondary Surveillance Radars allowing radar processing systems and therefore controllers and to see various data on a flight, including airframe unique id, indicated airspeed and flight director selected level, amongst others.<br />
* CPDLC: Controller Pilot Datalink Communications - allows digital messages to be sent between controllers and pilots, avoiding the need to use radiotelephony. It is especially useful in areas where difficult-to-use [[High Frequency | HF]] radiotelephony was previously used for communication with aircraft, e.g oceans. This is currently in use in various parts of the world including the Atlantic and Pacific oceans.<br />
* [[ADS-B]]: provides a data downlink of various flight parameters to air traffic control systems via Satellite and reception of those data by other aircraft in the vicinity. The most important is the aircraft's latitude, longitude and level: such data can be utilised to create a radar-like display of aircraft for controllers and thus allows a form of pseudo-radar control to be done in areas where the installation of radar is either prohibitive on the grounds of low traffic levels, or techinically not feasible (e.g. oceans). This is currently in use in Australia and parts of the Pacific Ocean<br />
<br />
== Major Accidents ==<br />
Failures in the system have caused delays or even, in rare cases, crashes. On [[July 1]], [[2002]] a [[Tupolev Tu-154]] and [[Boeing 757]] collided above [[Überlingen]] near the boundary between [[Germany|German]] and [[Switzerland|Swiss]]-controlled [[airspace]] when a [[Skyguide]]-employed controller apparently gave instructions to the southbound Tupolev to descend despite an instruction from the on-board automatic [[Traffic Collision Avoidance System]] software to climb. The northbound Boeing, equipped with similar [[avionics]], was already descending due to a software prompt. All passengers and crew died in the resultant collision. Skyguide company publicity had previously acknowledged that the relatively small size of Swiss airspace makes real-time cross-boundary liaison with adjoining authorities particularly important. See ''[[Bashkirian Airlines Flight 2937]]'' for more on this accident. It is worth noting, that currently air traffic controllers have no way of knowing if or when the TCAS system is issuing resolution advisories to pilots. They also do not know what the advisory is telling the pilots. Therefore, pilots are supposed to immediately report TCAS resolution advisories and follow them as soon as possible. Consequently, they should ignore ATC instructions until they have reported to the ground that they are clear of the conflict.<br />
<br />
Other fatal collisions between airliners have occurred over [[India]] and [[Zagreb]] in [[Croatia]]. When a risk of collision is identified by aircrew or ground controllers an "air miss" or "air prox" report can be filed with the air traffic control authority concerned. The worst fatal collision between airliners actually took place on the ground, on [[March 27]], [[1977]], in what is known as the [[Tenerife Disaster]].<br />
<br />
The [[Federal Aviation Administration|FAA]] has spent over USD$3 billion on software, but a fully-automated system is still over the horizon. The UK has recently brought a new control centre into service at [[Swanwick, Hampshire|Swanwick]], in [[Hampshire]], relieving a busy suburban centre at [[West Drayton]] in [[Middlesex]], north of [[London Heathrow Airport]]. Software from [[Lockheed-Martin]] predominates at Swanwick. The Swanwick facility, however, has been troubled by software and communications problems causing delays and occasional shutdowns, paralyzing air traffic in the area.<br />
<br />
==Air Navigation Service Providers (ANSPs)==<br />
In the [[United States]], the [[Federal Aviation Administration]] (FAA) provides this service to all aircraft in the [[National Airspace System]] (NAS). The FAA is responsible for all aspects of U.S. Air Traffic Control including hiring and training controllers, although there are contract towers located in many parts of the country. A contract tower is an Airport Traffic Control Tower (ATCT) that performs the same function as an FAA-run ATCT but is staffed by employees of a private company ([[Martin State Airport]] in [[Maryland]] is an example). In [[Canada]], Air Traffic Control is provided by [[NAV CANADA]], a private, non-share capital corporation that operates Canada's civil air navigation service.<br />
<br />
*[[Austria]] - [http://www.austrocontrol.at Austro Control]<br />
*[[Australia]] - Airservices Australia (State Owned Corporation).<br />
*[[Belgium]] - [http://www.belgocontrol.be/ Belgocontrol]<br />
*[[Canada]] - [[NAV CANADA]]<br />
*[[Denmark]] - [[Naviair]] (Danish ATC)<br />
*[[Europe]] - [[Eurocontrol]] (European Organisation for the Safety of Air Navigation)<br />
*[[France]] - [[DGAC]] (French ATC)<br />
*[[Germany]] - [[Deutsche Flugsicherung]] (German ATC)<br />
*[[Ireland]] - [[IAA]] ([[Irish Aviation Authority]])<br />
*[[Italy]] - [[ENAV]] (Italian ATC)<br />
*[[Mexico]] - [http://www.seneam.gob.mx Servicios a la Navegación en el Espacio Aéreo Mexicano]<br />
*[[Netherlands]] - [[LVNL]] (Dutch ATC)<br />
*[[New Zealand]] - [[Airways Corporation]] (State Owned Enterprise)<br />
*[[Norway]] - [[Avinor]] (State-owned private company)<br />
*[[Spain]] - [[AENA]] (Spanish ATC and Airports)<br />
*[[Sweden]] - [[LFV]] (Swedish ATC)<br />
*[[United Kingdom]] - [[National Air Traffic Services]] (49% State Owned Public-Private Partnership)<br />
*[[United States of America]] - [[Federal Aviation Administration]] (Government Body)<br />
*[[India]] - [[Airports Authority Of India (AAI)]] (Under [[Ministry Of Civil Aviation]] , [[Government Of India]])<br />
*[[South Africa]] - [[Air Traffic and Navigation Services]] , [http://www.atns.co.za]<br />
<br />
==See also==<br />
* [[Air Safety]]<br />
* [[Airspace]]<br />
* [[Australian Air Traffic Control]]<br />
* [[Automatic Dependent Surveillance-Broadcast]] (ADS-B)<br />
* [[Aviation light signals]]<br />
* [[Flight level]] (FL)<br />
* [[Flight planning]]<br />
* [[Flight Progress Strip]]<br />
* [[Free Flight]]<br />
* [[Global Air Traffic Management]]<br />
* [[IFATCA]] (International Federation of ATC Associations)<br />
* [[Professional Air Traffic Controllers Organization]]<br />
* [[Tenerife Disaster]]<br />
* [[Zagreb mid-air collision]]<br />
<br />
==External links==<br />
===Official Air Traffic Control Organisations and Research Institutes===<br />
* [http://www.aena.es/ AENA] - Spanish ATC and Airports ([[Madrid]])<br />
* [http://www.airservicesaustralia.com Airservices Australia]<br />
* [http://www.anacna.it/ ANACNA] - Associazione Nazionale Assistenti e Controllori Navigazione Aerea - Italian Guild of ATS <br />
* [http://www.atcguild.com/ ATC Guild India]<br />
* [http://www.belgocontrol.be/ Belgocontrol - Belgium]<br />
* [http://www.dfs.de/ DFS] - Deutsche Flugsicherung - German ATC ([[Frankfurt]]/Langen)<br />
* [http://www.aviation-civile.gouv.fr/ DGAC] - French ATC ([[Paris]])<br />
* [http://www.dlr.de/ DLR] - Deutsches Zentrum für Luft- und Raumfahrt - German Aerospace Centre ([[Cologne]])<br />
* [http://www.easa.eu.int/ EASA] - European Aviation Safety Agency ([[Cologne]])<br />
* [http://www.egats.org EGATS] - '''Eurocontrol''' Guild of Air Traffic Services<br />
* [http://www.enav.it/ ENAV] - Italian ATC ([[Rome]])<br />
* [http://www.eurocontrol.int Eurocontrol] - European Organisation for the Safety of Air Navigation ([[Brussels]])<br />
* [http://www.eurocontrol.int/eec/ Eurocontrol Experimental Centre] - EEC ([[Paris]]/Brétigny)<br />
* [http://www.eurocontrol.int/muac/ Eurocontrol Maastricht Upper Area Control Center] - MUAC<br />
* [http://www.faa.gov FAA] - Federal Aviation Administration ([[Washington, D.C.]])<br />
* [http://www.faa.gov/atpubs/ATC/ FAA - FAAO 7110.65R (ATC Manual)]<br />
* [http://www.lfv.se/ LFV] - Swedish ATC ([[Stockholm]])<br />
* [http://www.lvnl.nl/ LVNL] - Luchtverkeersleiding Nederland - Dutch ATC ([[Amsterdam]])<br />
* [http://www.natca.org NATCA] - National Air Traffic Controllers Association ([[Washington, D.C.]])<br />
* [http://www.natca.no NATCA] - Norwegian Air Traffic Controllers Association ([[Norway]])<br />
* [http://www.nats.co.uk/ NATS] - National Air Traffic Services of the UK ([[London]])<br />
* [http://www.navcanada.ca/ NAV CANADA] - Canadian Air Navigation Services<br />
* [http://www.naviair.dk/ Naviair] - Danish ATC ([[Copenhagen]])<br />
* [http://www.nlr.nl/ NLR] - Nationaal Lucht- en Ruimtevaartlaboratorium - National Aerospace Lab of the Netherlands ([[Amsterdam]])<br />
<br />
=== Next Generation ATC - Research ===<br />
* [http://www.gisdevelopment.net/technology/gps/ma04082pf.htm Communication Navigation Surveillance / Air Traffic Management ]<br />
* [http://www.intentproject.org/deliverables/INTENT_D3-1_v04_22-05-03_P.pdf Global Air and Ground Collaboration in Air Traffic Separation Assurance]<br />
* [http://www.jpdo.aero Next Generation Air Transportation System Joint Planning and Development Office]<br />
* [http://www.aero-space.nasa.gov NASA Aeronautics Research Mission Directorate]<br />
* [http://atc.avit.und.edu/f1_Home/index.php University of North Dakota's Program for Air Traffic Control]<br />
* J. P. Wangermann and R. F. Stengel "Principled Negotiation Between Intelligent Agents: A Model for Air Traffic Management," ''Artificial Intelligence in Engineering'', Vol. 12, No. 3, July 1998, pp. 177-187<br />
<br />
=== History of Air Traffic Control ===<br />
* [http://www.centennialofflight.gov/essay/Government_Role/Air_traffic_control/POL15.htm U.S. Centennial of Flight Commission - Air Traffic Control]<br />
<br />
===Internet Services===<br />
* [http://www.dxtuners.com Listen to Air Traffic Control radio with live audio]<br />
* [http://www.liveatc.net Live audio Air Traffic Control from over 100 airports worldwide]<br />
* [http://flightaware.com/live/ Map of airborne flights controlled by US ATC]<br />
<br />
[[Category:Air traffic control|*]]<br />
<br />
[[da:Flyvekontroltjeneste]]<br />
[[de:Flugsicherung]]<br />
[[es:Control de tráfico aéreo]]<br />
[[fa:مراقبت پرواز]]<br />
[[fr:Contrôle du trafic aérien]]<br />
[[nl:Luchtverkeersleiding]]<br />
[[ja:航空交通管制]]<br />
[[no:Flykontrolltjeneste]]<br />
[[pt:Controle de tráfego aéreo]]<br />
[[fi:Lennonjohto]]<br />
[[tr:Hava Trafik Kontrol]]<br />
[[sv:Air Traffic Control]]<br />
[[zh:航空运输管制]]</div>Robbbb