Learn how air traffic control automation fuses radar, ADS-B and flight-plan data, predicts conflicts, supports hand-offs and handles system failures.
In real-world aviation, air traffic control automation combines flight plans, radar, ADS-B and other surveillance data to build a live traffic picture, predict aircraft trajectories, flag conflicts and coordinate hand-offs. It advises and organises controllers; it does not normally issue tactical clearances or replace the controller responsible for maintaining separation.
In our Aviation & Real-World Flying coverage, we use “automation” to mean a chain of linked systems rather than one computer. It includes surveillance processing, flight-data processing, trajectory prediction, safety alerts, electronic coordination and traffic-flow tools. For the wider operational context, see our overview of how surveillance, clearances and sector hand-offs fit together.
What information does ATC automation use?
ATC automation combines planned information with observed aircraft movement, although the available sources vary by facility and airspace.
- Flight-plan data: call sign, aircraft type, equipment, route, requested level, departure and destination airports, and estimated times.
- Surveillance reports: primary radar returns, secondary radar, Mode S, ADS-B and multilateration where those systems are available.
- Controller inputs: cleared altitude or flight level, route amendments, runway assignment and coordination status.
- Operational data: active sectors, runway configuration, restricted airspace, weather and wind information where integrated.
The system tries to correlate each surveillance track with the correct flight plan. It may use the assigned transponder code, Mode S identity, aircraft address, position and expected route. A wrong code, mistyped transponder flight ID, duplicate assignment or stale flight plan can leave a target uncorrelated or associate it with the wrong record. Our explanation of how squawk codes provide identification and altitude information covers that link in more detail.
How does ATC automation build the traffic picture?
The automation chain turns reports from separate sources into tracks, labels, predictions and coordination data that controllers can use.
- Process the flight plan. The flight-data system checks the submitted plan, assigns it to the relevant sectors and prepares electronic flight information for each controller position.
- Create a surveillance track. Tracking software filters successive sensor reports to estimate the aircraft’s position, direction, speed and altitude. Where sensors overlap, the system may fuse their reports into one track.
- Correlate track and flight plan. The software matches the observed target with the expected aircraft, then displays a label containing details such as call sign, altitude, speed and cleared level.
- Predict the trajectory. The system projects where the aircraft is likely to go using its known route or clearance, present motion, aircraft-performance assumptions and sometimes wind data.
- Coordinate between sectors. Electronic messages pass flight details, estimates and hand-off requests to the next controller. Acceptance updates the track’s status, but transfer of responsibility still follows the applicable ATC procedure.
- Sequence and meter traffic. Where fitted, arrival, departure and flow-management tools suggest times, spacing or runway sequences to prevent excessive demand at a sector or airport.
A predicted trajectory is not necessarily identical to the route programmed in the aircraft’s flight-management system. If a controller gives a direct routing or altitude change by voice but the ground record is not updated, the prediction may continue along the old route and generate an unnecessary warning.
How does automated conflict detection work?
Conflict-detection tools compare predicted aircraft positions against configured separation and safety thresholds.
| Tool | Information used | Purpose |
|---|---|---|
| Trajectory or medium-term conflict probe | Flight plans, clearances and predicted paths | Warns of a possible planning conflict early enough for the controller to change a route, level or sequence. |
| Short-term conflict alert | Recent surveillance positions, levels and movement | Warns the controller that two tracks are developing into an urgent proximity conflict. |
| TCAS or ACAS | Surveillance performed aboard the aircraft | Provides pilots with traffic information and, when required, a resolution advisory. It is independent of the ground conflict probe. |
An alert does not prove that separation has already been lost. It can be triggered by uncertainty, an unrecorded clearance, rapid manoeuvring or a prediction that no longer reflects the aircraft’s intent. Controllers verify the actual traffic picture rather than obeying an alert blindly.
Other ground safety nets can warn about low altitude, unsafe approach paths, restricted-airspace penetration or runway conflicts. Their names and capabilities differ between installations. For the airborne side, our cockpit guide to traffic displays, transponders and TCAS explains why TCAS is not simply an extension of the controller’s radar screen.
Does ATC automation issue clearances?
Usually, no: the controller decides the tactical clearance, communicates it and monitors the result.
Automation can prepare or transmit authorised standard messages, including some departure, frequency-change and data-link clearances. It may also recommend sequencing, headings, levels or conflict solutions. These functions support the controller’s judgement; they do not give the ground computer unrestricted authority to fly the aircraft.
This distinction matters during a hand-off. The system can transfer flight data and request acceptance from the next sector, but the pilot changes frequency, heading or altitude only after receiving the appropriate clearance or following a published procedure.
Is ATC automation the same everywhere?
No; tower, approach, en-route and oceanic facilities use different combinations of automation because their surveillance coverage, traffic and time scales differ.
- Airport towers may use electronic flight strips, departure lists, surface surveillance and runway-incursion alerts.
- Approach control relies heavily on frequent surveillance updates, compact data labels, arrival sequencing and short-term safety alerts.
- En-route centres place more emphasis on trajectory prediction, sector coordination, flow management and medium-term conflict detection.
- Oceanic control may have limited terrestrial radar coverage, so automation uses flight plans, position reports, ADS-C and CPDLC alongside procedural separation.
ADS-C is not the same as ADS-B: ADS-C sends reports under a reporting contract with the ground system, while ADS-B broadcasts aircraft data. Our account of CPDLC, ADS-C and procedural separation over oceans explains how automation works when conventional radar is unavailable.
What happens if ATC automation fails?
Controllers move to redundant equipment or degraded operating procedures, then reduce traffic to match the information and coordination tools still available.
- Loss of one surveillance source: another sensor may continue feeding the display. If coverage or identification becomes inadequate, controllers use procedural separation, larger spacing or traffic restrictions.
- Flight-data or network failure: facilities can use backup systems, local flight information, paper strips or voice coordination, depending on their equipment and procedures.
- Incorrect track correlation: the controller verifies the call sign, position, altitude and transponder information, then removes or corrects the suspect association.
- Unreliable trajectory prediction: the flight record is updated to reflect the clearance, or the controller treats the affected advisory as invalid while continuing to monitor the observed tracks.
An automation outage normally reduces capacity before it creates an immediate safety problem. Departures may be delayed, aircraft held or rerouted, and sectors prevented from accepting more traffic. Separation requirements remain in force; what changes is the method and workload required to maintain them.