An aerodrome change may begin as a drawing, a surveyed feature or an operational decision. Before people can use the resulting aeronautical information, it must pass through a coordinated process that connects its originator with those responsible for managing and distributing it. A new file format alone cannot make that process reliable.
Aeronautical Information Management (AIM) emphasizes coordinated, quality-assured digital data. ICAO describes the transition from product-based Aeronautical Information Services (AIS) to data-centric AIM. AIS already handles aeronautical data; the change places greater emphasis on managing and exchanging that data throughout its lifecycle, rather than focusing mainly on the resulting publications. It is more than putting documents online.
What changes when the focus moves to data
Publications remain useful outputs, but the organization also needs to understand the data behind them. Who supplied it? Which checks apply? Who owns a correction? How will an approved change reach the people and systems that need it?
ICAO’s AIM framework connects those responsibilities with the collection, management and provision of aeronautical information. The Aeronautical Information Publication (AIP), its amendments and supplements remain part of that environment alongside other information products and digital data sets.
For an airport or aviation organization, a practical starting point is to trace one aeronautical information change from its source to its final use. This reveals responsibilities that can be difficult to see when each team reviews only its own document or system.
Work through a change before choosing a solution
Consider an illustrative aerodrome infrastructure change. The project team should establish what aeronautical information may be affected and involve the responsible specialists early. It should not assume that construction completion and information readiness are the same milestone.
Follow the proposed change through its handoffs: identify the originator, the reviewing function, the publishing responsibility and the users who need to know. Record where a discrepancy would be returned and who would decide that it has been resolved. This is a useful project exercise rather than an operational instruction for issuing a particular publication.
Software can support these handoffs, but it cannot resolve an unanswered ownership question. Agreeing responsibilities first gives a system specification a clearer purpose and gives reviewers something concrete to test.
Questions for an AIM capability review
- Which aeronautical data and information products are included in the scope?
- Who supplies each class of information and who accepts it for the next stage?
- How are data quality concerns investigated and corrections tracked?
- How are information changes coordinated with the operational project?
- What records allow the organization to understand where a published item came from?
The answers should describe a working information chain, not only a list of available software features. They also help separate a publishing requirement from a broader data-management improvement.
Connecting the requirement with GANS
GANS’s published AIM scope includes Aeronautical Information Publications (AIPs) and amendments, NOTAMs, pre-flight information bulletins and Aeronautical Information Circulars (AICs). It also covers aerodrome, airspace, route, obstacle and terrain data. These are specific information products and data responsibilities to discuss when defining a project’s deliverables, handoffs and update process.
Explore GANS Aeronautical Information Management services. For a service discussion, prepare the affected products, participating organizations and the handoff that is causing difficulty. See GANS office contact details. If the change also involves airspace and flight procedure design, identify that interface in the brief.