Defining an airport’s Air Traffic Services (ATS) requirement starts with the scope: which services are needed, where each unit’s responsibility begins and ends, and how it coordinates with the wider operation. Distinguishing ATS from Air Traffic Control (ATC) helps operators specify that scope without overlooking related functions.
Air traffic control is part of air traffic services, not another name for the entire field. ATS also includes flight information and alerting services. Understanding that distinction helps airport operators and aviation authorities ask for the right capability rather than assume that every function sits inside one control service.
What air traffic control covers
Air traffic control services address aircraft movements within their assigned operational responsibilities. Aerodrome, approach and area control have different scopes: the requirement for one should not be treated as an automatic requirement for all three.
For a prospective service arrangement, the useful question is not simply whether a provider offers ATC. It is which operational functions are included, where responsibility begins and ends, and how the handovers to other units will work. The answer needs to match the aerodrome and airspace concerned.
Why the wider ATS distinction matters
Flight information and alerting remain important when discussing the broader service requirement. They should not disappear from a brief merely because the project is described informally as an ATC contract. Equally, the fact that functions sit under the same broad category does not mean every unit delivers them in the same way.
Keep the operational service separate from its supporting capabilities. Engineering, training and aeronautical information can be essential interfaces without being interchangeable with control duties. A clear brief names those dependencies and identifies who is responsible for each one.
A practical starting brief for an airport operator
Before requesting a proposal, assemble a concise description of the operation. Identify the service area, the present arrangements, the change being considered and the organizations that must participate. State whether the need concerns a new operation, a transition or a review of existing provision.
Then work through four questions:
- Which aerodrome, approach, area, flight information and alerting responsibilities are relevant to the proposed scope?
- Which responsibilities remain with the airport, authority or neighboring service units?
- What supporting systems, training and information interfaces must be coordinated?
- What evidence will demonstrate that the agreed service is ready for its intended operational role?
These questions form a discussion brief, not a substitute for the applicable regulatory assessment or operational approvals. Their purpose is to prevent a broad label from hiding an important gap in responsibility.
Discussing the requirement with GANS
GANS provides Air Traffic Services alongside engineering capabilities, training and consultancy. Its published ATS scope includes aerodrome, approach and area control, flight information services and Air Traffic Flow Management. That combination allows a service discussion to consider operational delivery and the supporting requirements together.
Explore GANS Air Traffic Services. For a service discussion, prepare the location, existing arrangements and intended change. See GANS office contact details. This gives GANS the context to discuss the relevant control services, supporting engineering and training needs, and coordination with other units. The discussion can then focus on a service scope matched to the airport’s operation rather than a general request for ATC support.