The Umbrex Travel, Transportation & Logistics Industry Practice has prepared this guide to terminology, acronyms, shorthand, and insider language to help a newcomer to the airports & air navigation service providers (ANSPs) sector get up to speed rapidly.
Aerodrome and Airspace Structure
Aerodrome and airport
Aerodrome is the regulatory term for a defined area used wholly or partly for aircraft arrival, departure, and surface movement. It includes the operational surfaces and associated installations. Airport usually implies an aerodrome with passenger, cargo, commercial, or public-service facilities, although legal usage varies by country.
Practitioners use aerodrome when discussing certification, ICAO standards, safeguarding, or technical design. They use airport more often for the operating company, terminal business, or customer proposition. An aerodrome certificate therefore covers rather more than the terminal with the expensive coffee.
Airside, landside, and security restricted area
Airside is the portion of the airport subject to controlled access and supporting aircraft operations. Landside is the publicly accessible side of the boundary. A security restricted area, or SRA in many jurisdictions, is a legally defined zone with additional screening and access-control requirements.
These are not merely architectural labels. Moving a facility, vehicle route, staff entrance, or baggage process across one of these boundaries can change screening obligations, escort rules, pass requirements, and construction procedures. Airside does not always mean the same thing as SRA, particularly at cargo, maintenance, and general aviation facilities.
Movement area and manoeuvring area
Under ICAO terminology, the movement area comprises the manoeuvring area plus aprons. The manoeuvring area includes runways and taxiways used for aircraft takeoff, landing, and taxiing, but excludes aprons.
The distinction determines who controls what and which procedures apply. Air traffic control normally controls the manoeuvring area. Apron control may sit with the airport operator, an airline, a ground handler, or an apron management service. Hearing that an incident occurred on the movement area does not tell you whether it happened under tower control.
FIR and UIR
A Flight Information Region (FIR) is airspace within which a state or delegated provider supplies flight information and alerting services. An Upper Information Region (UIR) performs the corresponding function in upper airspace where a state has established one.
An FIR is not necessarily identical to national territory, and it is not all necessarily controlled airspace. Oceanic FIR boundaries, delegated service arrangements, and disputed sovereign boundaries can make maps politically interesting and operationally untidy. ANSP traffic volumes and route-charge exposure are often analyzed by FIR rather than by airport market.
CTR and TMA
A Control Zone (CTR) is controlled airspace extending upward from the surface around one or more aerodromes. A Terminal Control Area or Terminal Manoeuvring Area (TMA) is controlled airspace established where routes converge around major airports, usually above lower airspace rather than directly from the surface.
The CTR protects local arrivals, departures, and circuit traffic. The TMA organizes the larger arrival and departure flows feeding several runways or airports. Airspace design discussions often concern where the CTR ends, how TMA sectors are shaped, and whether adjacent airports compete for the same altitude or route structure.
ICAO airspace classes
ICAO airspace Classes A through G define which flight rules are permitted, what air traffic services are provided, and which traffic receives separation. States implement the classes differently, so a class letter must be read together with the applicable national rules.
Class A normally permits instrument flight rules traffic only, while Classes F and G provide progressively less comprehensive control. The important practical question is not simply whether airspace is controlled. It is which aircraft are separated from which others, what clearance is required, and what surveillance or communication capability supports the service.
Runway and Apron Infrastructure
Runway designator
A runway number represents its magnetic direction rounded to the nearest ten degrees, with the final zero omitted. A runway aligned approximately 274 degrees is therefore designated Runway 27. Reciprocal ends differ by 18, such as 09 and 27. Parallel runways receive L, C, or R suffixes.
Designators can change as magnetic variation moves the rounded bearing across a threshold. Renumbering is not just new paint. It affects charts, signs, navigation databases, procedures, software, training, and every local habit built around the old number.
Aerodrome Reference Code
The ICAO Aerodrome Reference Code combines a number related to aircraft reference field length with a letter related principally to wingspan. A Code 4F aerodrome is designed around a substantially larger aircraft geometry than a Code 3C facility.
The code guides dimensions and separations for runways, taxiways, and stands. It does not mean every Code 4F runway has sufficient pavement strength, terminal capacity, or rescue capability for every Code F aircraft. The FAA uses a different Airport Reference Code system, so an unqualified reference to “the code” deserves a geographic follow-up question.
Declared distances
Declared distances state how much runway-related length is available for particular aircraft performance calculations:
- TORA, Takeoff Run Available: length available for the ground run.
- TODA, Takeoff Distance Available: TORA plus any declared clearway.
- ASDA, Accelerate-Stop Distance Available: TORA plus any declared stopway.
- LDA, Landing Distance Available: length declared available for landing.
These values can differ at each runway end and can change during works or after a displaced threshold. Saying “the runway is 3,000 metres” is therefore only the beginning of a performance discussion.
Clearway and stopway
A clearway is an obstacle-controlled area beyond the runway that an aircraft may use in its airborne takeoff performance calculation. It does not need to support the aircraft. A stopway is a prepared area beyond the takeoff run that can support an aircraft during an abandoned takeoff.
The easiest distinction is that clearway contributes to TODA, while stopway contributes to ASDA. Neither automatically adds to landing distance, and neither is simply “extra runway.”
Runway strip, RESA, and OFZ
A runway strip surrounds the runway and associated stopway to reduce damage if an aircraft leaves the paved surface and to protect aircraft flying over it. A Runway End Safety Area (RESA) extends beyond the runway strip end to reduce the consequences of undershoots and overruns. An Obstacle Free Zone (OFZ) is protected airspace around the runway and approach surfaces.
These protections solve different problems. A RESA is not the same as a stopway, and an OFZ is not a paved area. Development proposals often work geometrically until one of these protected envelopes is added to the drawing.
ACR/PCR and ACN/PCN
The ICAO Aircraft Classification Rating and Pavement Classification Rating system, ACR/PCR, expresses aircraft pavement loading and pavement bearing capability. It replaced the legacy Aircraft Classification Number and Pavement Classification Number, ACN/PCN, framework in ICAO application from late 2024, although legacy terminology remains common.
At its simplest, unrestricted operation is generally expected when the aircraft rating does not exceed the reported pavement rating, subject to tire pressure, pavement type, and local conditions. Limited overload operations may still be acceptable under an engineering policy. A single rating is not a full pavement-life analysis, despite its irresistible usefulness in presentation decks.
Rapid-exit taxiway
A rapid-exit taxiway is connected to a runway at an acute angle so landing aircraft can vacate at higher speed than on a conventional right-angle exit. It is also called a high-speed exit.
Its purpose is to reduce runway occupancy time and increase arrival throughput. The benefit depends on aircraft mix, touchdown behavior, exit location, braking conditions, and the downstream taxiway layout. A beautifully positioned exit is less useful if the receiving taxiway is routinely blocked.
Contact, remote, and MARS stands
A contact stand provides direct terminal access, normally through a passenger boarding bridge. A remote stand requires bussing or walking and often supports towing, staging, or long dwell. A Multiple Aircraft Ramp System (MARS) stand can accommodate one large aircraft or multiple smaller aircraft in alternative marked configurations.
MARS stands create flexibility but require careful stand guidance, fueling, bridge, service-road, blast, and safeguarding arrangements. Capacity models that count every painted position as simultaneously usable tend to age badly.
Apron management service
An apron management service coordinates aircraft and vehicle movement on aprons where responsibility is not exercised directly by air traffic control. It may allocate taxi instructions, sequence pushbacks, operate visual docking systems, or coordinate stand access.
The handoff point between apron control and tower control is operationally important. It determines radio frequencies, clearances, incident responsibility, and how departure queues are managed. Organizational ownership varies considerably between airports.
Navigation and Surveillance
CNS/ATM
Communications, Navigation and Surveillance/Air Traffic Management, usually shortened to CNS/ATM, is the technical and operational ecosystem supporting air traffic services. Communications connect pilots and controllers, navigation determines and follows position, surveillance shows the traffic picture, and ATM organizes the resulting flows.
Practitioners may use CNS to mean the engineering asset base and ATM to mean the operational service. The dividing line is useful but imperfect because modern procedures depend heavily on integrated software, data networks, and aircraft capabilities.
Performance-Based Navigation
Performance-Based Navigation (PBN) specifies the navigation performance required for an operation rather than prescribing particular ground-based aids. Performance requirements can include accuracy, integrity, continuity, availability, functionality, and onboard monitoring.
PBN enables more repeatable tracks, tailored terminal routes, reduced reliance on conventional beacons, and access to constrained terrain or airspace. It does not mean aircraft may fly any path they choose. The published navigation specification, procedure design, aircraft approval, crew authorization, and surveillance environment still control.
RNAV and RNP
Area Navigation (RNAV) allows aircraft to fly a desired path within navigation-aid coverage or onboard-system capability. Required Navigation Performance (RNP) is a form of RNAV that additionally requires onboard performance monitoring and alerting.
Both appear as navigation specifications such as RNAV 1 or RNP 1. The number broadly expresses lateral accuracy in nautical miles for the specified operation, but it is not the entire approval standard. RNP Authorization Required procedures impose additional aircraft, crew, and operational controls and should not be treated as interchangeable with ordinary RNP procedures.
SID and STAR
A Standard Instrument Departure (SID) connects a runway or terminal area to the en-route structure. A Standard Instrument Arrival (STAR) brings traffic from the en-route network toward an approach or terminal sequencing point.
SIDs and STARs package routes, altitude constraints, speed constraints, navigation requirements, and noise considerations into repeatable procedures. Clearance to follow one does not always authorize every published vertical element automatically; phraseology and local rules matter. This distinction has generated more than a few energetic safety briefings.
ILS categories
An Instrument Landing System (ILS) provides lateral and vertical guidance to a runway. CAT I, CAT II, and CAT III operations support progressively lower decision heights and runway visual ranges, with CAT III subdivided under some regulatory frameworks.
A runway having CAT III ground equipment does not by itself create a CAT III operation. The aircraft, crew, operator approval, lighting, power redundancy, runway protection, low-visibility procedures, and equipment serviceability must all support the category. One unserviceable component can raise the applicable minima.
RVR, DA, and DH
Runway Visual Range (RVR) estimates how far a pilot on the runway centerline can see runway markings or lights. It is measured or assessed for specified runway zones and is not the same as general meteorological visibility.
Decision Altitude (DA) is referenced to mean sea level, while Decision Height (DH) is referenced to the relevant threshold or touchdown elevation. At the applicable point, the approach may continue only if the required visual reference has been acquired and other conditions are met.
GBAS and SBAS
A Ground-Based Augmentation System (GBAS) uses equipment at or near an airport to augment satellite navigation and support precision approach guidance. A Satellite-Based Augmentation System (SBAS) provides wide-area corrections and integrity information through satellites.
GBAS can support multiple runway ends from one installation and enable flexible approach paths. SBAS has broader geographic coverage but different service and approval characteristics. Neither should be described simply as “GPS landing” when discussing certification or operational resilience.
ADS-B and Mode S
Automatic Dependent Surveillance-Broadcast (ADS-B) allows an aircraft to broadcast identity, position, altitude, velocity, and other information derived from onboard systems. Mode S is a selective secondary surveillance capability using unique aircraft addresses and supporting richer data exchange than older transponder modes.
ADS-B depends on aircraft-reported position rather than radar-derived range and bearing. ANSPs may combine ADS-B, Mode S radar, multilateration, and flight-plan data into one surveillance picture. Coverage on the controller display does not necessarily mean every underlying sensor has the same integrity or failure mode.
A-SMGCS, SMR, and multilateration
An Advanced Surface Movement Guidance and Control System (A-SMGCS) supports surveillance, routing, guidance, and control of aircraft and vehicles on the movement area, particularly in low visibility or complex layouts. Surface Movement Radar (SMR) detects objects directly, while multilateration calculates position from transponder-signal arrival times at multiple receivers.
A-SMGCS may provide labels, conflict alerts, route support, stop-bar integration, and vehicle tracking. Its capability is better described by the implemented services than by assuming a universal “level” label, since maturity frameworks differ.
Air Traffic Control and Flow Management
ATS and ATC
Air Traffic Services (ATS) is the wider family that includes flight information, alerting, air traffic advisory service where provided, and air traffic control. Air Traffic Control (ATC) specifically aims to prevent collisions and maintain an orderly flow of traffic through aerodrome, approach, and area control services.
Calling every ANSP activity “ATC” overlooks functions such as aeronautical information, communications infrastructure, flow management, and alerting. This matters in cost allocation, regulation, staffing, and service-level discussions.
TWR, APP, and ACC
Tower (TWR) controls aerodrome traffic and usually the immediate runway environment. Approach control (APP) manages arriving and departing traffic in terminal airspace. An Area Control Centre (ACC) manages en-route traffic across one or more control areas.
These are service functions, not necessarily separate buildings. Approach control may be located in a tower, an ACC, or a remote center. Responsibility can also be delegated across geographic boundaries, so organizational charts should not be mistaken for airspace maps.
Sectorization and sector opening scheme
Sectorization divides controlled airspace into manageable controller sectors. A sector opening scheme specifies how elementary sectors are combined or split at different demand levels and staffing configurations.
Opening more sectors can increase capacity, but only if trained controllers, frequencies, workstations, coordination arrangements, and adjacent-sector interfaces are available. Excessive fragmentation can create additional handoffs and coordination workload, so “just open another sector” is not always the operational masterstroke it sounds like.
Executive and planner controller
In many control environments, an executive controller communicates with aircraft and issues tactical clearances, while a planner controller manages coordination, traffic planning, and boundary conditions. Titles and task allocation vary by ANSP.
The pairing is central to sector capacity and workload studies. A traffic count alone may miss the coordination burden carried by the planner or the tactical complexity faced by the executive controller.
Separation minima
Separation minima define the required vertical, lateral, longitudinal, or radar-based spacing between relevant aircraft. The applicable minimum depends on airspace, surveillance capability, navigation performance, communication, aircraft status, and regulatory approval.
Minima are hard safety constraints, but the spacing controllers actually deliver may be larger to absorb uncertainty, wake effects, runway sequencing, or coordination delays. Capacity models based solely on the legal minimum are therefore usually optimistic.
Wake turbulence separation and RECAT
Wake turbulence separation protects following aircraft from vortices generated by heavier or aerodynamically different aircraft. Traditional schemes group aircraft into broad wake categories. RECAT, or recategorization, uses more refined aircraft groupings and pair-specific evidence to reduce unnecessary spacing safely.
RECAT can improve runway throughput, particularly with a favorable aircraft mix. Benefits depend on sequence composition and controller tools, not just formal approval. A schedule full of identical narrowbodies behaves differently from alternating heavy and light aircraft.
ATFCM
Air Traffic Flow and Capacity Management (ATFCM) balances traffic demand against available airport, sector, route, and network capacity. In the United States, the broader term Traffic Flow Management is more common.
ATFCM operates strategically, pre-tactically, and tactically. Measures include rerouting, level restrictions, ground delays, miles-in-trail, departure sequencing, and capacity regulations. It is a network function because solving congestion at one point can move it to another.
Sector capacity and occupancy count
Sector capacity is commonly expressed as an entry rate or sustainable traffic count over a specified period. Occupancy count considers how many aircraft are simultaneously present or predicted in the sector, often within shorter overlapping intervals.
The two answer different workload questions. Entry rate measures flow into the sector; occupancy reflects how long aircraft remain and how much traffic accumulates. Weather deviations and slow-climbing traffic can raise occupancy even when the entry rate looks normal.
ATFM regulation
An ATFM regulation limits demand through a constrained airport, sector, or airspace volume by assigning a regulated flow rate for a defined period. In European network operations, it creates calculated takeoff times for affected flights.
The regulation carries a reason, location, duration, capacity value, and delay consequences. A weather regulation and an ATC-capacity regulation may produce similar delays but imply very different operational, regulatory, and performance narratives.
CTOT and slot tolerance window
A Calculated Takeoff Time (CTOT) is the takeoff time assigned to a flight subject to an ATFM measure. The associated tolerance window defines when the aircraft may take off and remain compliant. In much of Europe, the standard window is commonly five minutes before to ten minutes after CTOT, subject to applicable procedures.
A CTOT is not an airport schedule slot and not simply a startup time. Airport and airline teams work backward from it using taxi assumptions, pushback sequencing, and readiness estimates. Missing the window may trigger a revised CTOT and materially more delay.
EOBT and flight-plan updating
The Estimated Off-Block Time (EOBT) in the flight plan is the estimated time the aircraft will begin movement associated with departure. It drives route validation, network demand forecasts, and ATFM calculations.
If the flight is delayed, the EOBT must be updated according to network rules, often through a delay message or equivalent system transaction. Stale EOBTs create phantom demand, poor slot allocation, and distrust in the plan. Networks dislike fictional aircraft almost as much as airports dislike unannounced real ones.
Airport Collaborative Decision-Making
A-CDM
Airport Collaborative Decision-Making (A-CDM) is an operating framework through which airport operators, aircraft operators, ground handlers, ATC, and network managers share consistent turnaround and departure information.
The objective is predictability, not merely more meetings or a shared dashboard. A-CDM aligns milestones, timestamps, responsibilities, and data exchanges so that local readiness information improves stand planning, departure sequencing, and network forecasts.
A-CDM milestone approach
The milestone approach tracks a flight through defined events such as flight-plan activation, takeoff from the origin, local landing, in-block, turnaround updates, startup approval, off-block, and takeoff.
Each milestone can trigger validation, alerts, or recalculation. Practitioners care less about whether a timestamp exists than whether it arrives early enough, comes from the accountable source, and causes the expected operational response.
TOBT
Target Off-Block Time (TOBT) is the aircraft operator’s or ground handler’s best estimate of when the aircraft will be ready to leave the stand, with turnaround activities completed to the locally defined readiness standard.
TOBT is an operational commitment, not a hopeful scheduled time. It feeds departure sequencing and should be updated when readiness changes beyond defined tolerances. Repeated late updates degrade both local sequencing and network planning.
TSAT
Target Start-up Approval Time (TSAT) is the time at which an aircraft can expect startup or pushback approval, taking account of TOBT, runway sequence, local constraints, and any CTOT.
TSAT is calculated by the airport or departure management process rather than declared by the airline. It does not guarantee immediate movement, but it tells the flight when the departure system expects to accept it. A stable TSAT is usually evidence of a stable plan.
TTOT and variable taxi time
Target Takeoff Time (TTOT) is the predicted time the aircraft will take off. It is derived from departure sequencing, TSAT or off-block timing, and a variable taxi time that reflects stand location, runway, traffic conditions, and local routing.
Using one fixed taxi allowance for every stand and runway pair undermines the calculation. Variable taxi times help connect terminal readiness with runway and network demand, which is the central trick behind much of A-CDM.
DMAN
A Departure Manager (DMAN) is a decision-support system that builds and updates a pre-departure sequence. It considers aircraft readiness, runway capacity, wake separation, routes, CTOTs, taxi times, and local priorities.
DMAN advises rather than magically creates capacity. If TOBT data are poor, the tool may sequence inaccurate assumptions with impressive computational efficiency.
AMAN and XMAN
An Arrival Manager (AMAN) sequences inbound aircraft to optimize flow toward a runway or terminal entry point. Extended Arrival Management (XMAN) pushes sequencing actions farther upstream, often into neighboring control centers.
The aim is to absorb delay through earlier speed adjustment rather than low-level vectoring or holding near the destination. Benefits include predictability, lower fuel burn, and reduced controller workload, but they depend on cross-border coordination and reliable trajectory data.
DPI
Departure Planning Information (DPI) messages communicate local departure estimates and status from an A-CDM airport to the network manager. European implementations include several DPI types corresponding to different planning stages.
DPI updates allow the network model to replace generic assumptions with airport-specific readiness and takeoff forecasts. If DPI quality deteriorates, network calculations may fall back to less accurate flight-plan information.
APOC
An Airport Operations Centre (APOC) brings airport, airline, handler, ATC, security, border, and other operational representatives into a shared decision environment. Some airports use a virtual model; others operate a physical center.
An APOC is most valuable during disruption, when stand, passenger, baggage, runway, and airspace decisions interact. The building itself is not the capability. Decision rights, common situational awareness, and tested playbooks matter more than the number of screens.
Aerodrome Safety and Surface Conditions
Aerodrome certificate
An aerodrome certificate is the civil aviation authority’s approval for an aerodrome to operate within a defined scope. Certification typically covers infrastructure, operating procedures, competence, emergency arrangements, the aerodrome manual, and continuing compliance.
A certified aerodrome may still have approved deviations, exemptions, operational restrictions, or corrective actions. Certification is therefore not a claim that every feature meets the latest standard without qualification.
ANSP certification and designation
Certification establishes that an air navigation service provider meets regulatory requirements for specified services. Designation or equivalent state authorization gives the provider responsibility to deliver those services in defined airspace or at defined aerodromes.
The distinction is important in liberalized or cross-border service markets. A provider may be technically certified without being designated to serve a particular airspace volume. Terminology and legal structures vary by region.
SMS and safety assessment
Aviation Safety Management Systems (SMS) provide a structured framework for identifying hazards, assessing safety risk, assuring controls, reporting occurrences, and monitoring safety performance. A safety assessment applies that discipline to a particular operational or technical change.
ANSPs often express the result as a safety argument supported by evidence, requirements, and assurance activities. A risk register alone is not a safety case. The assessment must explain why the changed system will remain acceptably safe in its actual operating environment.
Runway incursion and runway excursion
A runway incursion involves the incorrect presence of an aircraft, vehicle, or person on the protected area of a surface designated for takeoff or landing. A runway excursion occurs when an aircraft veers off or overruns the runway surface.
Incursions concern conflict and unauthorized presence; excursions concern loss of runway containment. Their prevention measures differ. Stop bars, clearance discipline, and surface surveillance primarily address incursions, while runway condition, braking, approach stability, and RESA provision feature heavily in excursion risk.
Runway hotspot
A hotspot is a location on an aerodrome movement area with a history or potential risk of collision or runway incursion where heightened pilot, driver, and controller attention is required.
Hotspots are charted and accompanied by local mitigations such as markings, lighting, route restrictions, phraseology, or briefing. A hotspot designation is not merely an admission of bad geometry. It is an operational warning that normal situational awareness may be insufficient.
Low-Visibility Procedures
Low-Visibility Procedures (LVP) are special aerodrome and ATC procedures activated below defined visibility or cloud thresholds. They protect instrument-landing critical areas, control vehicle access, alter taxi routes, increase spacing, and preserve surface awareness.
LVP activation usually reduces capacity before weather reaches the landing minima. This is why a technically CAT III-capable runway can still generate extensive delay during fog.
OLS and PANS-OPS surfaces
Obstacle Limitation Surfaces (OLS) protect aerodrome airspace by restricting the height and location of objects around runways. PANS-OPS surfaces are constructed for instrument procedure design and obstacle clearance.
They overlap but are not interchangeable. A building may satisfy the statutory aerodrome safeguarding surface yet affect a particular departure, missed approach, or procedure-design surface. Airport planners therefore need both aerodrome safeguarding and flight-procedure analysis.
FOD and wildlife hazard
Foreign Object Debris is any inappropriate object on the movement area that could damage aircraft or equipment. Foreign Object Damage is the resulting harm, although practitioners use FOD for both. Wildlife hazards include bird and animal activity that can cause strikes or operational disruption.
Controls include inspections, sweeping, staff reporting, habitat management, dispersal, waste control, and strike-data analysis. The small object on the apron may have a remarkably direct path to an engine invoice.
RFF category
The aerodrome Rescue and Fire Fighting (RFF) category is determined principally by the dimensions of aircraft normally using the aerodrome. It drives minimum extinguishing-agent quantities, vehicle capability, staffing, and response requirements.
An airport can sometimes operate at a temporarily reduced category under prescribed conditions, but this may restrict aircraft types or require airline acceptance and regulatory procedures. RFF category is therefore both a safety classification and an operating constraint.
GRF, RCR, and RWYCC
The ICAO Global Reporting Format (GRF) standardizes assessment and reporting of runway surface conditions. The airport issues a Runway Condition Report (RCR), assigning a Runway Condition Code (RWYCC) from 0 to 6 for each runway third, together with contaminant type, depth, and coverage where applicable.
Flight crews use the report for landing and takeoff performance. Pilot braking-action reports can support reassessment under the applicable procedure. RWYCC is not a general weather score; it is a performance-oriented description of the runway surface.
SNOWTAM
A SNOWTAM is a special-series NOTAM reporting hazardous runway, taxiway, or apron conditions caused by snow, ice, slush, frost, or standing water under the prescribed format.
Under GRF, it carries structured runway-condition information rather than free-form winter commentary. Despite the name, its relevance extends beyond falling snow and into the full glamorous family of frozen and wet contaminants.
Aeronautical Information and Data
AIP
The Aeronautical Information Publication (AIP) is a state’s authoritative publication of aeronautical information of lasting significance. It includes national rules, airspace structures, routes, aerodrome data, communications, procedures, and facilities.
The AIP is controlled operational information, not a tourist guide for pilots. Permanent changes belong in the AIP, while temporary or short-notice changes may be distributed through supplements, circulars, or NOTAMs.
AIRAC cycle
Aeronautical Information Regulation and Control (AIRAC) is the internationally synchronized cycle for publishing operationally significant aeronautical changes. Effective dates occur every 28 days, with information distributed sufficiently early for data preparation and flight-management-system loading.
Missing an AIRAC deadline can postpone a procedure or airspace change by an entire cycle or more. The physical work may be complete, but the operation cannot safely begin until charts, databases, systems, and users contain the same effective information.
NOTAM
A NOTAM distributes time-critical aeronautical information concerning the establishment, condition, or change of a facility, service, procedure, or hazard. Typical subjects include closures, lighting failures, crane activity, navigation-aid outages, and temporary restrictions.
NOTAMs are not intended to become a permanent substitute for updating the AIP. Excessive volume, poor wording, and obsolete notices create information overload, which is why filtering and digital NOTAM initiatives receive so much attention.
ATIS
Automatic Terminal Information Service (ATIS) broadcasts routine arrival and departure information such as runway in use, weather, transition level, significant conditions, and operational remarks. Updates receive sequential identifying letters.
Pilots report the current ATIS identifier when contacting ATC, reducing repetitive frequency traffic. A new letter may reflect a meaningful runway or weather change, or merely an update to one detail, so controllers still verify critical information.
METAR and TAF
A METAR is a coded routine aerodrome weather observation. A Terminal Aerodrome Forecast (TAF) describes expected conditions over a defined period around the aerodrome.
METAR tells operators what was observed at the reporting time; TAF expresses a forecast with change groups and probabilities. Neither alone captures every operationally relevant phenomenon, and airports often supplement them with runway sensors, wind-shear systems, lightning data, and local forecasts.
SWIM
System Wide Information Management (SWIM) is the architectural approach for sharing standardized, governed, service-based ATM information across authorized participants. It supports interoperable exchange of flight, aeronautical, weather, and capacity information.
SWIM is not one giant central database. It is a framework of information services, standards, governance, security, and technical infrastructure. The difficult part is often agreeing what a data element means before exchanging it faster.
AIXM, FIXM, and IWXXM
AIXM models aeronautical information, FIXM models flight and flow information, and IWXXM supports structured exchange of aviation meteorological information. These standards enable machine-readable data exchange across ATM systems.
They are not interchangeable file formats. Each covers a different information domain, and implementation profiles may select only portions of the full model. Data semantics, version control, and effective dates are as important as message transport.
Passenger and Baggage Systems
CUPPS and CUTE
Common Use Passenger Processing Systems (CUPPS) allow multiple airlines to use shared check-in desks, gates, printers, and workstations through standardized interfaces. Common Use Terminal Equipment (CUTE) is the older term and remains common in speech and legacy contracts.
Common use lets airports allocate counters and gates flexibly without installing a dedicated airline stack at every position. It does not remove airline applications or departure-control logic; it provides the shared environment through which they are accessed.
CUSS
Common Use Self-Service (CUSS) is the standard framework allowing multiple airlines to offer check-in and related services through shared kiosks. The airline application remains distinct even though the physical device and platform are common.
CUSS is often discussed alongside self-bag-drop, but the two are not identical. A kiosk may issue a boarding pass or bag tag without performing the physical bag acceptance and security checks required at the bag-drop unit.
DCS
An airline’s Departure Control System (DCS) manages check-in, seat assignment, passenger acceptance, load control interfaces, boarding status, and flight closure. Airport common-use systems provide access to the DCS but do not replace it.
When boarding or check-in fails, the distinction determines which party investigates. The screen may belong to the airport, the application to the airline, the network to another provider, and the printer to someone whose name appears only after the incident bridge begins.
BHS and HBS
The Baggage Handling System (BHS) transports, identifies, sorts, stores, and presents bags between check-in, screening, make-up, transfer, and reclaim. Hold Baggage Screening (HBS) applies regulated security screening, usually through explosive-detection equipment and defined alarm-resolution levels.
BHS capacity is governed by more than conveyor speed. Screening availability, merge logic, destination coding, early-bag storage, make-up capacity, operator interventions, and fault recovery all matter.
BRS and Resolution 753
A Baggage Reconciliation System (BRS) confirms that bags are associated with accepted passengers and supports load verification before departure. IATA Resolution 753 requires bag tracking at key custody events, including acceptance, aircraft loading, transfer, and arrival delivery.
Reconciliation answers whether a bag is authorized and accounted for on the flight. Tracking answers where custody was recorded. A scan can satisfy a tracking point without proving the entire reconciliation process was correct.
EBS and make-up
Early Bag Storage (EBS) holds bags that arrive before their flight is open for final sortation. The make-up area is where sorted bags are assembled and loaded into carts or unit load devices for transport to the aircraft.
EBS can smooth peaks and support transfer operations, but it cannot compensate indefinitely for inadequate make-up positions or late flight allocation. Stored bags still need somewhere to go when the schedule becomes real.
Minimum Connection Time
Minimum Connection Time (MCT) is the shortest scheduled interval permitted between an arriving and departing flight for a defined airport, terminal, airline, route, or passenger-processing combination.
MCT is a schedule-construction rule, not a guarantee that every passenger can make the connection under every condition. Domestic-to-domestic, international-to-international, terminal-change, and security-rescreening connections may each have different values.
AODB
The Airport Operational Database (AODB) is the central operational repository for flight schedules, aircraft movements, stands, resources, timestamps, and status information. It typically integrates airline, ATC, handler, baggage, billing, and display systems.
The AODB is often called the airport’s operational source of truth. In practice, becoming the source of truth requires rules about which system owns each field, how conflicts are resolved, and how late changes propagate.
RMS and FIDS
A Resource Management System (RMS) allocates airport resources such as stands, gates, counters, baggage belts, and make-up positions. A Flight Information Display System (FIDS) publishes selected flight information to passengers and staff.
RMS makes allocation decisions; FIDS communicates operational information. Both usually consume AODB data, but local overrides and timing rules can create visible discrepancies. The passenger notices the display, while the root cause may sit three interfaces upstream.
OOOI, AIBT, and AOBT
OOOI refers to the aircraft movement events out, off, on, and in: leaving the stand, taking off, landing, and arriving at the stand. Airport and A-CDM terminology commonly uses Actual Off-Block Time (AOBT), Actual Takeoff Time (ATOT), Actual Landing Time (ALDT), and Actual In-Block Time (AIBT).
Different systems may derive these events from chocks, doors, parking brake, transponder, ACARS, or surveillance data. Two timestamps with the same label can therefore differ unless the triggering event and source are specified.
Airport Slots and Capacity
IATA Level 1, Level 2, and Level 3 airports
Under the IATA Worldwide Airport Slot Guidelines, a Level 1 airport has adequate capacity for demand, a Level 2 airport requires schedule facilitation, and a Level 3 airport requires formal slot coordination because demand significantly exceeds available capacity.
Level 3 status means planned operations require allocated airport slots. It does not mean every hour is equally constrained, nor that physical expansion is the only remedy. Runway, terminal, stand, environmental, and regulatory constraints may bind at different times.
Airport slot and ATFM slot
An airport slot is permission to use coordinated airport infrastructure for an arrival or departure at a specified date and time. An ATFM slot, commonly represented by a CTOT, is a day-of-operation flow-management restriction.
The airport slot belongs to schedule planning; the ATFM slot manages tactical network demand. A flight may hold a valid airport slot and still receive a two-hour ATFM delay. Conversely, an on-time CTOT does not cure operation outside the coordinated airport slot.
Coordination parameters
Coordination parameters are the capacity limits used by a slot coordinator or facilitator when assessing schedules. They may cover runway movements, terminal passengers, stands, gates, baggage systems, or other constrained resources by time interval.
Parameters are usually more detailed than a single annual capacity figure. They may vary by arrival or departure, aircraft type, terminal, international status, or rolling interval. Changing one parameter can merely reveal the next bottleneck.
Series of slots
A series of slots is generally at least five slots requested for the same service at approximately the same time on the same day of the week and distributed regularly within one scheduling season.
Series status matters because historic precedence is assessed at series level. Ad hoc individual slots do not automatically generate the same future-season rights.
Historic precedence and the 80/20 rule
Historic precedence allows an airline to retain a slot series in the equivalent next season if it satisfies the applicable usage requirement. The traditional rule requires at least 80 percent use, producing the shorthand 80/20 or “use it or lose it.”
Waivers and regional legislation can modify the threshold or treatment. The calculation also depends on cancellations, approved changes, and justified non-use. It is not simply flights operated divided by slots initially requested.
JNUS
Justified Non-Use of Slots (JNUS) covers specified circumstances in which non-operation may be disregarded for historic-precedence purposes. Examples can include airport closure, severe disruption, government restrictions, or other qualifying events under the applicable rules.
JNUS is evidence-based and rule-specific. Airlines cannot usually label ordinary commercial cancellations as extraordinary and expect the usage calculation to become sentimental.
Slot pool and new entrant
Slots without historic precedence, newly created capacity, and returned slots enter the slot pool for allocation. New entrant status gives qualifying carriers priority consideration for a portion of available slots.
The legal definition of new entrant varies by jurisdiction and may depend on the carrier’s existing number of slots, route presence, or group relationships. Priority does not guarantee commercially attractive timings.
Schedule facilitation
At a Level 2 airport, a schedule facilitator works with airlines to adjust planned timings and avoid capacity exceedances. Unlike a Level 3 coordinator, the facilitator does not allocate mandatory airport slots.
The process relies on cooperation, schedule transparency, and realistic capacity analysis. Persistent non-cooperation can support escalation toward formal coordination if congestion becomes structural.
Secondary slot trading
Secondary trading allows airlines to exchange, transfer, lease, or commercially trade airport slots where the legal regime permits. The coordinator still records or approves the transaction and checks compliance with applicable rules.
Trading is well established at some highly constrained airports and prohibited or more limited elsewhere. The economic value attaches to access at a scarce time, but the legal characterization of that value is jurisdiction-dependent.
Curfew and night quota
A curfew prohibits or restricts operations during specified hours. A night quota permits limited operations, often controlled through movement counts, noise classifications, or quota-count budgets.
The distinction matters in schedule recovery. A delayed flight facing a hard curfew may not operate at all, while a quota regime may permit it if aircraft classification and remaining allowance support the movement.
Operational Performance
Busy hour and design day
The busy hour represents a high-demand operating interval selected for planning or performance analysis. A design day is a representative schedule used to test facilities and processes, often reflecting a future planning year rather than the single busiest historical day.
Neither is automatically the absolute peak. Designers often exclude rare extremes that would produce uneconomic infrastructure, but the chosen percentile and schedule assumptions should be explicit.
Declared capacity and practical capacity
Declared capacity is the capacity made available for scheduling or flow-management purposes. Practical capacity is the throughput that can be sustained at an acceptable level of delay, resilience, and operating quality.
Theoretical maximum throughput assumes an unusually cooperative world. Practical capacity recognizes wake mix, runway crossings, weather, controller workload, stand availability, and disruption recovery. If a runway can process 50 movements for one heroic hour but only 42 reliably, practitioners usually care about the latter.
IATA Level of Service
IATA’s airport Level of Service framework evaluates passenger-processing facilities using space, waiting time, and operating conditions. The target is generally an optimum condition rather than maximum spaciousness or zero waiting.
Newcomers sometimes treat Level of Service as a single airport-wide grade. It is assessed by process area and time period, so check-in may be acceptable while security or immigration is overloaded.
ASMA additional time
The Arrival Sequencing and Metering Area (ASMA) metric estimates additional time flown within a defined terminal-area radius, commonly 40 nautical miles, compared with an unimpeded reference time.
It is used as a proxy for arrival inefficiency caused by holding, vectoring, sequencing, and congestion. High ASMA time does not by itself identify the responsible party; runway demand, weather, airspace design, airline sequencing, and upstream flow management may all contribute.
Additional taxi-out time
Additional taxi-out time compares actual taxi-out duration with an unimpeded reference for comparable runway and stand conditions. It highlights surface congestion, departure queuing, remote-stand effects, and inefficient sequencing.
It is not the same as total taxi time. A long taxi from a distant stand may be structurally necessary, while additional time attempts to isolate the avoidable or congestion-related portion.
ATFM delay per flight
ATFM delay per flight measures delay assigned through flow-management regulations, usually averaged over all flights or affected flights. It is often calculated from the difference between an assigned takeoff time and the flight’s earliest feasible takeoff basis.
It should not be confused with passenger arrival delay or total departure delay. A flight can absorb ATFM delay through turnaround recovery, faster taxi, or shorter airborne time, while another flight can arrive late without any ATFM delay.
A0 and A15
A0 measures operations completed no later than the scheduled time, while A15 allows a fifteen-minute threshold. Airports and airlines may calculate these using departure off-block time, arrival in-block time, or another specified event.
The denominator, event definition, early-operation treatment, and cancellations policy matter. A punctuality figure without those conventions is numerically tidy but operationally ambiguous.
ATCO-hour productivity
Air Traffic Control Officer-hour productivity relates controlled traffic output, such as IFR flight hours or movements, to controller hours worked on operational duty. It appears in ANSP benchmarking and economic-efficiency analysis.
Higher values can reflect better staffing efficiency, favorable traffic complexity, larger sectors, or delayed investment. Comparisons require normalization for airspace complexity, seasonality, service scope, training time, and resilience requirements.
ASQ
Airport Service Quality (ASQ) is Airports Council International’s standardized passenger-experience measurement program. It benchmarks satisfaction across touchpoints such as access, cleanliness, security, wayfinding, facilities, and overall experience.
ASQ is survey-based and should not be confused with objective queue or processing measurements. It reveals how passengers perceived the operation, which is often related to measured performance but occasionally follows its own mysterious logic.
Economic Regulation and Charges
Aeronautical and non-aeronautical revenue
Aeronautical revenue arises from airport services directly associated with aircraft, passengers, and regulated operational facilities. Non-aeronautical revenue includes retail, food and beverage, parking, property, advertising, and other commercial activities.
The boundary affects economic regulation, till treatment, investment incentives, and airline consultation. Items such as common-use systems, premium facilities, or property serving aeronautical users may be classified differently under local rules.
Single till, dual till, and hybrid till
Under a single till, commercial revenues and costs are considered when setting aeronautical charges. A dual till separates aeronautical activities from commercial activities, allowing the airport to retain more commercial upside. A hybrid till shares only part of that benefit with aeronautical users.
Till choice materially changes airport charges, investment incentives, and risk allocation. Two regulators can accept the same traffic and capital assumptions yet produce different tariffs because they draw the regulated boundary differently.
Residual and compensatory agreements
In a residual airport-use agreement, signatory airlines generally cover the airport’s remaining agreed revenue requirement after other revenues, receiving influence or benefits in return. Under a compensatory model, airlines pay specified rates while the airport bears more traffic and financial risk.
These terms are especially associated with the United States. Real agreements often blend the models by cost center, so labeling an airport wholly residual or compensatory may conceal the important mechanics.
Landing charge and MTOW basis
A landing charge is commonly assessed by aircraft Maximum Takeoff Weight (MTOW), often per tonne or part thereof. Charges may include minimum fees and modifiers for noise, emissions, time of day, or congestion.
MTOW charging is administratively straightforward but does not perfectly represent runway wear, capacity consumption, or environmental impact. A light aircraft can consume much the same runway slot as a larger one, which is why charging structures attract lively airline consultation.
Passenger Service Charge
A Passenger Service Charge (PSC) is levied per departing, arriving, or transferring passenger to recover eligible terminal and passenger-processing costs. It may be paid by airlines, embedded in the ticket, or collected through another statutory mechanism.
Rates often vary by domestic or international status, transfer category, terminal, or passenger exemption. The commercial label may be similar across airports while the regulated cost base differs substantially.
RAB and building-block model
A Regulated Asset Base (RAB) represents capital invested in assets recognized for regulatory remuneration. A building-block model typically combines return on the RAB, depreciation, operating expenditure, tax, and traffic assumptions to determine allowed revenue.
The contentious questions are usually which assets enter the RAB, when they enter, how efficiently incurred expenditure is treated, and who bears volume risk. A terminal can be physically complete while its regulatory treatment remains very much under construction.
Price cap
A price cap limits airport charges or allowed revenue over a regulatory period. Formulas may use inflation less an efficiency factor, revenue-per-passenger caps, service-quality adjustments, or building-block calculations.
The cap is only the visible output. Traffic forecasts, capital allowances, cost efficiency, service standards, and risk-sharing rules determine how demanding it really is.
Service unit and unit rate
ANSP charges are often calculated using service units that weight traffic by distance and aircraft weight. A unit rate converts those service units into a monetary charge. In European route charging, the simplified structure is:
Route charge = distance factor × aircraft weight factor × unit rate
Service units normalize traffic for charging and performance analysis. They are not the same as flights, movements, or flight hours, so traffic growth can differ depending on the measure used.
Route and terminal air navigation charges
Route charges recover eligible en-route air navigation costs. Terminal charges recover eligible approach and aerodrome control costs within a terminal charging zone or equivalent framework.
The boundary between route and terminal services is set by regulation rather than by an obvious physical line. Cost allocation, exempt flights, weight formulas, and collection arrangements vary across states.
Determined unit cost and risk sharing
Under performance-based ANSP regulation, determined unit cost is the approved cost per forecast service unit for a reference period. Traffic risk-sharing and cost risk-sharing rules determine how deviations from forecasts and approved costs are divided between users and the provider.
These mechanisms prevent every traffic surprise from automatically becoming either an airline problem or an ANSP problem. The thresholds, carryovers, and exceptional-cost provisions often matter more than the headline unit-rate target.
Planning and Operational Readiness
Airport master plan and ALP
An airport master plan defines the long-term development of runways, terminals, stands, access, utilities, commercial land, and supporting infrastructure against forecast demand and policy objectives. In the United States, the formal Airport Layout Plan (ALP) records existing and proposed development in an approved drawing set.
A master plan is a strategic and technical development framework, while the ALP has a specific regulatory and grant-related role. Neither by itself authorizes construction or airspace changes.
Design aircraft and critical aircraft
The design aircraft is the aircraft, or family of aircraft, whose physical and operational characteristics drive facility dimensions. The critical aircraft is often the most demanding aircraft that regularly uses, or is forecast regularly to use, a facility under the applicable standard.
“Most demanding” may refer to wingspan, tail height, approach speed, pavement loading, turning radius, or another characteristic. The largest aircraft overall is not necessarily critical for every design element.
Planning Activity Level
A Planning Activity Level (PAL) is a demand threshold that triggers a planned development stage, such as a terminal expansion, additional stand pier, or baggage-system upgrade.
PALs are preferable to calendar-only triggers because traffic rarely respects the forecast year printed in the business case. A project may be advanced, deferred, or reconfigured depending on when the threshold is actually approached.
Concept of Operations
A Concept of Operations (ConOps) describes how a proposed airport, airspace, procedure, technology, or operating model will function from the users’ perspective. It identifies actors, scenarios, information flows, roles, constraints, and abnormal situations.
In airspace and ATM work, the ConOps bridges strategic intent and detailed requirements. A diagram showing cleaner routes is not yet a ConOps unless it explains how controllers, pilots, systems, and adjacent units operate them.
Fast-time simulation
Fast-time simulation models airport or airspace operations faster than real time using algorithmic behavior. It can test runway configurations, sector demand, taxi flows, stand plans, delay, route structures, and future traffic scenarios.
Results depend heavily on behavioral assumptions, separation rules, controller logic, weather cases, and calibration. A precise simulation output is not necessarily an accurate forecast; it may simply be an assumption wearing several decimal places.
Real-time and human-in-the-loop simulation
Real-time simulation runs operational scenarios at normal speed. A human-in-the-loop study places controllers, pilots, dispatchers, or airport operators into the simulated environment to assess workload, usability, coordination, and procedural feasibility.
It is more resource-intensive than fast-time modeling but can expose problems an algorithm misses, such as ambiguous phraseology, awkward scan patterns, or coordination tasks that look trivial in a process map.
Airspace change proposal
An airspace change proposal is the formal case for introducing or modifying routes, controlled airspace, procedures, classifications, or usage arrangements. It typically requires design evidence, safety assessment, environmental analysis, stakeholder engagement, and regulatory approval.
Approval processes differ by state, but consultation and implementation data cycles often dominate the schedule. The route can be technically designed long before it is institutionally ready to fly.
ORAT and day-in-the-life trials
Operational Readiness, Activation and Transition (ORAT) prepares a new or changed airport facility for live operation. It integrates procedures, recruitment, training, systems, asset handover, stakeholder readiness, trials, migration, and opening-day command arrangements.
A day-in-the-life trial tests realistic passenger, baggage, aircraft, staff, and system scenarios before opening. ORAT is not ordinary commissioning. A conveyor can pass its engineering test while the people, messages, bags, and exceptions surrounding it remain gloriously unprepared.
Environmental Performance
LTO cycle
The ICAO Landing and Takeoff (LTO) cycle models aircraft operations below approximately 3,000 feet using standard phases such as approach, taxi or idle, takeoff, and climb-out. It supports local emissions inventories and certification comparisons.
The standard cycle is not a complete account of an individual flight’s actual emissions. Real taxi duration, engine type, thrust settings, auxiliary-power use, and local operating conditions can differ substantially.
CDO and CCO
Continuous Descent Operations (CDO) allow aircraft to descend with minimal level flight and lower thrust. Continuous Climb Operations (CCO) similarly reduce level-offs during departure.
Both can reduce fuel burn, noise, emissions, and controller interventions. Benefits depend on traffic demand, runway sequence, airspace restrictions, aircraft capability, and coordination with adjacent sectors. At peak times, full continuity may be operationally impossible.
Free Route Airspace
Free Route Airspace (FRA) allows users to plan routes between defined entry, exit, and intermediate points without following the fixed ATS route network, subject to airspace availability and operational constraints.
FRA can reduce planned distance and fuel burn, but it increases the range of trajectories controllers and systems must manage. Cross-border implementation and military-airspace availability strongly influence the realized benefit.
Horizontal flight efficiency
Horizontal flight efficiency compares flown or planned route length with a reference such as the great-circle distance or an achieved-distance benchmark. European performance frameworks use indicators including planned and actual trajectory extensions.
A shorter route is usually more efficient, but directness can conflict with weather avoidance, military airspace, sector capacity, charging zones, and airline wind optimization. The shortest line on the map is not always the lowest-fuel trajectory.
Balanced Approach to aircraft noise
ICAO’s Balanced Approach addresses aircraft noise through four elements: quieter aircraft at source, land-use planning, noise-abatement operating procedures, and operating restrictions.
Restrictions are intended to follow consideration of the other elements and a problem-specific assessment. The framework matters when airports propose night limits, runway-use rules, or aircraft bans and must demonstrate proportionality.
Noise contours, DNL, and Lden
Noise contours map locations experiencing equivalent modeled or measured aircraft-noise exposure. Day-Night Average Sound Level (DNL) and day-evening-night level (Lden) apply energy averaging with penalties for sensitive periods.
DNL and Lden are not directly interchangeable because their time periods and penalties differ. They describe cumulative exposure, not the loudness of a single overflight. Community response can therefore change even when the annual contour remains similar.
Quota Count
The Quota Count (QC) system assigns aircraft movements a noise category based on certified noise performance, commonly for management of night operations at certain UK airports. An airport may have both a movement limit and a total QC budget.
A quieter aircraft consumes less quota, allowing the same movement count to produce a smaller quota total. QC classifications are regime-specific and should not be applied as a universal aircraft-noise score.
NADP 1 and NADP 2
Noise Abatement Departure Procedures adjust thrust-reduction and acceleration profiles to manage noise distribution. Broadly, NADP 1 emphasizes noise reduction closer to the airport, while NADP 2 tends to provide benefit farther from the airport, subject to operator procedures and local requirements.
The names do not imply that one procedure is universally quieter. They redistribute noise differently and can affect fuel burn, climb profile, and community exposure.
APU, GPU, and PCA
An aircraft’s Auxiliary Power Unit (APU) supplies onboard power and conditioned air but creates noise and emissions. A Ground Power Unit (GPU) supplies electrical power from the stand, while Pre-Conditioned Air (PCA) supplies heating or cooling.
Providing fixed electrical ground power and PCA can reduce APU use, but only if equipment is compatible, reliable, conveniently connected, and enforced through operating rules. Installed equipment that crews cannot trust will mostly decorate the stand.
Airport Carbon Accreditation
Airport Carbon Accreditation is an airport-specific carbon-management certification program administered through Airports Council International. Its levels reflect progressively broader measurement, reduction, stakeholder engagement, and net-zero or transition requirements.
Accreditation level should be read with the emissions boundary and methodology. Direct airport-controlled emissions are different from aircraft, airline, tenant, passenger-access, and supply-chain emissions that the airport may influence but not control.
The Phrase Translator
“We’re constrained in the rolling hour, not across the day.”
It may mean: Total daily movements fit, but too many flights are concentrated in overlapping peak intervals. Moving a handful of timings may solve more than adding theoretical annual capacity.
“That’s an airport slot, not an ATFM slot.”
It may mean: The flight has permission to use the airport at a scheduled time, but it has not received protection from day-of-operation network delay.
“The TOBT moved, so the TSAT is no longer protected.”
It may mean: The aircraft will not be ready as promised, and departure sequencing may allocate its previous position to another flight.
“DMAN is sequencing bad TOBTs very efficiently.”
It may mean: The software is working correctly, but the readiness information supplied to it is unreliable. Automation has not cured the input problem.
“The stand plan works until the first widebody goes tech.”
It may mean: The allocation is feasible under the base schedule but has little recovery space for an aircraft that becomes unserviceable and remains on stand.
“We can recover two movements an hour if ROT comes down.”
It may mean: Runway occupancy, rather than separation minima alone, is limiting throughput. Better exit use or reduced runway crossings could release capacity.
“The runway is CAT III capable, but the operation isn’t.”
It may mean: The ground installation meets one part of the requirement, but aircraft approval, crews, lighting, power, LVP, or equipment serviceability prevents full CAT III use.
“ASMA is showing us where the arrival queue lives.”
It may mean: Additional airborne time near the airport indicates that demand is being absorbed through terminal-area sequencing or holding rather than upstream ground delay.
“We’re above 80 percent only after JNUS.”
It may mean: The slot series would miss the historic-usage threshold unless specified cancellations are accepted as justified non-use.
“The PCR supports normal operations; the concern is overload frequency.”
It may mean: Aircraft loading is not an automatic prohibition, but repeated operations above the normal compatibility threshold could accelerate pavement deterioration.
“The NOTAM is out, but AIRAC is the real dependency.”
It may mean: Users have been warned temporarily, but permanent charts, procedures, and navigation databases are not yet synchronized for operational implementation.
“We need the safety argument before opening the split sector.”
It may mean: The proposed staffing configuration may add capacity, but the ANSP must first demonstrate safe coordination, workload, communication, and contingency arrangements.
“The EBS is masking a make-up constraint.”
It may mean: Bags can be stored early, but the downstream positions where they are assembled for flights cannot handle the release peak.
“The till decision matters more than the terminal cost estimate.”
It may mean: Whether commercial revenues offset aeronautical charges may have a larger tariff effect than a modest change in project expenditure.
“The CTOT is compliant, but the passenger schedule is already lost.”
It may mean: The flight can still take off within its network slot, but passenger connections, crew legality, curfew exposure, or aircraft rotation consequences are already severe.
“We have an AODB truth problem.”
It may mean: Multiple systems disagree about flight status, timing, aircraft type, or resource allocation, and no one trusts which source should control downstream decisions.
“The noise envelope is the binding runway constraint.”
It may mean: Physical runway throughput could support more operations, but planning conditions, quota limits, contours, or community-noise obligations prevent that capacity from being scheduled.
Net Net
Airports and ANSP language is difficult because physical infrastructure, controlled airspace, aircraft performance, safety regulation, network flow, passenger processing, environmental limits, and regulated economics all describe the same operation from different angles. A term that sounds like a timestamp may control a runway sequence; a surface code may alter aircraft performance; a regulatory classification may determine the economics of an entire expansion.
- Is this referring to the aerodrome, terminal, apron, controlled airspace, or wider ATM network?
- Which formal classification applies, such as airport level, airspace class, aerodrome code, wake category, RWYCC, or RFF category?
- Is the time being discussed scheduled, estimated, targeted, calculated, or actual, and which system supplies it?
- Are we discussing an airport slot, an ATFM restriction, a stand allocation, or a runway sequence?
- Which capacity is binding: runway, sector, stand, terminal, baggage, environmental, or regulatory capacity?
- What is the denominator and event definition behind the reported delay, punctuality, productivity, or service-unit metric?
- Which requirement controls the decision: the AIP, aerodrome certificate, safety assessment, operating procedure, slot rule, charging regulation, or airline approval?
- Does the proposed change require an AIRAC publication, NOTAM, flight-procedure amendment, safety case, or airspace-change approval?
- Which operational party is authoritative for the relevant field or decision: airport operator, aircraft operator, handler, tower, approach unit, ACC, coordinator, or network manager?
- What assumption about aircraft mix, weather, taxi time, passenger flow, controller workload, or schedule concentration drives the result?
- What evidence supports the conclusion: surveillance data, AODB timestamps, simulation, safety evidence, pavement analysis, passenger survey, or operational trial?
- What would materially change the outcome: a different runway configuration, revised TOBT, lower RWYCC, missed CTOT, unavailable stand, curfew exposure, or altered traffic forecast?
Real fluency does not come from memorizing every acronym. It comes from knowing whether the conversation is about permission, position, performance, capacity, safety, or money, and asking the question that reveals which one actually controls.