Air traffic control Study Guide

📖 Core Concepts Air Traffic Control (ATC) – Ground‑based service that directs aircraft on the ground and in controlled airspace to prevent collisions, organize traffic flow, and support pilots. Pilot‑in‑Command Authority – Pilots must obey ATC, but retain final safety authority and may deviate in emergencies. Airspace Classes & Services – Controllers issue mandatory instructions in controlled airspace; in non‑controlled airspace they may give non‑binding advisories. Separation Minimums – Minimum distance (horizontal/vertical) that must be kept between aircraft; tighter in terminal areas than en‑route sectors. Surveillance Types – Primary radar, secondary radar, Surface Movement Radar, ADS‑B (broadcast) and ADS‑C (contract) provide aircraft position data. Decision‑Support Tools – Flight Data Processing Systems, Short‑Term Conflict Alert (STCA), Medium‑Term Conflict Detection (MTCD) help predict and resolve conflicts. Modernisation Initiatives – SESAR (Europe) and NextGen (U.S.) shift toward satellite‑based navigation, digital data links, and integrated displays (IIDS, EXCDS). --- 📌 Must Remember Primary ATC purpose: collision avoidance, traffic flow efficiency, pilot support. Pilot authority: obey ATC unless safety demands a deviation (emergency). Radar ranges: En‑route up to 240 nm; Airport surveillance up to 52 nm (below 25 000 ft); Surface radar ≤ 2 nm. ADS‑B vs. ADS‑C: ADS‑B continuously broadcasts position; ADS‑C sends at set intervals or on request, useful where radar is absent (e.g., over water). STCA time window: detects conflicts 35 s – 3 min ahead. Call sign structure: Airline designator (2‑3 letters) + flight number (e.g., AAL872). Non‑airline flights use registration tail number; spoken form uses last three characters with NATO phonetics. FAA Order 7110.65 – Governs all U.S. ATC procedures. SESAR/NextGen goals: increase capacity, cut fuel use (5‑10 % potential), improve safety and environmental performance. --- 🔄 Key Processes Flight‑Plan Processing Flight plan entered → Flight Data Processing System → distributed to clearance delivery, tower, TRACON, Area Control. Separation Enforcement Radar/ADS data → conflict detection (STCA/MTCD) → controller issues altitude/heading change → pilot acknowledges with full call sign. Tower Operations (Ground → Air) Clearance Delivery: Issue route clearance before taxi. Ground Control: Assign taxi routes, monitor with surface radar. Tower (Air) Control: Authorize runway entry, take‑off, landing. Conflict Detection Workflow Input: radar/ADS‑B/C data → MTCD predicts intersecting trajectories minutes ahead → controller selects resolution (altitude, heading) → automated tool may suggest optimal maneuver. Emergency Deviation Pilot declares emergency → may deviate from ATC instruction → informs controller; controller re‑sequencing of affected traffic. --- 🔍 Key Comparisons Tower Control vs. Ground Control – Tower: active runway surface, take‑off/landing; Ground: taxiways, ramps, surface movement. ADS‑B vs. ADS‑C – ADS‑B: continuous broadcast, independent of controller request; ADS‑C: scheduled or on‑demand reports, useful where radar missing. Mandatory Frequency (MF) Airport vs. Controlled Tower Airport – MF: pilots self‑announce on a common frequency, no clearances; Tower: ATC issues clearances and separation. Public ATC (e.g., FAA) vs. Private Model (NAV CANADA) – Public: government funded, regulated by orders like 7110.65; Private non‑profit: user‑fee funded, aims for cost recovery and efficiency. --- ⚠️ Common Misunderstandings “Pilot must always follow ATC” – True except when safety requires an emergency deviation. “ADS‑B replaces radar entirely” – ADS‑B complements radar; coverage gaps still exist (e.g., low‑altitude terrain masking). “All ATC communications are mandatory” – In non‑controlled airspace, many advisories are optional. “Call sign = registration” – Only when no airline designator exists; otherwise airline flight number is used. --- 🧠 Mental Models / Intuition “Three‑layer onion” – Visualize ATC as layers: Surface (Ground), Terminal (Tower/TRACON), En‑route (Area Control). Each layer has its own radar range and separation rules. “Conflict horizon” – Think of a moving bubble ahead of each aircraft; STCA watches the bubble 35 s–3 min out, MTCD watches several minutes out. “Pilot‑controller handshake” – Pilot says call sign → receives instruction → repeats back exact call sign + instruction → confirmation. This loop ensures both parties are synchronized. --- 🚩 Exceptions & Edge Cases Weather‑induced deviations – Thunderstorms, low visibility may force reroutes, holds, or alternate airports, overriding normal separation minima. Remote/Virtual Towers – Controllers operate from off‑site locations; surveillance still required but physical tower absent. ADS‑C contract mode – Used over oceans where radar isn’t available; aircraft report only when requested. Mandatory Frequency Airports – No ATC clearance; pilots must self‑coordinate but still follow standard phraseology. --- 📍 When to Use Which Choose Radar vs. ADS‑B – Use radar when within 240 nm en‑route coverage or below 25 000 ft; rely on ADS‑B for high‑altitude, satellite‑visible aircraft, especially in low‑radar regions. Select STCA vs. MTCD – STCA for immediate (seconds‑to‑minutes) conflict alerts during approach/landing; MTCD for proactive conflict resolution minutes ahead on en‑route sectors. Tower vs. Ground Control instructions – Use Tower for runway‑related clearances (take‑off, landing); Ground for taxi routes and surface movements. Public vs. Private ATC model – Public model when regulatory uniformity is critical; private (e.g., NAV CANADA) when cost recovery and user‑fee funding are prioritized. --- 👀 Patterns to Recognize “Separation tighter → higher traffic density” – Terminal areas always have smaller minimums; expect more frequent vectoring. “Weather → delay → reroute → increased fuel burn” – Spot weather mentions in questions; anticipate downstream effects on ATC actions. “Call sign repetition” – Exam items often test correct read‑back; look for mismatched call sign or missing phonetic letters. “ADS‑B presence” – In modern scenarios, expect continuous position updates; missing ADS‑B often signals remote or oceanic flight. --- 🗂️ Exam Traps Choosing “mandatory” vs. “advisory” – A question may describe an MF airport; the wrong answer is to treat it like a tower‑controlled field. Confusing radar ranges – Some may state “airport radar covers 240 nm”; the correct range is 52 nm (below 25 000 ft). Misidentifying pilot authority – Selecting “pilots can never disobey ATC” ignores the emergency exception. Call sign mix‑up – Selecting registration instead of airline flight number for a commercial flight is incorrect. Assuming ADS‑B eliminates all conflicts – Conflict detection still needed; ADS‑B provides data but does not resolve separations automatically. ---