Air Traffic and Weather (BAE755B)

Module-5
Call signs, Technology, Air Navigation Service providers and Air traffic service
providers, Privatization ATC regulations Weather Conditions Worldwide,
METAR, Cloud reporting Abbreviation.

Dept. of AE, MITE

Air Traffic and Weather (BAE755B)

Call signs:
Definition & purpose
• A callsign is the spoken identifier used in radio communications to uniquely identify
an aircraft or flight. It is the primary means for controllers and crews to address and
track individual flights.
Types & structure
• Airline (commercial) callsign: usually the airline’s telephony designator (an assigned
word) + flight number.
o e.g., British Airways uses the telephony designator “Speedbird”, so flight
BA149 = “Speedbird One Four Niner”.
• Registration callsign: civil GA / ferry / charter flights often use the aircraft registration
(e.g., “N123AB” → “November One Two Three Alpha Bravo”).
• Special or tactical callsigns: military, medevac, presidential, test flights or state flights
may use special designators (e.g., “Medevac”, “Rescue”, or unique mission callsigns).
• IATA vs ICAO flight numbers: Commercial passengers see IATA numbers (e.g.,
BA149) but ICAO telephony for voice uses the assigned telephony callsign
(Speedbird). Flight plans use ICAO designators (alphanumeric).
Regulation & assignment
• Telephony designators are assigned centrally (ICAO national registries) and regulated
to avoid confusingly similar names. Registrations are national (prefix + unique code).
Operational importance
• Unambiguous radio identification reduces readback errors and prevents wrong
clearances.
• Callsigns may convey priority (e.g., “Medevac”), and controllers use them together
with SSR codes for surveillance identification.

Dept. of AE, MITE

Air Traffic and Weather (BAE755B)

Technology (in ATM):

Definition & scope
• In ATM, technology means the set of Communication, Navigation and Surveillance
(CNS) systems plus automation, data exchange, and decision-support tools that enable
safe, efficient control of air traffic.
Major technology building blocks
1. Communications
o VHF voice for terminal/approach; HF for oceanic; CPDLC (Controller–Pilot
Data Link Communications) for textual clearances on long routes.
o Networked data sharing (SWIM-type) for system-wide information exchange.
2. Navigation
o Conventional: VOR/DME, ILS.
o Modern: GNSS (GPS/GLONASS), RNAV/RNP enabling Performance-Based
Navigation (PBN) and more efficient trajectories.

Dept. of AE, MITE

Air Traffic and Weather (BAE755B)

3. Surveillance
o Primary Radar (PSR): detects targets by reflected radio.
o Secondary Surveillance Radar (SSR): interrogates transponders to get Mode
A/C/S replies (squawk, altitude, and Mode S data).
o ADS-B (Automatic Dependent Surveillance–Broadcast): aircraft broadcast
GPS-derived position—enables more accurate tracking (including in
remote/oceanic areas).
o Multilateration (MLAT): uses time-difference-of-arrival at multiple ground
stations to locate aircraft with transponder responses.
4. ATM Automation & Decision Support
o Tools such as TMA, TBFM, arrival managers, conflict-detection algorithms,
and flow management systems that sequence traffic, compute optimal
trajectories and support controller decisions.
5. Safety Nets
o TCAS/ACAS (onboard collision avoidance), STCA (Short Term Conflict
Alert), MSAW (Minimum Safe Altitude Warning) on the ground.
6. Remote Towers & Digital Tower Tech
o Camera/ sensor suites allow tower services from remote locations, useful for
low-traffic airfields.
7. Aeronautical Information & MET integration
o Automated AIS/AIM data, MET feeds into OIS and trajectory tools.
Operational benefits
• Higher capacity through precise trajectories and sequencing.
• Better surveillance coverage (ADS-B) reduces separation minima in some airspaces.
• Improved predictability (data links, PBN) → fewer delays, fuel savings.
Limitations & challenges
• Dependence on resilient communications and cybersecurity.
• Heterogeneous equipage: not all aircraft have ADS-B/CPDLC/RNP capability.
• Implementation requires regulatory change, training and investment.

Dept. of AE, MITE

Air Traffic and Weather (BAE755B)

Air Navigation Service Providers (ANSPs) & Air Traffic Service

(ATS) Providers:
Definitions
• ANSP (Air Navigation Service Provider): an organization (public, private or hybrid)
that provides air navigation services (communications, navigation, surveillance, and
ATS) within a state or area.
• ATS (Air Traffic Services): the services provided—ATC (aerodrome/tower,
approach/departure, area/en-route control), Flight Information Service (FIS), and
Alerting Service.
Core functions of ANSPs / ATS providers
• Air Traffic Control (ATC): maintain separation, issue clearances, sequence
arrivals/departures.
• Aeronautical Information Service (AIS/AIM): provide aeronautical data/NOTAMs.
• Surveillance & communications provision: operate radars, data links, voice nets.
• Safety & contingency planning: manage emergency procedures and resilience.
• Flow management & coordination: implement GDPs, AFPs, reroutes, liaise with
airline ops.
Organizational structure / units
• Aerodrome control (tower): ground movement & runway operations.
• Terminal (approach/departure): managing inbound/outbound within terminal control
area.
• Area Control Center (ACC) / En-route centers: manage en-route traffic in FIRs.
• Flow Management Units / Network Managers: coordinate capacity and demand
regionally.
Regulation & oversight
• ANSPs operate under national civil aviation authority safety oversight (CAA) and
within ICAO SARPs. Economic regulation may be imposed for charges and
performance (through independent regulators).
Operational interactions
• ANSPs liaise with airports, airlines and meteorological services to implement CDM,
OIS, and ATFM measures.
.

Dept. of AE, MITE

Air Traffic and Weather (BAE755B)

Privatization of ATC — models & regulations:

What is meant by privatization?
• Shifting air navigation services from direct government administration to corporate,
private or corporatized entities that operate under regulatory oversight. Models vary
from state-owned corporations to fully privatized or public–private partnerships.
Common organizational models
• Government department model: ANS run as a government agency (traditional).
• Corporatized ANSP: state-owned company with corporate governance (e.g., many
European ANSPs).
• Non-profit private model: user-funded non-government entity (e.g., NAV CANADA).
• Full privatization / PPP: private stakeholder investment with contractual service
obligations.
Regulatory framework & safeguards
• Safety oversight remains the remit of the national aviation safety regulator (e.g., CAA)
regardless of ownership.
• Economic regulation often enforced by independent regulators to control charges,
monopoly power and service performance (targets, KPIs).
• International obligations: ANSPs must comply with ICAO standards; cross-border
coordination required.
Pros of privatization / corporatization
• Increased operational flexibility and faster modernization (investment & procurement).
• Potentially more efficient cost recovery and customer-focused services.
• Ability to borrow/raise capital, innovate (remote towers, automation).
Cons & risks
• Accountability & national control concerns (strategic sovereignty).
• Risk of prioritizing profit over service coverage (smaller airports).
• Transition issues: workforce restructuring, industrial relations, and continuity of safety
culture.
Operational & social impacts
• Tariff/regulatory changes can affect airline costs.
• Staff terms and training may change—impacts on morale and retention.

Dept. of AE, MITE

Air Traffic and Weather (BAE755B)

Weather Conditions Worldwide (and aviation impacts):

Overview
• Weather patterns vary by scale (global → synoptic → mesoscale → local) and have
direct operational effects on aviation (safety, capacity, routing).
Key global phenomena affecting aviation
• Jet stream: strong upper-level winds cause tailwinds/headwinds and clear-air
turbulence (CAT).
• Mid-latitude frontal systems & cyclones: generate widespread low clouds,
precipitation, wind and icing.
• Tropical systems (cyclones/hurricanes/typhoons): cause massive airspace closures,
rerouting and airport shutdowns.
• Monsoon regimes: prolonged heavy rainfall and convective activity affecting wide
regions seasonally.
• ITCZ & deep convection in tropics: frequent thunderstorm activity → convective
avoidance, SWAP activations.
• Mountain meteorology: orographic turbulence, downslope winds, mountain waves
and lee-side rotors.
• Polar conditions: extreme cold, airframe icing, limited diversion options, polar route
communications (HF).
• Volcanic ash: causes engine damage; leads to large airspace closures and global
rerouting.
Aviation operational implications
• Capacity reductions: low ceilings/visibility and convective activity reduce airport
throughput → GDPs / ground stops.
• Rerouting & fuel planning: long detours to avoid storms or ash require extra fuel and
dispatch decisions.
• Safety considerations: icing, wind shear, turbulence and lightning demands
operational mitigations and crew briefings.
• Surveillance & comms impacts: HF outages on oceanic routes, radome icing affecting
surveillance, or ash affecting instruments.
Forecasting & decision making
• Use of MET products (SIGMETs, TAFs, nowcasts), OIS integration and CDM to
implement flow measures.

Dept. of AE, MITE

Air Traffic and Weather (BAE755B)

METAR — format, elements, examples and interpretation:

What is a METAR?
• A METAR is the routine aviation surface weather observation issued typically every
hour (or half-hour at some stations) for pilots, dispatchers and ATC. A special report is
called SPECI when conditions change significantly between METARs.
General structure (common elements, in order)
1. Type: METAR or SPECI.
2. Station Identifier: 4-letter ICAO code (e.g., EGLL, VABB).
3. Date/Time group: DDHHMMZ (day, hour, minute, Zulu).
4. Modifier: AUTO (automated) or COR (correction).
5. Wind: dddffKT (direction in degrees true / speed in knots); gusts as Ggg. Variability
(e.g., 180V240) or VRB for variable.
6. Visibility: reported in meters (ICAO) or statute miles (some regions like U.S.). RVR
(Runway Visual Range) if applicable.
7. Present Weather: coded groups (intensity + descriptor + precipitation/phenomena,
e.g., +RA = heavy rain, -SN = light snow, TSRA = thunderstorm with rain).
8. Sky condition / cloud layers: amount + cloud type + base (e.g., FEW020 SCT045
BKN100 OVC250) and CB/TCU if present.
9. Temperature / Dew point: TT/TD in °C (negative indicated with M, e.g., M02 = -
2°C).
10. Altimeter / QNH: e.g., Q1013 (hPa) or A2992 (inHg in the U.S.).
11. Remarks (RMK): additional info: runway states, sea level pressure, precipitation
totals, recent weather (RE), maintenance notes, etc.
12. Trend groups: NOSIG, TEMPO, FM (used for short-term expected changes,
sometimes in METAR or in TAFs).
Common present-weather codes (examples)
• Intensity/Proximity: - (light), no sign = moderate, + (heavy), VC (in the vicinity).
• Weather types: RA (rain), SN (snow), DZ (drizzle), FG (fog), BR (mist), HZ (haze), TS
(thunderstorm), GR (hail), SG (snow grains), SS (sandstorm), DS (duststorm).
• Example group: -SHRA = light rain showers.
Sample METAR and decoding
• Example:
METAR VABB 041700Z 21012KT 9999 FEW020 SCT035 28/18 Q1008 NOSIG
Decode: METAR for VABB at 04 day 17:00Z. Wind 210°/12 kt. Visibility 10 km or

Dept. of AE, MITE

Air Traffic and Weather (BAE755B)

more (9999). Few clouds at 2000 ft, scattered at 3500 ft. Temperature 28°C, dewpoint
18°C. QNH 1008 hPa. No significant changes expected.
SPECI & AUTO
• SPECI: issued when significant changes occur between routine METARs (sudden
storms, visibility drop, wind shear).
• AUTO: automated station; RMK may indicate AO1/AO2 for precipitation sensor
capability.
Operational importance
• METAR is the real-time snapshot used for ATC acceptance rates, dispatch decisions,
runway selection, and de-icing planning.

Cloud reporting abbreviations (and operational significance):

Why cloud reporting matters
• Cloud amount and base determine visual meteorological conditions (VMC) vs.
instrument meteorological conditions (IMC), affect approach minima, minima for
visual circuits and determine if an airport is usable under VFR.
Standard abbreviations & meanings
• SKC — Sky Clear (no clouds) (used often in US METARs)
• CLR — Clear (no clouds detected below 12,000 ft; automated US usage)
• NSC / NCD — No Significant Cloud / No Cloud Detected (used in some reporting
regimes)
• FEW — Few clouds — 1–2 oktas (1/8–2/8 sky coverage)
• SCT — Scattered — 3–4 oktas (3/8–4/8)
• BKN — Broken — 5–7 oktas (5/8–7/8) → often considered a ceiling if low
• OVC — Overcast — 8 oktas (8/8) → solid cloud layer; definite ceiling
• CB — Cumulonimbus (thunderstorm cloud) — always significant (vertical
development; severe turbulence, icing, lightning)
• TCU — Towering Cumulus (significant vertical growth; may precede CB)
• AC / AS / NS / ST — Altocumulus, Altostratus, Nimbostratus, Stratus (layer/cloud-
type indicators used in detailed reporting)
Oktas & approximate % cover
• FEW = 1–2 oktas (~12.5–25%); SCT = 3–4 oktas (~37.5–50%); BKN = 5–7 oktas
(~62.5–87.5%); OVC = 8/8 (100%).

Dept. of AE, MITE

Air Traffic and Weather (BAE755B)

Ceiling definition (operational)

• The ceiling is conventionally the height of the lowest cloud layer reported as broken
(BKN) or overcast (OVC) — this is critical for approach minima and VFR flight. (Note:
specific regulatory ceilings for classification may vary by authority—always refer to
national regulations for exact thresholds.)
Reporting format in METAR
• Cloud groups are shown as AMMBBB where A is amount (FEW/SCT/BKN/OVC),
MM is cloud type (e.g., CB), BBB is base in hundreds of feet (e.g., BKN020 = broken
at 2000 ft).
Operational significance
• BKN/OVC at low levels → IMC, require instrument approaches, possibly reduced
airport capacity.
• CB / TCU present → avoid convective activity; triggers SWAP, reroutes, and possibly
ground stops.
• High scattered clouds (SCT/FEW) → mostly VMC; less effect on operations unless
bases are near minima.

Dept. of AE, MITE