Learn what ATC radar screens show, how controllers identify, separate and sequence aircraft, and what happens when surveillance data fails.
Air traffic controllers use radar screens to identify aircraft, monitor their position, altitude and movement, predict conflicts, and issue heading, climb, descent and speed instructions to keep traffic separated and sequenced. In real-world aviation, the display usually combines radar, transponder, ADS-B and flight-plan data rather than raw echoes alone.
What does an ATC radar screen show?
An ATC surveillance display presents processed aircraft tracks over a map of the controller’s airspace. Controllers often call it a radar scope, although many modern systems fuse several surveillance sources:
- Primary radar detects reflected radio energy and provides a position without identifying the aircraft or reporting its altitude.
- Secondary surveillance radar interrogates an aircraft’s transponder, which can return a four-digit code, pressure-altitude data and, with suitable equipment, additional identity information.
- ADS-B broadcasts position, velocity and identification data generated aboard the aircraft where the service is approved and available.
- Flight-plan processing associates the surveillance track with a call sign, route, aircraft type and clearance information. This is stored data rather than something measured by radar.
| Display item | What the controller learns | Important limitation |
|---|---|---|
| Track symbol | The processed position of an aircraft | It may be fused from several sensors rather than representing one live radar echo. |
| Data block | Call sign or code, altitude, ground speed and other facility-dependent information | Ground speed is not indicated airspeed, and transponder altitude is not radar-measured height above terrain. |
| History trail or vector | Recent movement or projected movement | A projected line normally assumes the aircraft continues on its existing track and speed; it does not guarantee where it will turn. |
| Map layers | Runways, fixes, routes, boundaries and restricted areas | The available layers and level of detail vary between facilities and controller positions. |
| Safety alert | A possible conflict, low-altitude risk or other system-defined hazard | Alerts assist the controller but do not replace the required visual scan and separation procedures. |
The phrase radar contact generally means that ATC has identified the aircraft on its surveillance display using an approved method. It does not mean the controller knows every cockpit setting or can see the aeroplane continuously without sensor delay.
How do controllers use radar to separate aircraft?
Controllers repeatedly identify, scan, predict, instruct and verify rather than reacting only when two symbols become close together.
- Identify the aircraft. A departing aircraft’s assigned transponder code may correlate automatically with its flight plan. If necessary, ATC can request IDENT, observe a specified code, compare a reported position or use another approved identification method. Pilots should press IDENT only when instructed.
- Build the traffic picture. The controller scans aircraft positions, altitude trends, ground tracks and speeds while accounting for sector boundaries, wake turbulence, weather, restricted airspace and differing aircraft performance.
- Predict conflicts. Track history, speed vectors and conflict tools reveal where aircraft may lose the prescribed horizontal or vertical separation. Exact minima depend on the airspace, surveillance system and controlling procedure; there is no single worldwide radar-separation figure.
- Choose a solution. The controller may issue a heading, climb, descent or speed restriction. Arrivals can be spaced by speed control or longer radar vectors, while departures may need heading or altitude restrictions until clear of other traffic. Our cockpit-side explanation of interpreting ATC headings and altitude instructions covers what the pilot must do after receiving these commands.
- Check the response. ATC listens to the readback and watches the track to confirm that the aircraft turns, climbs or descends as expected. A wrong readback, delayed turn or unexpected altitude trend must be challenged rather than assumed correct.
- Coordinate the hand-off. Before an aircraft leaves the sector, its track and flight data are transferred to the next controller. Our explanation of how hand-offs fit into the full clearance-to-landing flow places this radar work in the wider ATC process.
A mistake we see often in simulation is treating a speed vector as the aircraft’s cleared route. It only projects the present motion. The flight may turn at a programmed waypoint, begin a procedure or respond to a new clearance before reaching the end of that line.
Does the radar screen control the aircraft automatically?
No. An air traffic controller uses the display to make decisions, then sends instructions by radio or, on equipped routes, by data link; the pilot or aircraft automation carries them out.
Depending on the facility, supporting tools can include short-term conflict alerts, minimum-safe-altitude warnings and route-based conflict probes. These tools can produce nuisance alerts or miss situations outside their design criteria, so an alert is neither a clearance nor a substitute for controller judgement.
TCAS is a separate airborne collision-avoidance system. It shows nearby transponder traffic to the flight crew and can issue resolution advisories, but it is not a miniature copy of the controller’s display. See our comparison of cockpit TCAS indications and the controller’s traffic picture for the operational differences.
What happens if an aircraft disappears from ATC radar?
A missing or unreliable radar target triggers identification checks and fallback procedures rather than blind reliance on an extrapolated symbol.
- Incorrect or missing transponder data: the controller may ask the pilot to verify the assigned code or transponder operation. A duplicate or mistyped code can prevent correct flight-plan association.
- Unverified altitude: ATC may compare the displayed value with the altitude reported by the pilot. Suspect altitude information cannot be used as though it were accurate.
- Coasting track: some systems briefly extrapolate a target after updates stop. A coast indication is a predicted position, not fresh surveillance data.
- Coverage gap or equipment outage: controllers can use another sensor, pilot position reports or procedural separation. They may increase spacing, restrict traffic or suspend an affected service when the required surveillance cannot be provided.
Radar loss and radio failure are separate events. A controller may still speak to an aircraft that is no longer displayed, or continue tracking an aircraft whose crew cannot reply.
Radar displays differ by ATC position
The display is tailored to the airspace and task rather than being identical at every controller position.
- Tower controllers primarily use the view from the tower, supported at some airports by surface-movement surveillance and traffic displays.
- Approach and departure controllers use detailed terminal displays for aircraft climbing, descending and turning rapidly near airports.
- En-route controllers monitor larger sectors, higher-altitude routes and traffic crossing sector boundaries.
- Oceanic and remote controllers may rely on ADS-C, ADS-B or position reports instead of conventional radar, with procedures and update intervals suited to that coverage.
For simmers, an ARTS-style radar-control simulation can demonstrate scanning, identification, vectors, altitude changes and arrival sequencing. Its older terminal-radar presentation is useful for learning the fundamentals, but it should not be treated as a replica of every modern ATC system or local procedure.